Anirudh Pucha's SOA Solutions

50th Oracle book,Packt Enterprise is offering an exclusive discount for Oracle books during July 2011

2011-07-14T20:47:00.000+05:30

To celebrate the publication of its 50th Oracle book,Packt Enterprise is offering an exclusive discount for Oracle books during July 2011.
Here is the link : http://www.packtpub.com/article/50th-oracle-book-offer

Tips on BAM 11g

2010-11-23T11:56:00.001+05:30

In general, before upgrading to latest patchset or applying any BAM adapter patches, always make sure the BAM Adapter staging-mode is set to "nostage". This configuration can be verified by searching "OracleBamAdapter" key word in MiddlewareHome/user_projects/domains//config/config.xml file.

To redeploy bam adapter, you should pick “I will make the deployment accessible from the following location” as the “Source accessibility” option and set the path to point to /Oracle_SOA1/soa/connectors/OracleBamAdapter.rar, otherwise, the staging-mode will be unset.

My technical contribution to a BPEL 2.0 book is published now !

2010-10-19T10:45:00.001+05:30

The book in which I've technically contributed as a reviewer is released : https://www.packtpub.com/ws-bpel-2-0-for-soa-composite-applications-with-ibm-websphere-7/book?utm_source=packtpub.com&utm_medium=blog&utm_content=blog&utm_campaign=mdb_005119.
Friends, you can see my biodata in the index pages of the book.

weblogic.transaction.internal.TimedOutException : Transaction Rolledback

2010-09-28T08:51:00.002+05:30

In SOA 11g :
####################

nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-30EEAE1332BCF5602AFB
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:148)
at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:567)
at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:427)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:276)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-30EEAE1332BCF5602AFB
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1733)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1578)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1900)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1488)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

]]
[2010-09-14T12:11:59.856+10:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.dispatch] [tid: orabpel.invoke.pool-4.thread-17] [userId: ] [ecid: 0000IgDwXA8DkZt5Gf_Aif1CYSZb000mvK,0:14:100000016] [APP: soa-infra] [dcid: 881a76989790c302:-9fb0eaf:12afa3cb2aa:-7ffd-0000000000001d8a] Failed to handle dispatch message ... exception ORABPEL-05002[[

Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-30EEAE1332BCF5602AFB
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1733)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1578)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1900)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1488)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-30EEAE1332BCF5602AFB
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002

Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-30EEAE1332BCF5602AFB
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1733)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1578)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1900)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1488)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 299 seconds
BEA1-30EEAE1332BCF5602AFB
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).

at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:206)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

Solution :
#####################
1) JTA timeout - set to 3600

2) "BPELEngineBean" and "BPELDeliveryBean"timeout - set to 1800

How to make your File Adapter pick only one file at a time from a location

2010-09-11T09:56:00.003+05:30

In SOA 11g, you use File adapter to read files from the given location.
With this read operation it picks all the files at time.

You want to configure File Adapters that it should pick one file at time from the given location with given polling interval.

Solution :

You set the "SingleThreadModel" and "MaxRaiseSize" properties for your file adapter.
Edit the adapter's jca file and add the following properties:

property name="SingleThreadModel" value="true"
property name="MaxRaiseSize" value="1"

You can set these properties also through jdeveloper, by opening composite.xml, selecting the adapter and then changing the properties through the properties panel.

Apply patch : 9892463 for an amazing purge script in SOA 11g - nearly 2 hours to purge 5 million instances ;)

2010-08-03T23:02:00.001+05:30

ESB Dispatch failed with error Cannot get part 'rootId'

2010-04-27T12:09:00.001+05:30

Issue ::
You register an Oracle ESB with some SOAP services and while trying to run the esb, you get the error ::

xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
xmlns="">env:ESBMessageProcessingFailed
xmlns="">ESB Dispatch failed with error Cannot get part 'rootId'. Part was not found in message; nested exception is: org.collaxa.thirdparty.apache.wsif.WSIFException: Cannot get part 'rootId'. Part was not found in message

Solution:

ESB by default generates ESB WSDL(Java Binding) and SOAP WSDL, By Default ESB WSDL will be invoked for better performance, We have a parameter called "includeESBBinding" to switch Off ESB WSDL, So that we can force to use SOAP based WSDL. So, All you have to do is to force to use SOAP Based WSDL by addding the parameter "includeESBBinding=false" in the Service Definition.

setting includeESBBinding=false on the invoked routing service

The Oracle BAM Active Data Cache service failed to start - System.DllNotFoundException: Unable to load DLL (OraOps10.dll)

2009-12-17T14:23:00.003+05:30

Issue :
##############
You start your DB and then try starting the BAM 10.1.3.x Services. Then, your BAM ADC Service fails to start with the following errors in the BAM ADC log::

2009-12-17 14:15:19,937 [2376] ERROR - ActiveDataCache The Oracle BAM Active Data Cache service failed to start. Oracle.BAM.ActiveDataCache.Common.Exceptions.CacheException: ADC Server exception in Startup(). ---> System.DllNotFoundException: Unable to load DLL (OraOps10.dll).
at Oracle.DataAccess.Client.OpsTrace.GetRegTraceInfo(UInt32& TrcLevel, UInt32& StmtCacheSize)
at Oracle.DataAccess.Client.OraTrace.GetRegistryTraceInfo()
at Oracle.DataAccess.Client.OracleConnection..ctor(String connectionString)
at Oracle.DataAccess.Client.OracleConnection..ctor(String connectionString)
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleDataFactory.GetConnection()
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleStorageEngine.GetServerVersion()
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleStorageEngine.Startup(IDictionary oParameters)
at Oracle.BAM.ActiveDataCache.Kernel.Server.DataStoreServer.Startup()
--- End of inner exception stack trace ---
at Oracle.BAM.ActiveDataCache.Kernel.Server.DataStoreServer.Startup()
at Oracle.BAM.ActiveDataCache.Kernel.Server.Server.Startup()
at Oracle.BAM.ActiveDataCache.Service.DataServer.Run()
2009-12-17 14:16:29,843 [2088] INFO - ActiveDataCache The Oracle BAM Active Data Cache service is starting.
2009-12-17 14:16:29,859 [2088] INFO - Common Using an un-secured connection. Set the BAMSecureServerKey configuration setting to secure the connection.
2009-12-17 14:16:29,890 [2088] INFO - ActiveDataCache Starting up performance counters...
2009-12-17 14:16:29,906 [2088] INFO - ActiveDataCache Performance counters started up completely.
2009-12-17 14:16:30,015 [2088] ERROR - ActiveDataCache Unable to load DLL (OraOps10.dll).
2009-12-17 14:16:30,015 [2088] WARN - ActiveDataCache Exception occurred in method Startup

Stack trace:
at Oracle.DataAccess.Client.OpsTrace.GetRegTraceInfo(UInt32& TrcLevel, UInt32& StmtCacheSize)
at Oracle.DataAccess.Client.OraTrace.GetRegistryTraceInfo()
at Oracle.DataAccess.Client.OracleConnection..ctor(String connectionString)
at Oracle.DataAccess.Client.OracleConnection..ctor(String connectionString)
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleDataFactory.GetConnection()
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleStorageEngine.GetServerVersion()
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleStorageEngine.Startup(IDictionary oParameters)
at Oracle.BAM.ActiveDataCache.Kernel.Server.DataStoreServer.Startup()

2009-12-17 14:16:30,015 [2088] ERROR - ActiveDataCache The Oracle BAM Active Data Cache service failed to start. Oracle.BAM.ActiveDataCache.Common.Exceptions.CacheException: ADC Server exception in Startup(). ---> System.DllNotFoundException: Unable to load DLL (OraOps10.dll).
at Oracle.DataAccess.Client.OpsTrace.GetRegTraceInfo(UInt32& TrcLevel, UInt32& StmtCacheSize)
at Oracle.DataAccess.Client.OraTrace.GetRegistryTraceInfo()
at Oracle.DataAccess.Client.OracleConnection..ctor(String connectionString)
at Oracle.DataAccess.Client.OracleConnection..ctor(String connectionString)
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleDataFactory.GetConnection()
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleStorageEngine.GetServerVersion()
at Oracle.BAM.ActiveDataCache.Kernel.StorageEngine.Oracle.OracleStorageEngine.Startup(IDictionary oParameters)
at Oracle.BAM.ActiveDataCache.Kernel.Server.DataStoreServer.Startup()
--- End of inner exception stack trace ---
at Oracle.BAM.ActiveDataCache.Kernel.Server.DataStoreServer.Startup()
at Oracle.BAM.ActiveDataCache.Kernel.Server.Server.Startup()
at Oracle.BAM.ActiveDataCache.Service.DataServer.Run()
2009-12-17 14:16:50,687 [4980] INFO - ActiveDataCache The Oracle BAM Active Data Cache service is starting.
2009-12-17 14:16:50,703 [4980] INFO - Common Using an un-secured connection. Set the BAMSecureServerKey configuration setting to secure the connection.
2009-12-17 14:16:50,734 [4980] INFO - ActiveDataCache Starting up performance counters...
2009-12-17 14:16:50,750 [4980] INFO - ActiveDataCache Performance counters started up completely.
2009-12-17 14:16:50,828 [4980] ERROR - ActiveDataCache Unable to load DLL (OraOps10.dll).
2009-12-17 14:16:50,828 [4980] WARN - ActiveDataCache Exception occurred in method Startup

Solution :
####################
Go to your BAM installed home in your local folder. Copy the C:\OracleBAM\ClientForBAM\BIN location and then go to My Computer - > Advanced - Environment Variables - > Path - Edit - > Paste this location C:\OracleBAM\ClientForBAM\BIN as the first entry in the path. Click OK.
Now, try starting your BAM Services. All the services including your BAM ADC Service starts successfully with logs as below ::

2009-12-17 14:20:24,640 [2432] INFO - ActiveDataCache The Oracle BAM Active Data Cache service is starting.
2009-12-17 14:20:24,656 [2432] INFO - Common Using an un-secured connection. Set the BAMSecureServerKey configuration setting to secure the connection.
2009-12-17 14:20:24,671 [2432] INFO - ActiveDataCache Starting up performance counters...
2009-12-17 14:20:24,687 [2432] INFO - ActiveDataCache Performance counters started up completely.
2009-12-17 14:20:28,859 [2432] DEBUG - ActiveDataCache Data Storage Engine is Oracle
2009-12-17 14:20:32,750 [2432] DEBUG - ActiveDataCache ADC schema version is 1003.0
2009-12-17 14:20:36,296 [2432] INFO - ActiveDataCache Accepting requests on tcp:4033
2009-12-17 14:20:36,296 [2432] INFO - ActiveDataCache The Oracle BAM Active Data Cache service has started.
2009-12-17 14:20:37,453 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:37,546 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:7afac3f8-17aa-4e14-89dc-e8e3467b47a5
2009-12-17 14:20:37,562 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 7afac3f8-17aa-4e14-89dc-e8e3467b47a5
2009-12-17 14:20:37,593 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:37,593 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:86d705f0-8d27-4b34-b84a-ae7c0f01cefe
2009-12-17 14:20:37,593 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 86d705f0-8d27-4b34-b84a-ae7c0f01cefe
2009-12-17 14:20:37,609 [5272] DEBUG - ActiveDataCache Exists:SysIterRolePrivilegeMapping
2009-12-17 14:20:37,703 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:37,703 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:839b2c8f-db8a-4c0f-b77d-6b4992f44690
2009-12-17 14:20:37,703 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 839b2c8f-db8a-4c0f-b77d-6b4992f44690
2009-12-17 14:20:37,703 [5272] DEBUG - ActiveDataCache Exists:SysIterMCProp
2009-12-17 14:20:37,734 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterMCProp:5598ea8e-a7b5-4bbd-a69e-1857309d9339
2009-12-17 14:20:37,734 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 5598ea8e-a7b5-4bbd-a69e-1857309d9339
2009-12-17 14:20:37,734 [5272] DEBUG - ActiveDataCache Exists:SysIterMCProp
2009-12-17 14:20:37,734 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterMCProp:1fb4f0fd-d9ea-4188-8aa0-9ecd9a3f8f5b
2009-12-17 14:20:37,734 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 1fb4f0fd-d9ea-4188-8aa0-9ecd9a3f8f5b
2009-12-17 14:20:37,953 [5272] DEBUG - ActiveDataCache Exists:SysIterMCProp
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterMCProp:542b423c-67ca-48c0-961d-02e76c978180
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 542b423c-67ca-48c0-961d-02e76c978180
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache Exists:SysIterMCProp
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterMCProp:cb67b151-d9ab-4cbf-a60b-34ae32fb8b3a
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: cb67b151-d9ab-4cbf-a60b-34ae32fb8b3a
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache Exists:SysIterMCProp
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterMCProp:a0c77d52-c331-4134-8615-28d256b23d8b
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: a0c77d52-c331-4134-8615-28d256b23d8b
2009-12-17 14:20:37,968 [5272] DEBUG - ActiveDataCache Exists:SysIterMCProp
2009-12-17 14:20:37,984 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterMCProp:ef7d8e46-206f-4765-9d25-d36d539c1b0b
2009-12-17 14:20:37,984 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: ef7d8e46-206f-4765-9d25-d36d539c1b0b
2009-12-17 14:20:38,000 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:38,015 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:2b68b7b5-00ba-4f7a-bea7-d1d43c8e6510
2009-12-17 14:20:38,015 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 2b68b7b5-00ba-4f7a-bea7-d1d43c8e6510
2009-12-17 14:20:38,031 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:38,031 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:8342b9b0-f4a9-4291-9474-01417e334b40
2009-12-17 14:20:38,031 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: 8342b9b0-f4a9-4291-9474-01417e334b40
2009-12-17 14:20:38,031 [5272] DEBUG - ActiveDataCache Exists:SysIterRule
2009-12-17 14:20:38,046 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:38,046 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:c43efc38-6ca7-4ffd-857a-ddd9e1fb22af
2009-12-17 14:20:38,046 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: c43efc38-6ca7-4ffd-857a-ddd9e1fb22af
2009-12-17 14:20:38,046 [5272] DEBUG - ActiveDataCache Exists:SysIterUser
2009-12-17 14:20:38,062 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterUser:ab03cf32-2401-4469-8faf-7ff2f8938fc8
2009-12-17 14:20:38,062 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: ab03cf32-2401-4469-8faf-7ff2f8938fc8
2009-12-17 14:20:38,062 [5272] DEBUG - ActiveDataCache Exists:SysIterEscalation
2009-12-17 14:20:38,078 [5272] DEBUG - ActiveDataCache Exists:SysIterRule
2009-12-17 14:20:38,109 [5272] DEBUG - ActiveDataCache OpenViewset: SysIterRule:de488111-4227-43eb-9e56-7e645c1fbfad
2009-12-17 14:20:38,109 [5272] DEBUG - ActiveDataCache Insta-Close Viewset: de488111-4227-43eb-9e56-7e645c1fbfad
2009-12-17 14:20:38,109 [5272] DEBUG - ActiveDataCache Exists:SysIterUser

[Error : Cannot load apachemoduleossl.dll into server] While Applying 10.1.3.5 Patchset On 10.1.3.1.0 SOA Oracle

2009-09-02T12:03:00.000+05:30

Symptoms
You have an existing 10.1.3.1.0 SOA Suite Installation, upgraded the orabpel and oraesb schemas with 10.1.3.5 schema upgrade scripts, and then start applying the 10.1.3.5 patchset on it.

While applying the patchset, the OUI Configuration Assistant fails with following errors :

Syntax error on line 278 of d:/soa331/apache/apache/conf/httpd.conf:
Cannot load d:/soa331/apache/apache/modules/apachemoduleossl.dll into server: (127) The specified procedure could not be found:

Cause
This is because the ApacheModuleOSSL.dll is not commented in the SOA_ORACLE_HOME\Apache\Apache\conf\httpd.conf file.
Solution
Replace the 10.1.3.5 SOA_ORACLE_HOME\Apache\Apache\modules\ApacheModuleOSSL.dll with 10.1.3.4 SOA_ORACLE_HOME\Apache\Apache\modules\ApacheModuleOSSL.dll
Open the 10.1.3.5 SOA_ORACLE_HOME\Apache\Apache\conf\httpd.conf file and change the entry below from :

LoadModule ossl_module modules/ApacheModuleOSSL.DLL

TO

#
#LoadModule ossl_module modules/ApacheModuleOSSL.DLL
#

3. Open the 10.1.3.5 SOA_ORACLE_HOME\Apache\Apache\conf\httpd.conf file and change the entry below from :

Include the SSL definitions and Virtual Host container
include "D:\SOA331\Apache\Apache\conf\ssl.conf"
TO

# Include the SSL definitions and Virtual Host container
# include "D:\SOA331\Apache\Apache\conf\ssl.conf"
4. Now, when you click on the 'retry' button on the OUI, it completes and 10.1.3.5 patchset gets applied successfully.

[ERROR ORABPEL-10057]: INVALID QUERY IN COPY OPERATION

2009-05-08T12:08:00.001+05:30

I created a BPEL project . While trying to assign the values from input
message to output message using assign activity, the namespace prefix is missing for some of the fields in the input message.

Hence am getting the below error
Error(73):
[Error ORABPEL-10057]: invalid query
[Description]: in line 73 of

"C:\jdevstudio10134\jdev\mywork\ManageProductOfferingAvailability\TransformCus
tomerQuoteToServiceOrderAS\bpel\TransformCustomerQuoteToServiceOrderAS.bpel", query

"/client:TransformCustomerQuoteToServiceOrderASProcessRequest/ns1:CustomerQuot
e/CustomerQuoteItem/ns1:id" is invalid, because step 'CustomerQuoteItem' is not valid.. Potential fix]: Check the XML schema and make sure your query string is
valid

Fix : 8500399 & 7174309(workflow)

CUSTOM ANT SCRIPTS FOR DEPLOYING ESB PROJECTS

2009-03-31T08:26:00.004+05:30

Registration of ESB Projects:

Ant comes up with a specialized task for registering the Oracle ESB projects into the SOA server.

1. Extract ESBMetadataMigration.jar from $SOA_Home\Integration\esb\deployment\documentation.zip

2. Modify the following properties in the ESBMetadataMigrationTaskdefs.xml

project name="ESBMetadataMigrationTaskdefs">
property name="commons.httpclient.home" value="#commons-httpclient jar location"/>
property name="jaxb.v2.0.2.home" value="#jaxb jar location"/>
property name="soa.suite.home" value="#Oracle_SOA_Home"/>
property name="esb.home" value="#ESBMetadataMigration.jar location"/>
!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Custom ant task definitions, to enable import. - This section should be treated as immutable upon installation. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
dirname property="imported.basedir" file="${ant.file.ESBMetadataMigrationTaskdefs}"/>
taskdef resource="oracle/tip/esb/client/anttasks/antlib.xml">
classpath>
pathelement location="${esb.home}/ESBMetadataMigration.jar"/>
pathelement location="${commons.httpclient.home}/commons-httpclient-3.0.1.jar"/>
pathelement location="${soa.suite.home}/lib/xmlparserv2.jar"/>
pathelement location="${soa.suite.home}/integration/esb/lib/commons-logging.jar"/>
pathelement location="${soa.suite.home}/integration/esb/lib/commons-codec-1.3.jar"/>
pathelement location="${soa.suite.home}/integration/esb/lib/oraesb.jar"/>
pathelement location="${jaxb.v2.0.2.home}/lib/activation.jar"/>
pathelement location="${jaxb.v2.0.2.home}/lib/jaxb-api.jar"/>
pathelement location="${jaxb.v2.0.2.home}/lib/jsr173_1.0_api.jar"/>
pathelement location="${jaxb.v2.0.2.home}/lib/jaxb-impl.jar"/>
/classpath>
/taskdef>
/project>

3. Import the following config files in your ant build script

import file="${bpel.home}/utilities/ant-orabpel.xml"/>
import file="${ESBMetaDataLoc}/ESBMetadataMigrationTaskdefs.xml"/>

4. Final step to register the ESB projects;

target name="ESB_1" description="run ESB_1">
echo>Registering ESB_1...
deployESBProjects esbMetadataServerHostname="${http.hostname}"
esbMetadataServerPort="${http.port}"
userName="${admin.user}"
password="${admin.password}">
esbProject directory="${ESB_1.file.path}"/>
/deployESBProjects>
/target>

P.S.: Please note that i have deleted "<" symbol in the beginning of every xml statement, since i was unable to display the xml content as a post. So, add "<" to beginning of each xml line.

Dehydration Store Tables used in Oracle BPEL PM

2009-02-26T12:07:00.000+05:30

cube_instance - stores instance metadata, eg. instance creation date, current
state, title, process identifier

cube_scope - stores the scope data for an instance ... all the variables
declared in the bpel flow are stored here, as well as some internal objects to
help route logic throughout the flow.

work_item - stores activities created by an instance ... all BPEL activities in
a flow will have a work_item created for it. This work item row contains meta
data for the activity ... current state, label, expiration date (used by wait
activities) ... when the engine needs to be restarted and instances recovered,
pending flows are resumed by inspecting their unfinished work items.

document - stores large XML variables. If a variable gets to be larger than a
specific size (configurable via the largeDocumentThreshold property via the
domain configuration page) then the variable is stored in this table to
alleviate loading/saving time from the cube_scope table.

audit_trail - stores the audit trail for instances. The audit trail viewed
from the console is modelled from an XML document. As the instance is worked
on, each activity writes out events to the audit trail as XML which is compress
ed and stored in a raw column. Querying the audit trail via the API/console wil
l join the raw columns together and uncompress the contents into a single XML do
cument.

audit_details - audit details can be logged via the api ... by default
activities such as assign log the variables as audit details (this behavior can
be set via the auditLevel property on the domain configuration page). Details a
re separated from the audit trail because they tend to be very large in size ...
if the user wishes to view a detail they click a link from the audit trail page
and load the detail separately. There is a threshold value for details too ...
if the size of a detail is larger than a specific value (see auditDetailThreshol
d) then it is place in this table, otherwise it is merged into the audit trail r
ow.

dlv_message - callback messages are stored here. All non-invocation messages
are saved here upon receipt. The delivery layer will then attempt to correlate
the message with the receiving instance. This table only stores the metadata
for a message. (eg. current state, process identifier, receive date).

dlv_message_bin - stores the payload of a callback message. The metadata of a
callback message is kept in the dlv_message table, this table only stores the
payload as a blob. This separation allows the metadata to change frequently
without being impacted by the size of the payload (which is stored here and
never modified).

dlv_subscription - stores delivery subscriptions for an instance. Whenever an i
nstance expects a message from a partner (eg. receive, onMessage) a subscription
is written out for that specific receive activity. Once a delivery message is r
eceived the delivery layer attempts to correlate the message with the intended s
ubscription.

invoke_message - stores invocation messages, messages which will result in the
creation of a instance. This table only stores the metadata for an invocation
message (eg. current state, process identifier, receive date).

invoke_message_bin - stores the payload of an invocation message. Serves the
same purpose the dlv_message_bin table does for dlv_message.

task - stores tasks created for an instance. The TaskManager process keeps its
current state in this table. Upon calling invoking the TaskManager process, a
task object is created, with a title, assignee, status, expiration date, etc...
When updates are made to the TaskManager instance via the console the
underlying task object in the db is changed.

schema_md - (just added via patch delivered to Veerle) contains metadata about
columns defined in the orabpel schema. Use case driving this feature was how
to change the size of a custom_key column for a cube_instance row? Changing
the db schema was simple but the engine code assumed a certain length and
truncated values to match that length to avoid a db error being thrown. Now, co
lumn lengths are defined in this table instead of being specified in the code.
To change a column length, change the column definition in the table, then chang
e the value specified in this table, then restart the server.

Column-by-column description:

table ci_id_range

- next_range (integer) - instance ids in the system are allocated on a block
basis ... once all the ids from a block have been allocated, another block is
fetched, next_range specifies the start of the next block.

table cube_instance

- cikey (integer) - primary key ... foreign key for other tables
- domain_ref (smallint) - domain identifier is encoded as a integer to save
space, can be resolved by joining with domain.domain_ref.
- process_id (varchar) - process id
- revision_tag (varchar) - revision tag
- creation_date (date)
- creator (varchar) - user who created instance ... currently not used
- modify_date (date) - date instance was last modified
- modifier (varchar) - user who last modified instance ... currently not used
- state (integer) - current state of instance, see com.oracle.bpel.client.
IInstanceConstants for values
- priority (integer) - current instance priority (user specified, has no impact
on engine)
- title (varchar) - current instance title (user specified, no engine impact)
- status (varchar) - current status (user specified)
- stage (varchar) - current stage (user specified)
- conversation_id (varchar) - extra identifier associated with instance, eg. if
passed in via WS-Addressing or user specified custom key.
- root_id (varchar) - the conversation id of the instance at the top of the
invocation tree. Suppose A -> B -> C, root( B ) = A, root( C ) = A, parent( B )
= A, parent( C ) = B. This instance, instance at the top of the tree will not
have this set.
- parent_id (varchar) - the conversation id of the parent instance that created
this instance, instance at the top of the tree will not have this set.
- scope_revision (integer) - internal checksum of scope bytes ... used to keep
caches in sync
- scope_csize (integer) - compressed size of instance scope in bytes
- scope_usize (integer) - uncompressed size of instance scope in bytes
- process_guid (varchar) - unique identifier for the process this instance be
longs to ... if changes need to be made for all instances of a process, this col
umn is used to query (eg. stale process).
- process_type (integer) - internal
- metadata (varchar) - user specified

table cube_scope

- cikey (integer) - foreign key
- domain_ref (integer) - domain identifier
- modify_date (date) - date scope last modified
- scope_bin (blob) - scope bytes

table work_item

- cikey (integer) - foreign key
- node_id (varchar) - part of work item composite key, identifier for bpel
activity that this work item created for
- scope_id (varchar) - part of work item composite key, identifier for internal
scope that this work item created for (note this is not the scope declared in
bpel, the engine has an internal scope tree that it creates for each instance,
bpel scopes will map to an internal scope but there will be other internal
scopes that have no mapping to the bpel definition).
- count_id (integer) - part of work item composite key, used to distinguish
between work items created from same activity in the same scope.
- domain_ref (integer) - domain identifier
- creation_date (date)
- creator (varchar) - user who created work item ... currently not used
- modify_date (date) - date work item was last modified
- modifier (varchar) - user who last modified work item ... currently not used
- state (integer) - current state of work item, see com.oracle.bpel.client.
IActivityConstants for values
- transition (integer) - internal use, used by engine for routing logic
- exception (integer) - no longer used
- exp_date (date) - expiration date for this work item; wait, onAlarm
activities are implemented as expiration timers.
- exp_flag (integer) - set if a work item has been called back by the
expiration agent (ie. expired).
- priority (integer) - priority of work item, user specified, no engine impact
- label (varchar) - current label (user specified, no engine impact)
- custom_id (varchar) - custom identifier (user specified, no engine impact)
- comments (varchar) - comment field (user specified, no engine impact)
- reference_id (varchar) -
- idempotent_flag (integer) - internal use
- process_guid (varchar) - unique identifier for the process this work item
belongs to ... if changes need to be made for all instances of a process, this
column is used to query (eg. stale process).

table document

- dockey (varchar) - primary key for document
- cikey (integer) - foreign key
- domain_ref (integer) - domain identifier
- classname (varchar) - no longer used
- bin_csize (integer) - compressed size of document in bytes
- bin_usize (integer) - uncompressed size of document in bytes
- bin (blob) - document bytes
- modify_date (date) - date document was last modified

table audit_trail

- cikey (integer) - foreign key
- domain_ref - domain identifier
- count_id (integer) - many audit trail entries may be made for each instance,
this column is incremented for each entry per instance.
- block (integer) - when the instance is dehydrated, the batched audit trail
entries up to that point are written out ... this block ties together all rows
written out at one time.
- block_csize (integer) - compressed size of block in bytes
- block_usize (integer) - uncompressed size of block in bytes
- log (raw) - block bytes

table audit_details

- cikey (integer) - foreign key
- domain_ref (integer) - domain identifier
- detail_id (integer) - part of composite key, means of identifying particular
detail from the audit trail
- bin_csize (integer) - compressed size of detail in bytes
- bin_usize (integer) - uncompressed size of detail in bytes
- bin (blob) - detail bytes

table dlv_message

- conv_id (varchar) - conversation id (correlation id) for the message...this
value is used to correlate the message to the subscription.
- conv_type (integer) - internal use
- message_guid (varchar) - unique identifier for the message...each message
received by the engine is tagged with a message guid.
- domain_ref (integer) - domain identifier
- process_id (varchar) - identifier for process to deliver the message to
- revision_tag (varchar) - identifier for process revision
- operation_name (varchar) - operation name for callback port.
- receive_date (date) - date message was received by engine
- state (integer) - current state of message ... see com.oracle.bpel.client.
IDeliveryConstants for values
- res_process_guid (varchar) - after the matching subscription is found, the
process guid for the subscription is written out here. - res_subscriber
(varchar) - identifier for matching subscription once found.

table dlv_message_bin

- message_guid (varchar) - unique identifier for message
- domain_ref (integer) - domain identifier
- bin_csize (integer) - compressed size of delivery message payload in bytes
- bin_usize (integer) - uncompressed size of delivery message payload in bytes
- bin (blob) - delivery message payload

table dlv_subscription

- conv_id (varchar) - conversation id for subscription, used to help correlate
received delivery messages.
- conv_type (integer) - internal use
- cikey (integer) - foreign key
- domain_ref (integer) - domain identifier
- process_id (varchar) - process identifier for instance
- revision_tag (varchar) - revision tag for process
- process_guid (varchar) - guid for process this subscription belongs to
- operation_name (varchar) - operation name for subscription (receive,
onMessage operation name).
- subscriber_id (varchar) - the work item composite key that this subscription
is positioned at (ie. the key for the receive, onMessage work item).
- service_name (varchar) - internal use
- subscription_date (date) - date subscription was created
- state (integer) - current state of subscription ... see com.oracle.bpel.
client.IDeliveryConstants for values
- properties (varchar) - additional property settings for subscription

table invoke_message

- conv_id (varchar) - conversation id for message, passed into system so
callbacks can correlate properly.
- message_guid (varchar) - unique identifier for message, generated when
invocation message is received by engine.
- domain_ref (integer) - domain identifier
- process_id (varchar) - identifier for process to deliver the message to
- revision_tag (varchar) - revision tag for process
- operation_name (varchar) - operation name for receive activity
- receive_date (date) - date invocation message was received by engine
- state - current state of invocation message, see com.oracle.bpel.client.
IDeliveryConstants for values
- priority (integer) - priority for invocation message, this value will be used
by the engine dispatching layer to rank messages according to importance ...
lower values mean higher priority ... messages with higher priority are dispatch
ed to threads faster than messages with lower values.
- properties (varchar) - additional property settings for message

table invoke_message_bin

- message_guid (varchar) - unique identifier for message
- domain_ref (integer) - domain identifier
- bin_csize (integer) - compressed size of invocation message payload in bytes
- bin_usize (integer) - uncompressed size of invocation message payload in bytes
- bin (blob) - invocation message bytes

table task

- domain_ref (integer) - domain identifier
- conversation_id (varchar) - conversation id for task instance ... allows task
instance to callback to client
- title (varchar) - current title for task, user specified
- creation_date (date) - date task was created
- creator (varchar) - user who created task
- modify_date (date) - date task was last modified
- modifier (varchar) - user who last modified task
- assignee (varchar) - current assignee of task, user specified, no engine
impact
- status (varchar) - current status, user specified, no engine impact
- expired (integer) - flag is set if task has expired
- exp_date (date) - expiration date for task, expiration actually takes place
on work item in TaskManaged instance, upon expiration task row is updated
- priority (integer) - current task priority, user specified, no engine impact
- template (varchar) - not used
- custom_key (varchar) - user specified custom key
- conclusion (varchar) - user specified conclusion, no engine impact

HOW TO USE CUSTOM EXTENSION FUNCTIONS IN ESB VIA JDEVELOPER 10.1.3.4

2009-02-12T09:20:00.001+05:30

How to create custom xpath functions in JDeveloper.

ANSWER
=======
My Sample extension function save in D:\myxpath

---------------------------------------
package myxpath.functions;
public class StringTest
{
public StringTest()
{
}
public static String toUpperCase(String s)
{ return s.toUpperCase();
}
}

----------------------------------------------

set PATH=D:\ORACLE\jdevstudio10134\jdk\bin;%PATH%
D:\myxpath>javac StringTest.java -d .

(Note -d and . it creates the class file with directory structure)

Create the XSL Mappers extesnion XML file
D:\myxpath\myxpathExtensionFunctions.xml
==========================================

xmlns:sample="http://www.oracle.com/XSL/Transform/java/myxpath.functions.StringTest">

============================================
For more info Refer:
SOA_Oracle_home\bpel\samples\demos\XSLMapper\ExtensionFunction\README.txt

Create the JDEV Extesnion XML file in
D:\myxpath\meta-inf\extension.xml
============================================

id="myxpath.functions.StringTest"
version="10.1.3"
esdk-version="1.0">
StringTest
Anirudh Pucha

============================================
For more info refer:
/jdev/doc/extension/ide-extension-packaging.html

Create the JAR file
D:\myxpath>jar -cvf myxpath.functions.StringTest.10.1.3.jar
myxpath\functions\StringTest.class
-m meta-inf\extension.xml

Copy this JAR file to \jdev\extensions\
For Eg: D:\ORACLE\jdevstudio10134\jdev\extensions\myxpath.functions.StringTest.10.1.3.jar

Goto Jdev->Tools->Prefereance->XSl Maps->User Defined Extension config file and give
myxpathExtensionFunctions.xml

Restart your JDEV and now you should be able to see the Custom XSL Map function under :
User Defined Function in XSL Mapper design.

Now you can use this custom function like this in design time:

To use this function at runtime for ESB:
Open your j2ee\oc4j_soa\config\server.xml and add a entry below

as follows :

ESBRuntimeException: Designtime cache has not been initialized

2009-01-25T12:59:00.002+05:30

when I click on the Instances icon on the right on the screen I get the
@ following error text box on the screen :
@ 08/07/22 11:57:33 oracle.tip.esb.infra.exception.ESBRuntimeException:
@ Designtime cache has not been initialized
@ Please look in logs for following signs of failure. Fix them and restart. (a)
@ Database access errors (b) ESB Bootstrap errors (c) OC4J class load errors
@ (d) Product installation errors (e) Export ESB params and verify if host and
@ port parameters are correct. Please contact Oracle Support if unable to fix
@ the issue.
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.console.CacheManager.getInitializedInstance(CacheManager.java:3
@ 19)
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.console.XMLConsoleManagerImpl.(XMLConsoleManagerImpl.java
@ :218)
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.console.ConsoleManagerFactory.getConsoleManager(ConsoleManagerF
@ actory.java:57)
@ 08/07/22 11:57:33 at
@ oracle.tip.esb.configuration.servlet.command.ServiceExplorerCommand.execute(Se
@ rviceExplorerCommand.java:45)

Probable Solution :

Note: Assuming here your esb-dt container name is OC4J_ESBDT

Make sure the directory esb-dt exist in $ORACLE_HOME/j2ee/OC4J_ESBDT/application-deployments/

Check the opmn/logs/default*.log and opmn.log (in the same location) files to see if there are any ESB related
exceptions logged.

If there is a timeout issues in
$ORACLE_HOME/j2ee/OC4J_ESBDT/log/OC4J_ESBDT_ESBDT_GROUP_1/oc4j/log.xml
Then

1. Increase the value of the transaction-timeout parameter in
the $ORACLE_HOME/j2ee/OC4J_ESBDT/config/transaction-manager.xml file.
For eg: transaction-timeout="300"

2. Increase the value of the xa_timeout parameter in the
$ORACLE_HOME/integration/esb/esb_config.ini file.

For Eg:
xa_timeout=3600
jms_receive_timeout=300

3. Login into repoistory DB as system user and then issue: ALTER SYSTEM set OPEN_CURSORS=5000 scope=both;

4. Restart the ESB Server ( opmnctl stopall; opmnctl startall).

Make sure you can connect to your repository database with oraesb schema.
If the passowrd is wrong to reset it for oc4jadmin
Check /oracle/SOA/SOA10gR3_HA/j2ee/OC4J_ESBDT/config/system-jazn-data.xml
Refer: Note 470680.1

Check the values for the ESB_PARAMETERS and make sure the 'DT_OC4J_HTTP_PORT' and 'DT_OC4J_HOST' are correct.
This should be your loadbalancer port and host name in HA.
Also make sure other parameters are configured properly according to your type of JMS ( OracleASjms or OracleOJMS)
Refer Note:453355.1
For HA: http://download.oracle.com/docs/cd/E10291_01/core.1013/e10294/webapp.htm#CHDCFDJG

If it is running on HTTPS then refer: Note 461419.1

Make sure the ESB-DT application is running by issuing:
opmnctl status -app
For Eg: If it is running then it wil be listed like this
4513 | esb-dt | started | g_rt_id | internal-ESB | true | default

If it is not running which means the appliction is not installed properly or it is not been started.
Try to start the application:
Opmnctl startproc application=esb-dt
Remember if it is HA dont use restartproc, use startproc or stopproc.

To make it starts automatically everytime we restart the instance check these:

/oracle/SOA/SOA10gR3_HA/j2ee/OC4J_ESBDT/config/default-web-site.xml

/oracle/SOA/SOA10gR3_HA/j2ee/OC4J_ESBDT/config/server.xml

Courtesy : Thanks to Arun who wrote this note in Metalink.

After ESB Console starts and If Instances are not showingup then set TrackingEnabled=true

If you encounter following error:

Encountered following exception in log.xml
java.lang.NoClassDefFoundError: org/apache/log4j/Category))

The workaround is as follows -

Add the following line to the orion-application.xml file for esbdt

Restart the instance

JVM Tuning for SOA Suite Applications

2009-01-25T11:56:00.000+05:30

JVM Tuning for SOA Suite Applications :
1. General Considerations

JVM parameters play a major role in the BPEL engine's performance. The major factors that affect
performance relate to the heap size.

JVM Heap Size:
--------------------
The amount of heap required varies based on the application and on the available memory, for most
j2ee server applications containers, if you have sufficient memory, then it would be recommended
to use a heap size of 512 MB or larger.

To maximize performance, set the maximum heap size to accommodate application requirements and
make sure that the total memory consumed by all of the JVMs running on the system does not exceed
the memory capacity of your system.

Maximum heap size:
---------------------------
The maximum heap size controls how much memory the JVM can use. If your BPEL instance runs on a
dedicated machine, set this as high as the maximum addressable memory space of your Operating
System.

Determine the maximum heap size for yourplatform using one of the following methods:

1.On Windows you should set the max heap to 1300m and the min heap to 500m

2.Consult your platform vendor documentation/Web page for information regarding the maximum heap
size for your particular JVM version.

3.Determine the maximum heap using a binary search for your platform/JDK combination by running
Java from the command line and specifying the maximum heap. For example,

java -mx3000m -version

You may see a message similar to the following:

Error occurred during initialization of VM
Could not reserve enough space for object heap

In this case, decrease the maximum heap value until you do not get the error message (and the
version is displayed). You may wish to start by setting the maximum heap to 1000M.

For example:

a) Start at 1000M
b) If that works, set it to 3000M.
c) If 3000M doesn't work, set it to 2000M
d) Continue until you find your platform/JDK maximum heap size.

Once you have determined the maximum heap size, specify it in your Jserv.properties file such that
the Java maximum heap is either the platform maximum or 3GB, whichever is smaller.

For example, your Jserv.properties entry might be:

wrapper.bin.parameters=-Xms500M -Xmx -XX:NewSize=128M -XX:MaxNewSize=128M

In this example, substitute the actual value for .

For example:

wrapper.bin.parameters=-Xms500M -Xmx3000M -XX:NewSize=128M -XX:MaxNewSize=128M

Initial heap size:
--------------------
Sun Micro System recommends setting the initial (minimum) heap size to be equal to the maximum
heap size for optimal performance. The following option starts JVM with an initial heap size of 2GB:
-Xmx2048m -Xms2048m

Eden Space:
--------------------
Another important heap configuration are the garbage collector's generational settings. The
garbage collector optimizes collection by classifying objects by how long they live. Most of the
BPEL engine's objects are short lived, thus they live in the eden space. We recommend sizing the
eden space to be 60-70% of the total maximum heap size. The following command line starts Java
with a eden sizing that is 60% of the maximum heap size:
-Xmx2048m -Xms2048m –Xmn1228m

Survivor Ratio
------------------
The young generation consists of eden plus two equally sized survivor spaces. Objects are
initially allocated in eden. One survivor space is empty at any time, and serves as a destination
of the next, copying collection of any live objects in eden and the other survivor space. Objects
are copied between survivor spaces in this way until they are old enough to be tenured, or copied
to the tenured generation.

To size the survivors and eden generation the following options can be used:

allocate 6/8 to eden space and 1/8 to each survivor space

(allocated from -XX:NewSize=1228m -XX:MaxNewSize=1228m -XX:SurvivorRatio=6

Eden : 6/8 * 1228 = 921

Survivors : 1/8 * 1228 = 153 ( survivor 1 and 2 are of equal size )

Tenure : total heap - new size = 2048 - 1228 = 820

-Xmx2048m -Xms2048m –Xmn1228m -XX:NewSize=1228 -XX:MaxNewSize=1228m

-XX:SurvivorRatio=6

Permgen
--------------
The permanent generation holds data needed by JVM to describe objects that do not have an
equivalence at the Java language level. Eg: objects describing classes and methods.

The Permanent Generation is allocated outside of the heap.
- The defaults are typically too small for J2EE Applications.
- Also note, using certain java.lang.reflect can generate temporary class definitions that can
easily impact the permanent generation
- Consider setting –XX:MaxPermSize equal to –XX:PermSize to minimize major collections
-XX:MaxPermSize=128m –XX:PermSize=128m

Aggressive heap setting
---------------------------------
If your machine has multiple CPUs, it is recommended to use -XX:+AggressiveHeap JVM flag. The
-XX:+AggressiveHeap option inspects the machine resources (size of memory and number of
processors) and attempts to set various parameters to be optimal for long-running, memory
allocation-intensive jobs. The following option starts JVM with aggressive heap settings:
-Xmx2048m -Xms2048m –Xmn1228m –XX:+AggressiveHeap

GC Parameters to Help Tuning with Sun JVMs
---------------------------------------------------------------
-verbose:gc
-XX:+PrintGCDetails
-XX:+PrintHeapAtGC
-XX:+PrintTenuringDistribution

These will give the details for the tenuring distribution so you can see if you allocations are
working the way you expect.

Note : There are many factors which influence the JVM settings, not only the size of the RAM, but
also the other applications running on the same machine etc. Because all the memory and other
resources on a machine is not available to container running the SOA Suite. The Operating System
also needs some resources plus other servers and applications.Also within the single server there
are multiple JVM running. Depending on the type of install, in case of advanced installation a
minimum of two instances will be running - home, oc4j_soa. Even if you have ample of resources
still having a very large heap for the container to work with is counter productive because of
java Garbage collection. The larger the heap the more time it takes to do GC hence the impact on
performance.

For example, for a machine with 4GB there is not much space anyway, you can simply use one OC4J
instance with one JVM per component.

What you should consider is not exceeding -Xmx1024m per JVM running OC4J, but rather consider
scaling out to multiple JVMs.

ESB : oracle.tip.esb.console.exception.SchemaValidationException

2008-12-30T10:09:00.001+05:30

You deploy an esb project and try to view it via console, and get the following error :

oracle.tip.esb.console.exception.SchemaValidationException: The metadata XML that was processed does not comply with the ESB Metadata XML Schema. Cause: Invalid value '' for attribute: 'executionType'.
If you are manually editing the Import Files, ensure that the metadata is valid and well formed. Otherwise, this is an Internal Error.

Solution :
Add an attribute (executionType="Immediate") to the ESB routing service.

Exception on JaxRpc invoke: HTTP Transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException

2008-12-18T11:43:00.000+05:30

A Process (without any human task) is initiated and invoke a sync web service call. The system
returns the following error:
Exception on JaxRpc invoke: HTTP Transport error: javax.xml.soap.SOAPException:
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message Send failed:
Connection reset

After receiving this message, one minute later, another new process is initiated, and no error
returned.

Solution :

Fixed in Bug : 7445876

ORABPEL-09715 ERROR: exception symbol "09715" not found in resource file.

2008-12-18T11:36:00.000+05:30

You get the errors below when attempting to invoke a jsp using predicate worklist API :

08/10/20 18:59:49 ERROR: exception symbol "09715" not found in resource file.
08/10/20 18:59:49 ORABPEL-09715

08/10/20 18:59:49 at oracle.bpel.services.workflow.repos.Predicate.appendPredicateList(Predicate.java:808)
08/10/20 18:59:49 at oracle.bpel.services.workflow.repos.Predicate.appendPredicateList(Predicate.java:763)
08/10/20 18:59:49 at oracle.bpel.services.workflow.repos.Predicate.(Predicate.java:488)
08/10/20 18:59:49 at _testPredicate._jspService(_testPredicate.java:53)
08/10/20 18:59:49 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
08/10/20 18:59:49 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
08/10/20 18:59:49 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
08/10/20 18:59:49 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
08/10/20 18:59:49 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
08/10/20 18:59:49 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
08/10/20 18:59:49 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
08/10/20 18:59:49 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
08/10/20 18:59:49 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
08/10/20 18:59:49 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
08/10/20 18:59:49 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
08/10/20 18:59:49 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
08/10/20 18:59:49 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
08/10/20 18:59:49 at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
08/10/20 18:59:49 at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
08/10/20 18:59:49 at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
08/10/20 18:59:49 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
08/10/20 18:59:49 at java.lang.Thread.run(Thread.java:595)

Solution :

Apply 10.1.3.4 MLR # 3 : Patch 7586063

FTP Command: RETR, reply: 550 RETR Error

2008-12-18T11:34:00.000+05:30

You get the following error while reading pdf file from the FTP folder through FTP adapter in the bpel process:

FTP Command: RETR, reply:
550 RETR Error: IFS-32615: "/MySharedFolders/abc/AAAA_TR_Ba?ak Hyytt
gogorta A.?._555555.pdf": Path is invalid.

Unable to get Binary file '/MySharedFolders/abc/AAAA_TR_Ba?ak Hyytt
gogorta A.?._555555.pdf'; FTP command RETR returned une
xpected reply code : 550

Solution :

Configure serverEncoding as UTF-8 in oc4j-ra.xml.

Tuning JCA Connection Cache in BPEL PM & ESB

2008-12-15T12:00:00.000+05:30

Tuning JCA Connection Cache :

The JCA WSIF Provider supports a JCA Connection Cache, which resides in the JCA WSIFPort implementation class.

Normally the JCA Connection Cache (Pool) is boundless, but it can be capped (through a partnerlink property). If for example the max size is 10, and 15 concurrent threads are trying to invoke the same endpoint, 5 of them will throw a (retryable) remote fault. This Connection pool ensures single threading through JCA LocalTransactions.

For BPEL these properties are configured in bpel.xml. For ESB, they are configured in the .esbsvc file as Endpoint Properties, normally set via the ESB Console.

true

Normally this property is derived from the declared transactional support of the adapter (e.g. the File adapter does not this connection pool since it is multi thread safe),
but that can be overridden thru this property.

500

If this is not specified, is assumed. Applies on a per WSIFPort (partnerlink) basis.

50000

Maximum age of idle connections in the pool - important since some type of connections hold on to expensive external resources (e.g. DB shadow processes). Measured in ms.

10000

How often to perform the idle connection scan (measured in ms).

To entirely disable the JCA Connection Cache/Pool, you can configure the following Endpoint Property:

false

This will make the Adapter Framework acquire and release CCI connections for each adapter Interaction (invocation)

AIP-11052 constraint violation:SYS_C0011059 Error Importing the export.xml file in B2B Console

2008-12-11T15:15:00.000+05:30

You take a export of the any B2B testcase repository. When you try to import this export.xml in B2B Console, you might encounter this error on the console itself :

AIP-11052: Writing following objects: Endpoint failed due to following
constraint violation: SYS_C0011059

Solution:
Download and Apply the Patch 7457066, which is 10.1.2.3 MLR # 5 for B2B.

AIP-16001 When Validating the Trading Partner Agreement on B2B Console

2008-12-11T15:14:00.000+05:30

You try to validate the imported xml file using the “Validate” Button present at the top right part of the B2B Console and encounter the following errors :

An error occurred during validation.

1. Error -: AIP-16001: The model validation engine failed due to an internal system error.
2. Error -: AIP-11016: SQL error

Solution :
Apply Patch 6488268
When you validate it for the first time, you might get the same error. Then validate it for multiple times by refreshing the B2B Console
Now, you will see that the error disappears and validates the Trading Partner Agreement successfully.

Yet another Contribution of my GURU to the SOA Community

2008-10-19T09:20:00.000+05:30

I am so excited to quote this :)

http://www.soapatterns.com/ - My guru - Clemens Utschig is one of the main authors..

Hurray!!!!!! Looking forward to read it once published.

Error: ORABPEL-11947 - Enqueue Failed, SQL Wrapper Has Been Closed Using AQ Adapter

2008-08-29T11:07:00.000+05:30

While doing the stress test you get following error:

http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. -
- 0
-

Enqueue failed; nested exception is: ORABPEL-11947 Please examine the log file to determine the problem.

SQL wrapper has been closed!

Domain log shows following error

java.sql.SQLException: SQL wrapper has been closed!
at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_intercept(SQLBCELProxy.java:296)
at oracle_jdbc_driver_T4CPreparedStatement_Proxy.executeQuery()
at oracle.tip.adapter.aq.database.Queue.getEmptyCLOB(Queue.java:152)
at oracle.tip.adapter.aq.database.EnqueueObject.setCLOBElement(EnqueueObject.java:156)
at
oracle.tip.adapter.aq.database.MessageWriter.buildEnqueueObject(MessageWriter.java:1070)

On debugging using any of the data-source, transaction or jdbc debug options as below
-Ddatasource.verbose=true
-DDataSourceConnection.debug=true
-Djdbc.connection.debug=true
-Djdbc.debug=true
-Dtransaction.debug=true

You would see the following error as well
oracle.AQ.AQException: JMS-184: Queue object is invalid
at oracle.AQ.AQUtil.throwAQEx(AQUtil.java:167)
at oracle.AQ.AQOracleQueue.enqueue(AQOracleQueue.java:1028)
at oracle.tip.adapter.aq.database.MessageWriter.doEnqueue(MessageWriter.java:640)
at oracle.tip.adapter.aq.database.MessageWriter.enqueue(MessageWriter.java:381)
at oracle.tip.adapter.aq.database.MessageWriter.writeMessage(MessageWriter.java:343)
at oracle.tip.adapter.aq.outbound.AQEnqueuer.execute(AQEnqueuer.java:111

Solution
To implement the solution, please execute the following steps:

1. Add the cache properties in bpel.xml under the partner link tag
eg:
partnerLinkBinding ....
....
property name="retryInterval">120 property name="cacheWSIFOperation">true property name="retryMaxCount">10 property name="cacheConnections">false/partnerLinkBinding

2. Define a JCA connection pool in oc4j-ra.xml for the JNDI name which is being used by the
outbound AQ partnerlink.
eg:
connector-factory location="eis/AQ/aqSample" connector-name="AQ Adapter"
....
connection-pooling use="private"
property name="waitTimeout" value="300" /
property name="scheme" value="fixed_wait" /
property name="maxConnections" value="100" /
property name="minConnections" value="0" /

3. Use seperate datasource for reading or writing the queue.

ORABPEL-11430: ERROR IN LISTING FILES IN THE REMOTE DIRECTORY

2008-08-08T10:11:00.000+05:30

Issue :
bug 7234557 - ORABPEL-11430: ERROR IN LISTING FILES IN THE REMOTE DIRECTORY
where it states that "FTP Adapter does not supported nested folders" .
How to workaround the issue (except using a Outgoing Folder with no subfolders, as the cst has not control over the FTP server that he is using) ?

Fix:
Fixed in SOA Suite 11g

ESBRuntimeException: Designtime cache has not been initialized

2008-08-08T10:09:00.000+05:30

Issue :
Here is the Error Trace:

08/08/06 11:13:31 oracle.tip.esb.infra.exception.ESBRuntimeException: Designtime cache has not been initialized
Please look in logs for following signs of failure. Fix them and restart. (a) Database access errors (b) ESB Bootstrap errors (c) OC4J class load errors (d) Product installation errors (e) Export ESB params and verify if host and port parameters are correct. Please contact Oracle Support if unable to fix the issue.
08/08/06 11:13:31 at oracle.tip.esb.console.CacheManager.getInitializedInstance(CacheManager.java:319)
08/08/06 11:13:31 at oracle.tip.esb.console.XMLConsoleManagerImpl.(XMLConsoleManagerImpl.java:218)
08/08/06 11:13:31 at oracle.tip.esb.console.ConsoleManagerFactory.getConsoleManager(ConsoleManagerFactory.java:57)
08/08/06 11:13:31 at oracle.tip.esb.configuration.servlet.command.ServiceExplorerCommand.execute(ServiceExplorerCommand.java:45)
08/08/06 11:13:31 at oracle.tip.esb.configuration.servlet.CommandServlet.doJob(CommandServlet.java:109)
08/08/06 11:13:31 at oracle.tip.esb.configuration.servlet.CommandServlet.doPost(CommandServlet.java:76)
08/08/06 11:13:31 at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
08/08/06 11:13:31 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
08/08/06 11:13:31 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
08/08/06 11:13:31 at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
08/08/06 11:13:31 at java.security.AccessController.doPrivileged(Native Method)
08/08/06 11:13:31 at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
08/08/06 11:13:31 at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
08/08/06 11:13:31 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
08/08/06 11:13:31 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
08/08/06 11:13:31 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
08/08/06 11:13:31 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
08/08/06 11:13:31 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
08/08/06 11:13:31 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
08/08/06 11:13:31 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
08/08/06 11:13:31 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
08/08/06 11:13:31 at java.lang.Thread.run(Thread.java:595)

Solution :
It might be a server network issue.
However, I have logged a bug for it : 7273700 - which has the solution.

B2B Outbound Error -AIP-50014: General Error

2008-08-08T10:05:00.000+05:30

You have configured AS2 with signing and encryption. The inbound and synchronous MDN are working fine. However the outbound transactions fail with :

2008.08.07 at 19:03:31:401: Thread-10: B2B - (ERROR) java.lang.NullPointerException
at oracle.tip.adapter.b2b.packaging.mime.MimePackaging.pack(MimePackaging.java:101)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1628)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:931)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1092)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:698)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:375)
at java.lang.Thread.run(Thread.java:534)

Solution :
You might have mistyped additional space in the from party .

BPEL INSTALL FAIL - ORA-01017: invalid username/password; logon denied

2008-05-17T18:35:00.000+05:30

Q: You try fresh a BPEL install (for AS mid-tier) on Sun 10. Dehydration store would be an existing 10gR2 DB on a 11.5.10.2 apps instance.

Installed 10gAS 10.1.3.1 in a separate home. Before I install BPEL 10.1.3.1 for AS midtier, I am trying to run IRCA script for creation of ORABPEL schema/objects. (Since I am using existing DB option)
Here is the command being used to run IRCA script

$ ./irca.sh orabpel
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: ddas2271 1522 omimd101
Enter sys password: Running IRCA for orabpel product(s):
connection="ddas2271.dev.sprint.com 1522 omimd101", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

ERROR: Failed to establish database connection due to the following error:
ORA-01017: invalid username/password; logon denied

Please check your connection parameters and try again.

You have created the orapwd file with new password for 'sys' user with entries =10 and set the REMOTE_LOGIN_PASSWORDFILE parameter in initSID.ora to EXCLUSIVE, bounced the instance, listener. Still I keep getting the same error message

SOL : Issue might be with the location of the orapw file in the wrong location.
So, change it accordingly.

oracle.tip.esb.infra.exception.ESBRuntimeException

2008-05-17T18:32:00.000+05:30

Q : An ESB installation is raising next error when entering on the ESB Console and also during deployment:

Designtime cache has not been initialized Please look in logs for following signs of failure. Fix them and restart. (a) Database access errors (b) ESB Bootstrap errors (c) OC4J class load errors (d) Product installation errors (e) Export ESB params and verify if host and port parameters are correct. Please contact Oracle Support if unable to fix the issue.
Error shown in opmn/logs/default_group~home~default_group~1.log

08/04/15 12:13:14 oracle.tip.esb.infra.exception.ESBRuntimeException: No se ha inicializado la caché de tiempo de diseño
Consulte los siguientes signos de fallo en los logs. Corríjalos y reinicie. (a) Errores de acceso a la base de datos (b) Errores de inicialización de ESB (c) Errores de carga de clase de OC4J (d) Errores de instalación del producto (e) Exporte los parámetros de ESB y verifique si los parámetros de host y puerto son correctos. Póngase en contacto con los Servicios de Soporte Oracle si no puede corregir este problema. (same error in Spanish)
08/04/15 12:13:14 at oracle.tip.esb.console.CacheManager.getInitializedInstance(CacheManager.java:319)
08/04/15 12:13:14 at oracle.tip.esb.console.XMLConsoleManagerImpl.(XMLConsoleManagerImpl.java:218)
08/04/15 12:13:14 at oracle.tip.esb.console.ConsoleManagerFactory.getConsoleManager(ConsoleManagerFactory.java:57)
08/04/15 12:13:14 at oracle.tip.esb.configuration.servlet.command.ServiceExplorerCommand.execute(ServiceExplorerCommand.java:45)
08/04/15 12:13:14 at oracle.tip.esb.configuration.servlet.CommandServlet.doJob(CommandServlet.java:109)
08/04/15 12:13:14 at oracle.tip.esb.configuration.servlet.CommandServlet.doPost(CommandServlet.java:76)
08/04/15 12:13:14 at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
08/04/15 12:13:14 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
08/04/15 12:13:14 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
08/04/15 12:13:14 at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
08/04/15 12:13:14 at java.security.AccessController.doPrivileged(Native Method)
08/04/15 12:13:14 at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
08/04/15 12:13:14 at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
08/04/15 12:13:14 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
08/04/15 12:13:14 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
08/04/15 12:13:14 at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
08/04/15 12:13:14 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
08/04/15 12:13:14 at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
08/04/15 12:13:14 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
08/04/15 12:13:14 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
08/04/15 12:13:14 at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
08/04/15 12:13:14 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
08/04/15 12:13:14 at java.lang.Thread.run(Thread.java:595)

Solution :
#############
First turn up logging to "FINEST" on relevant ESB loggers using AS Control screens, restart the container, and see what ends up in the logs.
You need to check the correct IP in the hosts file and ensure that you point to the right hostname . If its wrong, then modify accordingly and then restart the AppServer.

FILE ADAPTER PICKING BASED ON ARRIVAL TIME

2008-04-10T10:08:00.000+05:30

Question:
###########
I am wondering how to get the file adapter to pick files from the inbound directory based arrival time if there is more than one file to pick up?

No matter I am setting the minimum age to 5 secs it still seems like that the File adapter is picking up files in alphabetic order if I copy more small files to the inbound directory.....

Solution :
###########
There is a patch available, please check 6445656.

You need to do two things:
i) Apply the patch
How do I guarantee ordering of messages processed by FileAdapter and BPEL

Even if you publish messages from the FileAdapter in a certain order, it does not guarantee the order in which BPEL would process these messages. In order to maintain message ordering, you will need to do the following:

i) Set oracle.tip.adapter.file.numProcessorThreads=1 (see FAQ entry "How do I configure number of threads for FileAdapter")

ii) Model the BPEL process as a synchronous FileAdapter BPEL process:

Normally the File adapter wizard only creates OneWay WSDLs so you will have to manually tweak it a little, i.e. modifying the generated WSDL so it becomes a Request-Response type WSDL with input and output messages.

For example:

Lets first create a XML schema type for the (dummy) Response (output) message.

targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/fileService/">

...

...
Then we define the WSDL message:

Now we can add an output message to the file read operation:

We also need to add an output element in the binding section:

Now the WSDL is OK.

In the BPEL Process you simply add a Reply activity as shown:

..

variable="Receive_1_Read_InputVariable" createInstance="yes">

[...]

[...]

Notice the use of a Correlation set on the Receive activity, which is needed establish/determine the FileReader partnerlink conversation ID. The Correlation property can be defined in the file read WSDL, e.g.

messageType="tns:records_msg" part="..." query="..."/>

Thus using a synchronous flow will guarantee ordering between the Receive and the Invoke right before the (first) Reply. Note - the process can still continue after the Reply if need be.

java.lang.OutOfMemoryError: unable to create new native thread

2008-04-08T16:13:00.001+05:30

ISSUE:
##########
java.lang.OutOfMemoryError: unable to create new native thread

SOLUTION :
#############
Amazingly, the overall JVM process memory layout is not documented by Sun Microsystems. But the heap and the native stack space basically contend for the memory allowed to the JVM process by the OS. The memory allowed to a process, and its layout, and its configuration, is OS-dependent. For HP-UX it’s well-documented in this presentation, according to which, increasing maxdsiz (as Ivan mentioned) allows more memory to the JVM process’s data region, which apparently contains both the java heap and the native stack space (and has nothing to do with swapping). But for other OSes, it’s different, and apparently much less documented.

Here are the resources on the general topic that I’ve been able to find. If anybody has any more resources on this general topic, please do share them.

* http://kbase.redhat.com/faq/FAQ_47_2747.shtm
* http://blogs.oracle.com/gverma/linux/kernel/memlimits
* http://blogs.oracle.com/gverma/java/kernel_limits
* http://www.odi.ch/weblog/posting.php?posting=411
* http://www.egilh.com/blog/archive/2006/06/09/2811.aspx

There is one more thing you can do in the situation of getting java.lang.OutOfMemoryError: unable to create new native thread, that you didn’t identify, which is to reduce the number of threads in the VM. For a BPEL system, that might mean reducing the number of WorkerBean threads, reducing the size of the OC4J HTTP thread pool, reducing the number of (clustered) adapter activations deployed to the BPEL node, etc.

As far as the best strategy for tuning the system to avoid this kind of OOME, I don’t think it’s a matter of tuning. Rather, it’s a matter of architecture. Like heap, or CPU cycles, or file handles, threads are a limited resource (for which native stack space is a proxy), which your architecture has to be careful not to exhaust. If you are getting this kind of OOME, and you can’t reduce the number of threads in the VM, or adjust heap or stack size to eliminate the condition, then it may be an indication that you have too much deployed to the VM, and you need to change your deployment architecture to reduce resource consumption per node.

I faced to the same issue some time ago and it was operating system configuration issue.
Environment was HP Unix and customer's system administrator just increased "maxdsiz" parameter and made enough disk space available for swapping.

SFTP STOPS LAUNCHING NEW INSTANCES

2008-04-08T16:10:00.001+05:30

ISSUE:
##########
I have a process based on the ftp adapter configured to use sftp without deleting the files.
After it was working fine for a while, it just stopped launching new instances.
I can see the following message in the log file repeating many times:

<2008-04-06 12:03:03,857> Connection Created
<2008-04-06 12:03:03,919> File :
/export/interfaces/ERP/DEV4BPEL/ITA/INT/EDI/IN/OM_ORDER_MANAGEMENT/TEMDEV/CURR//DafneORDERS.01.00000000000000981131.dat could not be fetched from source.
This does not affect processing !!

I can also see that the temporary files in $SOA/j2ee/home/fileftp/temp_ftp///inbound are created with size of 0.

SOLUTION:
############

You're probably hitting A Bug : 6691360

oracle.classloader.util.AnnotatedNoClassDefFoundError;ORABPEL-09903/ORABPEL-12510;ORABPEL-12510

2008-04-02T09:11:00.003+05:30

ERROR :
##########
<2008-03-27 09:16:51,506> Error while notifying observer class com.collaxa.cube.admin.adaptors.platform.PlatformAdaptor_oc4j_10g$1 with aspect class com.collaxa.cube.admin.observer.DomainInitAspect
oracle.classloader.util.AnnotatedNoClassDefFoundError:

The missing class is available from the following locations:

1. Code-Source: HOME/lib/dms.jar (from (ignore manifest Class-Path) in META-INF/boot.xml in HOME/j2ee/home/oc4j.jar)
This code-source is available in loader oracle.dms:3.0.

at oracle.classloader.PolicyClassLoader.handleClassNotFound (PolicyClassLoader.java:2068) HOME/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@27634497]
at oracle.classloader.PolicyClassLoader.internalLoadClass (PolicyClassLoader.java:1679) [/turkcell/bostbl/product/OracleAS_SOA/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@27634497]
at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1635) [/turkcell/bostbl/product/OracleAS_SOA/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@27634497]
at oracle.classloader.PolicyClassLoader.loadClass (PolicyClassLoader.java:1620) [/turkcell/bostbl/product/OracleAS_SOA/j2ee/home/lib/pcl.jar (from system property java.class.path), by sun.misc.Launcher$AppClassLoader@27634497]
at java.lang.ClassLoader.loadClassInternal (ClassLoader.java:319) [jre bootstrap, by jre.bootstrap:1.5.0_06]
Missing class: oracle.dms.instrument.Refresh
Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/DB/BoDatabase'
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the OC4J Application server or
2) the 'location' attribute in $J2EE_HOME/application-deployments/default/deployed-adapter-name/oc4j-ra.xml has not been set to eis/DB/BoDatabase. In the last case you might have to add a new 'connector-factory' entry (connection) to oc4j-ra.xml.
Please correct this and then restart the BPEL/OC4J Application Server

<2008-03-28 09:37:31,073>
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Caused by: ORABPEL-12517
AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
The Resource Adapter was unable to activate the endpoint :{} due to the following reason: ORABPEL-12510
Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/DB/BoDatabase'
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the OC4J Application server or
2) the 'location' attribute in $J2EE_HOME/application-deployments/default/deployed-adapter-name/oc4j-ra.xml has not been set to eis/DB/BoDatabase. In the last case you might have to add a new 'connector-factory' entry (connection) to oc4j-ra.xml.
Please correct this and then restart the BPEL/OC4J Application Server
Caused by: ORABPEL-12510
Unable to locate the JCA Resource Adapter via WSDL port element jca:address.
The Adapter Framework is unable to startup the Resource Adapter specified in the WSDL jca:address element: {http://xmlns.oracle.com/pcbpel/wsdl/jca/}address: location='eis/DB/BoDatabase'
The reason for this is most likely that either
1) the Resource Adapters RAR file has not been deployed successfully to the OC4J Application server or
2) the 'location' attribute in $J2EE_HOME/application-deployments/default/deployed-adapter-name/oc4j-ra.xml has not been set to eis/DB/BoDatabase. In the last case you might have to add a new 'connector-factory' entry (connection) to oc4j-ra.xml.
Please correct this and then restart the BPEL/OC4J Application Server
ORABPEL-09903

Could not initialize activation agent.
An error occured while initializing an activation agent for process "BO_EXT_DUAL_UPDATE_CHECKER_PROCESS", revision "1.0".
Please ensure that the activation agents are configured correctly in the bpel deployment descriptor (bpel.xml).
oracle.tip.adapter.fw.agent.jca.JCAActivationAgent: java.lang.reflect.InvocationTargetException

SOLUTION:
############
Please open your 10.1.3.1\OracleAS_2\j2ee\oc4j_soa\config\server.xml and see if you have

tag present.
I strongly believe that this tag is missing. So, have this tag in place and then bounce the
server. This should fix your issue.
####################################
$$$

$$$$$$$$$

ORABPEL-09500 ora:readFile

2008-02-19T12:51:00.000+05:30

Apply Patch 5926809

AIP - 18506 in Oracle B2B

2008-02-08T13:22:00.000+05:30

Restart the Metadata Repository i.e. Infra compoenents

org.apache.slide.structure.ObjectNotFoundException in ESB

2008-02-07T09:42:00.000+05:30

140.85.97.27:9806:1202156237991:50
>
>
> *WSDL Parsing failed due to
> :org.apache.slide.structure.ObjectNotFoundException: No object found
> at /files/ESB_Projects/WPIMCSApps_APTxStatusListener/https:
>
>
>
140.85.97.27:9806:1202156237991:50
>
>
> *WSDL parsing failed :WSDL Parsing Failed:
> org.apache.slide.structure.ObjectNotFoundException: No object found at
> /files/ESB_Projects/WPIMCSApps_APTxStatusListener/https:
> > org.apache.slide.structure.ObjectNotFoundException: No object found at
> /files/ESB_Projects/WPIMCSApps_APTxStatusListener/https::
> java.lang.RuntimeException:
> org.apache.slide.structure.ObjectNotFoundException: No object found at
> /files/ESB_Projects/WPIMCSApps_APTxStatusListener/https:
> * at
> oracle.tip.esb.server.bootstrap.protocol.esb.ESBURLConnection.connect(Unknown
> Source)
> at
> oracle.tip.esb.server.bootstrap.protocol.esb.ESBURLConnection.getInputStream(Unknown
> Source)
> at java.net.URL.openStream(URL.java:1007)
> at oracle.tip.esb.utils.WSDLUtil.parseWSDL(WSDLUtil.java:125)
> at
> oracle.tip.esb.model.entity.Service.loadWSDLOperations(Service.java:128)
> at
> oracle.tip.esb.model.entity.ServiceOperation.getWSDLOperation(ServiceOperation.java:92)
> at
> oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:199)
> at
> oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
> at
> oracle.tip.esb.server.dispatch.DeferredEventDispatcher.processSubscriptions(DeferredEventDispatcher.java:150)
> at
> oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
> at
> oracle.tip.esb.server.dispatch.DeferredEventDispatcher.dispatch(DeferredEventDispatcher.java:67)
> at
> oracle.tip.esb.server.dispatch.agent.JavaDeferredMessageHandler.handleMessage(JavaDeferredMessageHandler.java:115)
> at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:162)
> at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:120)
> at
> oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
> at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
> at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
> at
> EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.slide.structure.ObjectNotFoundException: No
> object found at /files/ESB_Projects/WPIMCSApps_APTxStatusListener/https:
> at
> org.apache.slide.store.txfile.AbstractXMLResourceDescriptor.retrieveObject(AbstractXMLResourceDescriptor.java:287)
> at
> org.apache.slide.store.txfile.TxXMLFileDescriptorsStore.retrieveObject(TxXMLFileDescriptorsStore.java:104)

Solution :
###############
Apply Merge Patch 6439295 on top of 10.1.3.3

ORABPEL-11038 - Control File not found while batching

2008-02-07T09:32:00.000+05:30

You are trying to follow File Adapter Control Files from the link available :

http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter_TN_001_FileAdapter_ControlFiles.pdf

You encounter an error :
####################

Could not invoke operation 'Write' against the 'File Adapter' due to:
ORABPEL-11038
Control File not found while batching.
Control File not found while batching

Solution :
############
Remove the following lines from your wsdl and then it should be fine: NumberMessages="1"
ElapsedTime="60"
FileSize="1024000"

JDEVELOPER 10.1.3.३ CONNECTING to R12 APPS MODULE

2008-01-29T13:03:00.000+05:30

You will not be able to create an irep file sometime when trying to connect to Oracle Apps R12 using JDeveloper 10.1.3.3.

Solution;
###########
Shutdown JDev first, add "AddVMOption -Duser.language=en", "AddVMOption -Duser.region=us" in jdev.conf then you will see the EBS object.

( OR )

Use JDeveloper 10.1.3.1.0

ORABPEL-02152

2008-01-29T12:59:00.000+05:30

Error while invoking bean "instance manager": [com.collaxa.cube.engine.core.InstanceNotFoundException: Instance not found in datasource.
The process domain was unable to fetch the instance with key "1220001" from the datasource.
Please check that the instance key "1220001" refers to a valid instance that has been started and not removed from the process domain.
]
ORABPEL-02152

Instance not found in datasource.
The process domain was unable to fetch the instance with key "1220001" from the datasource.

SOLUTION :
###################
Apply patch : 6725374 - 10.1.3.3

BPEL - B2B Integration - Message Tracking

2008-01-07T16:52:00.000+05:30

@ To create outbound process to send data from BPEL to Integration B2B and send
@ out to remote
@ trading partner. Please see the attached files as process to create BPEL
@ project. When testing the
@ BPEL process, the data didn't reach the Integration B2B (I check at
@ Business Message Status Report
@ at Integration B2B Control). And I don't know how to check the data in
@ ip_out_queue of Oracle AQ.
@ .
@ But, we are not able to see any reports on the b2b console and also not able
@ to track the messages being received and sent to/from B2B .
@ How do we get the status messages and reports in the IP_IN_QUEUE and
@ IP_OUT_QUEUE ?
###################
Solution :
************
a. Apply Patch for Bug 6656289 for B2B, Set the
oracle.tip.adapter.b2b.qMsgRatio=20 or to suitable Value.
b. Set Suitable Value for EXPIRE_TIME in B2B_BATCH_EVENT(Follow Metalink Note
460057.1)

ORABPEL-05244 - Timed out waiting for process load lock.

2007-12-26T12:16:00.000+05:30

<2007-04-30 15:12:23,912>

Error while invoking bean "process manager": Timed out waiting for process load
lock.
Failed to obtain load lock for process "test_debmas01-1.0"; timed out after
150,000 seconds.
ORABPEL-05244
Timed out waiting for process load lock.
Failed to obtain load lock for process "test_debmas01-1.0"; timed out after
150,000 seconds.
at com.collaxa.cube.engine.deployment.LockManager.acquire(LockManager.java:89)
at com.collaxa.cube.engine.deployment.LockManager.acquire(LockManager.java:62)
at
com.collaxa.cube.engine.deployment.DeploymentManager.getProcess(DeploymentManager.
java:351)
at
com.collaxa.cube.engine.deployment.DeploymentHelper.lookupProcess(DeploymentHelper
.java:247)
at
com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getMetaData(BPELProcessManagerBea
n.java:224)

Solution :
###############
Resolve a lock timeout error as follows:
■ Increase the lock timeout value through the Java system property
orabpel.process.lock.timeout. This property can be set from the OPMN
start command by specifying -Dorabpel.process.lock.timeout=300 (the
unit is seconds).
■ If you still receive a lock timeout even with extremely large timeout values, a
writer thread is most likely stuck. To determine what the writer thread is doing,
try to obtain several thread dumps while the readers are blocking attempts to
acquire the lock (perform Ctrl-Break on Windows or kill -3 on UNIX).

ORABPEL-11430 & ORABPEL-11400

2007-12-26T08:58:00.000+05:30

<2006-08-08 18:16:39,531> FTPClient.listNames(): unexpected 550 is encountered.
<2006-08-08 18:16:39,531> Error retrieving polled files.
<2006-08-08 18:16:39,531>
ORABPEL-11430
Error in listing files in the remote directory.
Unable to list file in remote directory.
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.

at oracle.tip.adapter.ftp.FTPClient.listFiles(FTPClient.java:598)
at oracle.tip.adapter.ftp.FTPAgent.getFileList(FTPAgent.java:272)
at oracle.tip.adapter.file.inbound.FileSource.getFileList(FileSource.java:199)
at oracle.tip.adapter.file.inbound.PollWork.pollFiles(PollWork.java:217)
at oracle.tip.adapter.file.inbound.PollWork.run(PollWork.java:118)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)

Fix :
##############
Patch 4508850

How does NonBlocking Invoke work in BPEL 10.1.३.3

2007-12-19T09:39:00.000+05:30

A sync bpel process, would not rehydrate unless it completes its entire callback process.
But, what if we need to dehydrate it using some breakpoint?
Yes, we can do it - we can have breakpoints in a sync process i.e. have a wait activity and then dehydrate it. This is called a durable transient bpel process.
But, consider a scope, which has several sync processes which cannot execute at once.
This is because BPEL follows pseudo-parallelism.
So, we Nonblocking Invoke mechanism, which ensure that it stores the messages in the JMQ Q, hereby ensuring that many process but wait for the reply back messages on time. This would reduce the time latency.

This Nonblocking Invoke mechanism is meant for two-way processing i.e. sync processes.

How to force Rollback in अ JTA transaction in BPEL 10.1.३.3

2007-12-19T09:25:00.000+05:30

Basically, all transactions in BPEL 10.1.3.3 are JTA transactions. We cant dehydrate the process easily in a asyc process, but what about an syc process?
This is a challenge when it comes to big sync processes. So, we need a forceful rollback when the process fails and throw an fault.
Here is scenario :
#################
client - > sends message -> - > -> syc invoke - > [ -> ] - > This transaction marked in [] rollback.
**********************
But, it rollbacks only when transaction=participate property is set in the PL.
Else, the process dehydrates and gets saved.

Threading in Oracle BPEL PM 10।1.3.३ - dspMaxThreads

2007-12-19T09:10:00.000+05:30

We need to know the relationship between ReceiverThreads and dspMaxThreads.
ReceiverThreads property specifies the maximum number of MDBs that process aysc across all domains. Whereas the dspMaxThreads are the maximum number of MDBs that process asy and threads that operate across a domain.
So, we need to ensure that the dspMaxThreads value is !> ReceiverThreads.
Actually, the dispatcher sends the messages to JMS Q, then the WorkerBean MDBs fetch them from the pool.
dspInvokeAllocFactor Property must ideally be 0.4 for less throttling of the properties and the above properties can be set in orion-ejb-jar.xml file.

Addressing the audience and eminent professionals

2007-10-06T19:47:00.000+05:30

.net Platform Evangelism

2007-10-06T19:31:00.000+05:30

Microsoft Ambassador & Platform Evangelist

2007-10-06T16:10:00.000+05:30

ORABPEL-11622 ऎंड ORABPEL-08033

2007-09-07T11:36:00.000+05:30

Errors :
***************
<2007-09-06 13:34:11,908> file:/dnbusr1/oracle/product/10.1.3.1/OraBPELJ2EE/bpel/domains/iedwmqa/tmp/.bpel_TNextGenProcess_1.0_1417034df84825571441aacdc693af30.tmp/PublishSSRService.wsdl [ PublishSSRMessage_ptt::PublishSSRMessage(SSRMessage) ] - Rolling back JCA LocalTransaction
<2007-09-06 13:34:12,052> unable to build the TopLink Session

<2007-09-06 13:34:12,053> unable to execute the outbound update operation on: UpdateSSSRService.UvrfdOrg

<2007-09-06 13:34:12,054> file:/dnbusr1/oracle/product/10.1.3.1/OraBPELJ2EE/bpel/domains/iedwmqa/tmp/.bpel_TNextGenProcess_1.0_1417034df84825571441aacdc693af30.tmp/UpdateSSSRService.wsdl [ UpdateSSSRService_ptt::update(UvrfdOrgCollection) ] - Could not invoke operation 'update' against the 'Database Adapter' due to: ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Transaction has been marked for rollback: Timed out]
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-23005] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.TransactionException
Exception Description: Error binding to externally managed transaction
Internal Exception: javax.transaction.RollbackException: Transaction has been marked for rollback: Timed out.

<2007-09-06 13:34:12,054> file:/dnbusr1/oracle/product/10.1.3.1/OraBPELJ2EE/bpel/domains/iedwmqa/tmp/.bpel_TNextGenProcess_1.0_1417034df84825571441aacdc693af30.tmp/UpdateSSSRService.wsdl [ UpdateSSSRService_ptt::update(UvrfdOrgCollection) ] - Rolling back JCA LocalTransaction
07/09/06 13:34:12 ----------------- __callback Caught Exception class com.collaxa.cube.ws.WebServiceException
<2007-09-06 13:34:12,055> Error while invoking bean "cube delivery": EJB Transaction Error.
EJB exception happened while invoking the partner.
Please verify partner service.

ORABPEL-08033

EJB Transaction Error.
EJB exception happened while invoking the partner.
Please verify partner service.

at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:576)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:416)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:222)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:736)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:371)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:195)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3271)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1697)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:184)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:269)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5244)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1083)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:530)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.evermind.server.ThreadState.runAs(ThreadState.java:622)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.collaxa.thirdparty.apache.wsif.WSIFException: file:/dnbusr1/oracle/product/10.1.3.1/OraBPELJ2EE/bpel/domains/iedwmqa/tmp/.bpel_TNextGenProcess_1.0_1417034df84825571441aacdc693af30.tmp/UpdateSSSRService.wsdl [ UpdateSSSRService_ptt::update(UvrfdOrgCollection) ] - WSIF JCA Execute of operation 'update' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Transaction has been marked for rollback: Timed out]
; nested exception is: ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Transaction has been marked for rollback: Timed out]
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-23005] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.TransactionException
Exception Description: Error binding to externally managed transaction
Internal Exception: javax.transaction.RollbackException: Transaction has been marked for rollback: Timed out.

at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:631)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:726)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:425)
... 57 more
Caused by: ORABPEL-11622

Solution :
%%%%%%%%%%%%%%%%%%%%%
it looks like the jms operation failed with a time-out, so that the global transaction was marked for rollback. When attempting to do an update to dbadapter in this error scenario, it fails to bind to the global transaction because it is marked for rollback. I.e. there is no way the update can succeed as part of this doomed transaction.

One idea would be to use a non-XA instance to perform the update, which does not depend on the state of the global transaction. For this you could edit $J2EE_HOME/application-deployments/default/DbAdaper/oc4j-ra.xml and set dataSourceName instead of what you are currently setting, which is xADataSourceName. Then make sure that the matching data-sources.xml entry has the tx-level="local" property set.

A better idea would be to increase the transaction timeout, and/or find out why the jms publish is failing.

Also it seems like you want to reprocess the row on failure, so you are trying to update the row so that it will be picked up again. Another way to do this would be to perform a synchronous post from the polling DBAdapter to BPEL. In this case if the bpel process instance fails, all work including that of the polling dbadapter will be automatically rolled back.

Please see the sample samples/tutorials/122.DBAdapter/advanced/endToEnd/DirectSQLPerformance/README.txt for instructions on how to do this. You may also want to set NumberOfThreads > 1.

Exception : ORABPEL-11168

2007-09-07T11:31:00.000+05:30

Question:
****************
file adapter takes an input file with the following contents:

=== start ====
abc,abc,abc
<-- blank line
=== end ====

The blank line causes an error when being processed by BPEL:

/Exception=ORABPEL-11168

Error while reading native data.
[Line=2, Col=1] Expected "," for the data starting at the specified position/
/... etc.../

Is there any way of allowing empty lines in the input file to be ignored?

Answer
***************
If your csv file has trailing blank lines, then you can use the array contruct..
For example, if your csv has atleast 2 trailing blank lines.

How to submit large payloads to BPEL

2007-09-07T11:28:00.000+05:30

Open the xsd file and add the following code :

maxOccurs="unbounded"/>

.
Re-Deploy BPEL Process and initiate the BPEL Process using SOAP/Java Delivery
API, using XML Source.

Will the synchronous messages show up at the Recovery page - Rejection Handlers

2007-08-18T18:38:00.000+05:30

BPEL will not save the synchronous processes to the invoke_message or dlv_message tables therefore they will never show up at the Recovery page. In the case of server shutdown/crash or transaction time out, errors or exceptions are going to be returned to the caller and the caller can decide what action to take.

In a case where the 'caller' is an Adapter, say JMS Adapter, the rejected message is handle by a configurable "Rejection Handler". The default rejection handler will put the rejected messages into a file under orabpel/domain/.

rejectedMessageHandlers

This setting lets you configure your BPEL process to process the correct records of a file and write only the rejected records to an archive directory by setting the rejectedMessageHandlers parameter in the bpel.xml file.
Correct. However, the "Rejection handlers" come in four different flavors.

(Note: all the following bpel.xml properties must be defined as Activation Agent properties, for example

partnerLink="inboundPL">

file://C:/orabpel/samples/test/errorTest/rejectedMessages

so they only apply to Inbound (WSDL) operations (~ BPEL Receive).

--------------------------------------------------------------------------------

File system based Rejection Handler

file://

for example

file://C:/orabpel/domains/default/rejectedMessages

This rejection handler is straight forward - bad messages are written to the configured directory - using the file name pattern

INVALID_MSG_ + + +

--------------------------------------------------------------------------------

RAW Oracle Advanced Queue based Rejection Handler

queue://jdbc:oracle:thin:@::|/|

( can be encrypted) for example

queue://jdbc:oracle:thin:@acme-sun:1521:ORCL|scott/tiger|JCA_BAD_MESSAGES

This rejection handler allows the user to designate a Oracle Rdbms RAW AQ queue as the rejection storage. Note that the ":" and "|" must appear in the places shown. Also note that the password can be encrypted using the encrypt.bat utility in orabpel/bin.

--------------------------------------------------------------------------------

BPEL Process Rejection Handler

bpel://]>|||

( for domain if not "bpel" - can be encrypted - "[]" means optional)

for example

bpel://default|JCA-RejectionHandler|handleRejection|message

This rejection handler will send the bad message to another (designated error handling) BPEL process. The user can thus define a process with a Receive operation of his own choosing (WSDL and BPEL src) - the only constraint is on the Message Type of the message that will be sent to this rejection handler. It must be declared to have the type "RejectedMessage". This can conveniently be achieved by importing the "xmllib" resident WSDL "RejectionMessage.wsdl" which defines such a message:

An xmllib WSDL import (from another WSDL) is achieved using the "well-known" URL

location="http://localhost:9700/orabpel/xmllib/jca/RejectionMessage.wsdl"/>

i.e. the Receive operation WSDL which the user defines for his Rejection Handler BPEL Process would simply contain this import and then the port type would reference this:

xmlns:rej="http://xmlns.oracle.com/pcbpel/rejectionHandler"

--------------------------------------------------------------------------------

WSIF Based Rejection Handler

wsif://||

for example

wsif://file:/C:/orabpel/samples/test/ErrorTest/FileAdapterWrite.wsdl|write|message

This last rejection handler lets the user configure any type of WSIF WSDL (JCA, EJB, JMS, HTTP, Java etc), i.e. any kind of Service which can be reached via WSIF - as the bad message handler. The exact same constraint vis-a-vis the Message Type as described above for the BPEL Process Rejection Handler also applies here.

--------------------------------------------------------------------------------

Adapter Fatal Error Failover BPEL Process

bpel://]>|||

( for domain if not "bpel" - can be encrypted - "[]" means optional)

for example

bpel://default|JCA-FatalErrorHandler|handleError|message

When an Adapter detects a disastrous, unrecoverable situation (no more memory, file handles, disk space or something similar) it can instruct the Adapter Framework to shut down the BPEL process which "owns" the Adapter Endpoint Activation. To activate some kind of compensating BPEL Process, the user can configure this bpel.xml Activation Agent property.

Again, as for the BPEL Process Rejection Handler, the Fatal Error BPEL Process must use a Message Type as described above. However, in this case, the Message Type is defined in FatalErrorMessage.wsdl so the Fatal Error WSDL should import

location="http://localhost:9700/orabpel/xmllib/jca/FatalErrorMessage.wsdl"/>

I saw error ORABPEL-05002 from domain.log, what should I do?

2007-08-18T18:36:00.000+05:30

I saw error ORABPEL-05002 from domain.log, what should I do?
<2005-12-20 17:34:42,139>
Failed to handle dispatch message ... exception ORABPEL-05002

Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage";
the exception is: Transaction was rolled back: timed out;
nested exception is: java.rmi.RemoteException:
No Exception - originate from:java.lang.Exception: No Exception - originate from:; nested exception is:
java.lang.Exception: No Exception - originate from:
A: These are the possible cause to the problem and their solutions:

Poor performance of the dehydration database If you are using Oracle Lite as dehydration store, please switch to use Oracle 9i or 10g. If Oracle 9i/10g is already in use, check the database parameter 'process' and 'session' to make sure it can handle the expected throughput.
OC4J has too few available connections to the dehydration database. In crease the maxConnection number of the BPELServerDataSource at the BPEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml (for developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/data-sources.xml (mid-tier installation).
Size of message is too big Two ways to deal with this problem:
Increase the transaction timeout at PEL_HOME/integration/orabpel/system/appserver/oc4j/j2ee/home/config/server.xml (developer edition) or IAS_HOME/j2ee/OC4J_BPEL/config/server.xml (mid-tier installation)
Decrease the auditLevel from BPELConsole -> Manage BPEL Domain -> Configurations tab. Doing so will reduce the amount of data saved to the dehydration store.

BPEL Installation And Configuration FAQ

2007-08-18T18:35:00.000+05:30

Can we install multiple orabpel schema in single DB?
Yes, this should work, however the IRCA script won't do it for you. But you can create a separate tablespace, user, ect and install the schemas there "manually". This is the same process which people use for non-Oracle DBs anyway, so it shouldn't be too painful. I suspect QA doesn't specifically test it, however, so you may not want to do it unless necessary.

Can we have one orabpel schema supporting many application environments?
Yes. As we discussed, you can either do this with a single BPEL "domain" where all the environments would share the same logical process sandbox. Or you can use multiple domains to separate the processes and instances. Different domains can either share the same orabpel schema (as you ask here) or have separate schemas.

Is it mandatory now or in future to install orabpel schema in the same DB as meta data repository?
In BPEL PM 10.1.2.0.0 (current release) orabpel schema must be separate from the infrastructure DB. In 10.1.2.0.2, we are part of the infrastructure DB. However, at that point you could still manually install the Orabpel schema somewhere else if you choose. Again, per #1 above, this may not be a standard configuration that QA tests, but it should work and we would support you with it.

Is it possible to integrate the BPEL console with OID for single sign on?
A: Not out of the box in 10.1.2. This is high in the list in 11. For 10.1.2, you can turn off the console authentication and apply your own separate authentication mechanism. Authentication is easy because the console is just a web app. However this does not provide access control and different level of privileges. These will be supported by the AS11 release.

Does BPEL PM support RAC DB? What versions of Oracle DB are supported?
A: Yes, RAC is supported for the BPEL PM dehydration store and for the DB and AQ adapters. Any version or Oracle 9i or 10g would work. We would recommend a RAC configuration of 10g if someone wants high availability, however. To configure BPEL PM 2.1.2 and 10.1.2 with RAC, use the following instructions:

for BPEL PM 2.1.2 and 10.1.2 just configure DataSource (orabpel\system\appserver\oc4j\j2ee\home\config\data-sources.xml) like this:

Name: BPELServerDataSource
Class: com.evermind.sql.DriverManagerDataSource
URL: jdbc:oracle:thin:@(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dwebvip01)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = dwebvip02)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA=(SERVER = DEDICATED)(SERVICE_NAME = asdb)))
Driver: oracle.jdbc.OracleDriver
Location: jdbc/BPELServerDataSource
XA location: BPELServerDataSource
EJB location: jdbc/BPELServerDataSource
inactivity-timeout: 300
retry interval: 2
max-connect-attempts: 60
max conn: 60
min conn: 12
For 10g RAC and implicit connection caching (jdbc 10g R1), all the following are valid ULRS:

Valid Usage:
url="jdbc:oracle:oci:@TNS_ALIAS"

url="jdbc:oracle:oci:@(DESCRIPTION=
(LOAD_BALANCE=on)
(ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=service_name)))"

url="jdbc:oracle:oci:@(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST=cluster_alias) (PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=service_name)))"

url = "jdbc:oracle:thin@//host:port/service_name"

url = "jdbc:oracle:thin@//cluster-alias:port/service_name"

url="jdbc:oracle:thin:@(DESCRIPTION=
(LOAD_BALANCE=on)
(ADDRESS=(PROTOCOL=TCP)(HOST=host1) (PORT=1521))
(ADDRESS=(PROTOCOL=TCP)(HOST=host2)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=service_name)))"

url = "jdbc:oracle:thin:@(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST=cluster_alias) (PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=service_name)))"

Invalid Usage:
url = "jdbc:oracle:thin@host:port:SID"

The BPEL PM DB and AQ adapters have been certified with 32-bit RAC configuration as well and certification was occurring as of 4/25/2005 for 64-bit RAC.

What are the install options for BPEL 10.1.3 and SOA Suite 10.1.3?
A: First a bit of background information from the previous version... In BPEL 10.1.2 there were two installation options: developer install and middle-tier install.

The developer install gave you everything you needed to start work as soon as the installation was complete. Namely, OC4J, the BPEL Process Manager, Oracle Lite for the dehydration store (already configured), JDeveloper already configured with the BPEL designer plugin.

The middle-tier install was intended for deployment environments. It installed BPEL Process Manager into an Application Server that was already installed and configured. You also had to have a database already configured with the BPEL schema. No design time components were installed.

For 10.1.3 there are two broad ways to install the product. You can install the entire SOA Suite or you can do individual component installations (BPEL, ESB, etc).

If you do a component installation, then that works similarly to 10.1.2. i.e. You can choose between a developer install or a middle-tier install. But unlike the previous version, you don't get JDeveloper installed for you. You need to download it and install it separately. You then need to install the BPEL/ESB Designer plugin (which is included with JDeveloper).

SOA Suite 10.1.3 is different. In summary, you get an Oracle Application Server and all of the SOA components (BPEL, ESB, Rules, etc). The installer gives you two options. (Actually there are more. Since we use the Oracle Application Server installer which has many install options, we have inherited those. But for the SOA Suite install there are only really two install options that we care about.)

Option 1: Basic Install

This is a one-click installation. You can only choose location of the ORACLE_HOME to install to, and the administration password.

You get an Oracle Application Server, but not with the Apache web server/listener. It uses the OC4J listener. You get all of the SOA components. You get Oracle Lite installed and configured with the SOA schemas (BPEL dehydration store, tables for ESB, etc).

Again, you don't get JDeveloper, which means you don't get any design-time elements for components that use JDeveloper (like BPEL and ESB). Other components with their own design time screens are included (like Rules). You will need to install JDeveloper separately, and then install the BPEL and ESB plugins. The SOA Suite installer contains instructions for that.

Option 2: Advanced Install

You get Oracle Application Server with Apache as the web server/listener. You will need to have an Oracle DB already installed and configured with the SOA schemas. (The installer will ask for the connection information to the database during the installation.)

Summary

For individual component installations, the install experience is similar to the previous version, except you have to install JDeveloper yourself.

For SOA Suite 10.1.3, there is no developer install and no middle-tier install. You will get the middle tier no matter what you do. If you want to install into an existing installation of the Application Server, then you cannot use the SOA Suite installer. You must use the individual component installers and choose the middle-tier install option.

Calling a PL/SQL procedure with a collection parameter इन JDeveloper 10.1.3.3

2007-08-02T16:24:00.000+05:30

(1)Create a dummy variable of the same type as the target PL/SQL collection parameter
(2)Create a While activity that runs through the source XML
(3)For every element in the XML, do an Assign Copy to the dummy variable
(4)For every element in the XML, do an Assign Append of the dummy variable to the PL/SQL colllection

Remove-नामेस्पसस इन अन क्ष्म्ल्

2007-07-16T18:02:00.000+05:30

http://www.tei-c.org/wiki/index.php/Remove-Namespaces.xsl#Required_Input

रेजेक्तिओन्हन्द्लिन्ग् इन BPEL

2007-06-09T18:58:00.000+05:30

rejectedMessageHandlers

This setting lets you configure your BPEL process to process the correct records of a file and write only the rejected records to an archive directory by setting the rejectedMessageHandlers parameter in the bpel.xml file.
Correct. However, the "Rejection handlers" come in four different flavors.

(Note: all the following bpel.xml properties must be defined as Activation Agent properties, for example

partnerLink="inboundPL">

file://C:/orabpel/samples/test/errorTest/rejectedMessages

so they only apply to Inbound (WSDL) operations (~ BPEL Receive).

--------------------------------------------------------------------------------

File system based Rejection Handler

file://

for example

file://C:/orabpel/domains/default/rejectedMessages

This rejection handler is straight forward - bad messages are written to the configured directory - using the file name pattern

INVALID_MSG_ + + +

--------------------------------------------------------------------------------

RAW Oracle Advanced Queue based Rejection Handler

queue://jdbc:oracle:thin:@::|/|

( can be encrypted) for example

queue://jdbc:oracle:thin:@acme-sun:1521:ORCL|scott/tiger|JCA_BAD_MESSAGES

This rejection handler allows the user to designate a Oracle Rdbms RAW AQ queue as the rejection storage. Note that the ":" and "|" must appear in the places shown. Also note that the password can be encrypted using the encrypt.bat utility in orabpel/bin.

--------------------------------------------------------------------------------

BPEL Process Rejection Handler

bpel://]>|||

( for domain if not "bpel" - can be encrypted - "[]" means optional)

for example

bpel://default|JCA-RejectionHandler|handleRejection|message

This rejection handler will send the bad message to another (designated error handling) BPEL process. The user can thus define a process with a Receive operation of his own choosing (WSDL and BPEL src) - the only constraint is on the Message Type of the message that will be sent to this rejection handler. It must be declared to have the type "RejectedMessage". This can conveniently be achieved by importing the "xmllib" resident WSDL "RejectionMessage.wsdl" which defines such a message:

An xmllib WSDL import (from another WSDL) is achieved using the "well-known" URL

location="http://localhost:9700/orabpel/xmllib/jca/RejectionMessage.wsdl"/>

i.e. the Receive operation WSDL which the user defines for his Rejection Handler BPEL Process would simply contain this import and then the port type would reference this:

xmlns:rej="http://xmlns.oracle.com/pcbpel/rejectionHandler"

--------------------------------------------------------------------------------

WSIF Based Rejection Handler

wsif://||

for example

wsif://file:/C:/orabpel/samples/test/ErrorTest/FileAdapterWrite.wsdl|write|message

This last rejection handler lets the user configure any type of WSIF WSDL (JCA, EJB, JMS, HTTP, Java etc), i.e. any kind of Service which can be reached via WSIF - as the bad message handler. The exact same constraint vis-a-vis the Message Type as described above for the BPEL Process Rejection Handler also applies here.

--------------------------------------------------------------------------------

Adapter Fatal Error Failover BPEL Process

bpel://]>|||

( for domain if not "bpel" - can be encrypted - "[]" means optional)

for example

bpel://default|JCA-FatalErrorHandler|handleError|message

When an Adapter detects a disastrous, unrecoverable situation (no more memory, file handles, disk space or something similar) it can instruct the Adapter Framework to shut down the BPEL process which "owns" the Adapter Endpoint Activation. To activate some kind of compensating BPEL Process, the user can configure this bpel.xml Activation Agent property.

Again, as for the BPEL Process Rejection Handler, the Fatal Error BPEL Process must use a Message Type as described above. However, in this case, the Message Type is defined in FatalErrorMessage.wsdl so the Fatal Error WSDL should import

location="http://localhost:9700/orabpel/xmllib/jca/FatalErrorMessage.wsdl"/>

EXCEPTION: ORA-22990: LOB LOCATORS CANNOT SPAN TRANSACTIONS

2007-06-07T18:52:00.000+05:30

EXCEPTION: ORA-22990: LOB LOCATORS CANNOT SPAN TRANSACTIONS

Fix
=========
Patch 4338987 available on MetaLink but for 10.1.2.0.0 fixed in 10.1.2.0.1

Bug 5651354 ORA-22990: LOB LOCATORS CANNOT SPAN TRANSACTIONS for 10.1.2.0.2

Reassign() अपि - रेस्त्रिच्त अचेस ओं रेअस्सिग्न() टास्क!

2007-06-07T16:34:00.000+05:30

QUESTION
===========
I have a bpel process in which i restricted system actions like Reassign,
now the process is in the production environment,

i have to reassign user tasks to another one :

i tried via the bpel api using reassign() api an error told me that the action is restricted on this task, eventhough i logged in as bpeladmin who has the right to perform restricted actions for tasks he owns.

ANSWER
=============

- just go to the domain folder in bpel, go to the temp directory then the folder of the process
- open the .task file of the task you want to allow an action for
- comment the action you want to allow in the "restrictedActions" tag
- restart the server

स्सनारियो व्हें फ़ाइल doesnt गेट पिच्केद इन ESB

2007-06-07T15:35:00.000+05:30

The minimum file age of files to retrieve. For example, this enables a large file to be completely copied into the directory before it is retrieved for processing. The age is determined by the last modified time stamp. For example, if you know that it takes three to four minutes for a file to be written, then set the minimum age to five minutes. If a file is detected in the input directory and its modification time is less than five minutes older than the current time, then the file is not retrieved because it is still potentially being written to.

ORABPEL-03802

2007-06-03T18:37:00.000+05:30

ORABPEL-03802

Correlation definition not registered.
The correlation set definition for operation "Read", process "ReadXML_Sync_PRC", has not been registered with the process domain.
Please try to redeploy your process to the process domain.

at com.collaxa.cube.engine.delivery.CorrelationRegistry.resolve(CorrelationRegistry.java:91)
at com.collaxa.cube.engine.delivery.DeliveryHelper.createCorrelationSet(DeliveryHelper.java:94)
at com.collaxa.cube.engine.delivery.SOAPProtocolHandler.calculateCorrelations(SOAPProtocolHandler.java:751)
at com.collaxa.cube.engine.delivery.SOAPProtocolHandler.receiveCallback(SOAPProtocolHandler.java:167)
at com.collaxa.cube.engine.delivery.DeliveryService.receiveCallback(DeliveryService.java:446)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.receiveCallback(CubeDeliveryBean.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at CubeDeliveryBean_LocalProxy_4bin6i8.receiveCallback(Unknown Source)
at com.collaxa.cube.engine.delivery.DeliveryHandler.continuePostAnyType(DeliveryHandler.java:416)
at com.collaxa.cube.engine.delivery.DeliveryHandler.continuePost(DeliveryHandler.java:370)
at com.collaxa.cube.engine.delivery.DeliveryHandler.post(DeliveryHandler.java:88)
at com.collaxa.cube.ejb.impl.DeliveryBean.post(DeliveryBean.java:201)
at com.collaxa.cube.ejb.impl.DeliveryBean.post(DeliveryBean.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DeliveryBean_RemoteProxy_4bin6i8.post(Unknown Source)
at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:195)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase$DeliveryServiceMonitor.send(AdapterFrameworkListenerBase.java:2543)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.executeDeliveryServiceSend(AdapterFrameworkListenerBase.java:569)
at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.deliveryServiceSend(AdapterFrameworkListenerBase.java:625)
at oracle.tip.adapter.fw.jca.AdapterFrameworkListenerImpl.performSingleActivation(AdapterFrameworkListenerImpl.java:952)
at oracle.tip.adapter.fw.jca.AdapterFrameworkListenerImpl.onMessage(AdapterFrameworkListenerImpl.java:799)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:281)
at oracle.tip.adapter.file.inbound.ProcessWork.publishMessage(ProcessWork.java:826)
at oracle.tip.adapter.file.inbound.ProcessWork.doTranslation(ProcessWork.java:580)
at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWork.java:266)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:179)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:272)
at java.lang.Thread.run(Thread.java:595)

Solution :

Install the patch : 5332819
ORABPEL-03802 CORRELATION DEFINITION NOT REGISTERED.

Can we have one orabpel schema supporting many application environments?

2007-06-01T20:42:00.002+05:30

Yes. As we discussed, you can either do this with a single BPEL "domain" where all the environments would share the same logical process sandbox. Or you can use multiple domains to separate the processes and instances. Different domains can either share the same orabpel schema (as you ask here) or have separate schemas.

Can we install multiple orabpel schema in single DB?

2007-06-01T20:42:00.001+05:30

Yes, this should work, however the IRCA script won't do it for you. But you can create a separate tablespace, user, ect and install the schemas there "manually". This is the same process which people use for non-Oracle DBs anyway, so it shouldn't be too painful. I suspect QA doesn't specifically test it, however, so you may not want to do it unless necessary.

ORABPEL-05002

2007-06-01T20:39:00.000+05:30

Can I add new nodes to the BPEL clustering without shutting down the dehydration database and other BPEL nodes?

2007-06-01T20:38:00.000+05:30

Yes you can. Just need to configure the new node to point to the existing dehydration database and copy the BPEL suitcase file (the jar file under orabpel/domains//deploy) from the existing nodes to the new node. Just need to make sure the process design does not hard code anything (such as hostname) that are only suitable for a particular node.

ORABPEL-09903

2007-05-21T19:54:00.000+05:30

The following error gets logged in BPEL logs:

What : ORABPEL-09903 occurs when data source

Reason:
Name is not set correctly.

Fix:
Set the name correctly in Oc4j-ra.xml is in %ORACLE_HOME%\j2ee\instance name>\application-deployments\default\AqAdapter.

Registering MQ Series as a Standalone Resource Provider in OC4J

2007-05-20T21:57:00.000+05:30

Registering MQ Series as a Standalone Resource Provider in OC4J
I have just been fighting to get MQ Series working with OC4J as a stand alone resource provider with the minimum of effort and in the most easy to understand way. Thought I would share with you the results of my travails.

To summarise you

Create the resources you want using MQ Explorer
Register a resource provider and its classes in application.xml
Create a resource adapter that uses the resource provider
Deploy the resource adapter to OC4J.
Configure the resource adapter to expose the correct resources.
Scenario
A standalone resource provider is available to all applications in the application server and so is an attractive way to install something as generic as IBM MQ Series. I decided to use the file based JNDI interface into MQ Series and registered a ConnectionFactory and a Queue into the JNDI namespace using Websphere MQ Explorer.

1. Creating the MQ Resources
Using Websphere MQ Explorer I create a file based JNDI naming tree and bound into it the following

A Queue (called “MQQ”) mapped onto the default queue.
A Queue (called “RouterLogQ”) mapped onto a new queue I created called AS_Router_LOGQ
A ConnectionFactory (called “MQCF”) mapped onto a ConnectionFactory.
The names obviously don’t matter but I intended to set up a JMS Router job to transfer messages from an Oracle queue to an IBM queue and each router job must have a log queue in both the source and target messaging systems, hence the creation of the queue AS_Router_LOGQ which I exposed through JNDI as RouterLogQ.

2. Registering the Resource Provider
This is simplicity itself. Declare the IBM resource provider in %ORACLE_HOME%/j2ee/home/config/application.xml.

name="mqjmsrp">

MQSeries resource provider

value="com.sun.jndi.fscontext.RefFSContextFactory">

value="file:C:/JNDI">

This declaration tells OC4J that it is using a resource provider that exposes resources through a JNDI naming context (class "com.evermind.server.deployment.ContextScanningResourceProvider"). The resource provider is called "mqjmsrp" (an arbitrary name that is referenced from the resource adapter). The exact details of the JNDI context are provided by identifying the class of the initial naming context (com.sun.jndi.fscontext.RefFSContextFactory). Finally we identify the file location which is the root of the MQ JNDI tree (using “java.naming.providor.url” property).

If we were to use a different JNDI naming context class then we may need different property parameters, such a port number and host name.

The final step to registering the provider is to add the MQ libraries to the classpath in %ORACLE_HOME%/j2ee/home/config/application.xml. The easiest way to do this is to point to the value of the %MQ_JAVA_LIB_PATH% environment variable that is set when you install MQ.

When you insert this make sure it is last in your list of library paths as it does contain the same classes as some OC4J libraries. You will be warned that these classes are being ignored when OC4J starts up. Don’t worry about that – trust me.

3. Create & deploy Resource Adapter
To create a resource adapter I used Oracle JDeveloper. Unfortunately JDeveloper has rather basic facilties for supporting creation of resource adapters. I followed the following steps to create the resource adapter.

I. Create an empty JDeveloper project and add appropriate libraries
This will provide us the structure in which to work. After creating the empty project add the standard J2EE librarie and create two new librarie from the following jar files

GJRA Library from %J2EE_HOME%/connectors/OracleASjms/OracleASjms/gjra.jar file
JCA Connectors library from %J2EE_HOME%/lib/connector.jar
By adding these libraries JDeveloper will be able to verify that classes referenced in the ra.xml file actually exist, thus checking that your file has the correct values in it.

II. Add a “new” ra.xml resource adapter descriptor file to the project by using the J2EE deployment descriptor wizard in JDeveloper.
This creates the resource descriptor file. So far so good. Many of the descriptors in JDeveloper have smart property editors that make sure you put the right elements in the right order, no such joy with resource adapter descriptors. So we need to build the remainder of the descriptor by hand.

Fill in the vendor details, EIS type and resource adapter version (provided in the template for the ra.xml file), which are all in our control and add a display name.

xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd"

xmlns="http://java.sun.com/xml/ns/j2ee" version="1.5">

MQjms

Oracle Corporation

MQ JMS

1.0

III. Add a “resourceadapter” tag to define the resource adapter and tie it back to the resource provider.
This gives us the following.

oracle.j2ee.ra.jms.generic.JMSResourceAdapter

lookupMethod

java.lang.String

resourceProvider

resourceProviderName

java.lang.String

mqjmsrp

The resource adapter needs a class to define it. This class is provided by the oracle.j2ee.ra.jms.generic.JMSResourceAdapter class which provides a generic JMS resource adapter wrapper. This class, together with the other classes used in this entry are shipped as part of the OracleASjms adapter in OC4J.

The resource adapter class needs to be configured. We need to identify the external service provider and this is done by identifying the provider as a resourceProvider (using the lookupMethod property) and then identifying which resource provider (using the resourceProviderName property). I have pointed it to the MQ Series resource provider we defined earlier, the resourceProviderName in the ra.xml pointing to the resource provider (“mqjmsrp”) defined in application.xml.

IV. Configure an outbound resource ConnectorFactory
JCA 1.5 introduced the idea of inbound and outbound resources. Outbound adapters are the original way of working, we make calls outbound from the resource adapter to the resource (remember resources are called EISs in JCA speak). Inbound adapters are new in JCA 1.5 and work on the Hollywood principal, don’t call us we’ll call you.

Lets define an outbound resource adapter using the “outbound-resourceadapter” element. We then need to declare the connection factories within the resource adapter. We do this within the “connection-definition” element.

oracle.j2ee.ra.jms.generic.ManagedConnectionFactoryImpl

jndiLocation

java.lang.String

MQCF

javax.jms.ConnectionFactory

oracle.j2ee.ra.jms.generic.ConnectionFactoryWrapper

javax.jms.Connection

oracle.j2ee.ra.jms.generic.ConnectionWrapper

Here we have declared a managed connection factory (managed means that it can be managed by the container, in our case OC4J). We need to provide a managed connection factory class which we identify (again using the classes provided in the OracleASjms adapter) .

We then configure the managed connection factory by identifying the JNDI location in the MQ JNDI space where a ConnectionFactory has been registered. In this case “MQCF”.

Having located the real ConnectionFactory we need to tell the adapter what classes it implements. We do this with the “connection-factory-interface” element which tells us that this is really a JMS ConnectionFactory. We provide a generic wrapper for this to provide the implementation class “ConnectionFactoryWrapper” (in the “connectionfactory-impl-class” tag).

Finally we tell the adapter that a ConnectionFactory class generates JMS “Connection”s (with the “connection-interface” element) and that we have provided a wrapper for this (identified by the “connection-impl-class” element) of a ConnectionWrapper class.

All this fuss allows the container to manage pools of connections itself, giving us greater control over how OC4J manages the integration with MQ.

V. Add other ConnectionFactory definitions.
We can have multiple connection factories in an outbound resource adapter definition. The table below summarises the connection factories supported by the generic JMS adapter.

javax.jms
factory-class>
oracle.j2ee.ra.jms.generic

oracle.j2ee.ra.jms.generic

>
javax.jms

oracle.j2ee.ra.jms.generic

ConnectionFactory
ManagedConnectionFactoryImpl
ConnectionFactoryWrapper
Connection
ConnectionWrapper

XAConnectionFactory
ManagedXAConnectionFactoryImpl
XAConnectionFactoryWrapper
XAConnection
XAConnectionWrapper

QueueConnectionFactory
ManagedQueueConnectionFactoryImpl
QueueConnectionFactoryWrapper
QueueConnection
QueueConnectionWrapper

XAQueueConnectionFactory
ManagedXAQueueConnectionFactoryImpl
XAQueueConnectionFactoryWrapper
XAQueueConnection
XAQueueConnectionWrapper

TopicConnectionFactory
ManagedTopicConnectionFactoryImpl
TopicConnectionFactoryWrapper
TopicConnection
TopicConnectionWrapper

XATopicConnectionFactory
ManagedXATopicConnectionFactoryImpl
XATopicConnectionFactoryWrapper
XATopicConnection
XATopicConnectionWrapper

VI. Declare the type of transaction support for the outbound-resourceadapter
We need to tell the container the type of transaction support provided by this adapter. The choices are XATransaction, LocalTransaction and NoTransaction. In this case we declare the resource adapter to support XA transactions by adding a suitable “transaction-support” element after all connection factory definitions.

XATransaction

If the resource provider only supports “LocalTransaction” then OC4J can still enlist the resource in XA transactions, but only if no other non-XA resources are involved.

VII. Add authentication and re-authentication elements for the outbound resource adapter
The container must be told about the authentication requirements of the resource. In this case we identify support for basic password authentication only.

BasicPassword

javax.resource.spi.security.PasswordCredential

false

We also say that reauthentication is not supported.

VIII. Declare placeholders for queues
So far we have identified what connection factories look like. We now tell the container what Queues and/or Topics look like. To do this we use the “adminobject” element. Here we identify the type of objects to be found (using the “adminobject-interface” element) and also their wrapper implementation (using the “adminobject-class” element).

Finally we identify the source location for these objects (in this Queues) by having a “resourceProviderName” property that we point at the MQ JMS resource provider.

This then provides a description of what a queue looks like. We will see later how this becomes a prototype for accessing MQ Series Queue objects from OC4J.

javax.jms.Queue

oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl

resourceProviderName

java.lang.String

mqjmsrp

The same configuration can be used for Topics by replacing references to Queue with references to Topic.

IX. Create Resource Adapter Deployment Profile
We have now finished with the ra.xml file and can proceed to package up the resource adapter for deployment to OC4J. To do this we create a new RAR file deployment profile within JDeveloper (I called mine “MQjms”). The name of the deployment profile by default will be the name of the RAR file and the resulting resource adapter.

Explicitly add the GJRA jar file (%J2EE_HOME%/connectors/OracleASjms/OracleASjms/gjra.jar) to the list of contributors. We are now ready to deploy the resource adapter archive (rar) file.

4. Deploy the MQ Resource Adapter to OC4J
We can deploy the rar file direct from JDeveloper or by using the EM console in App Server. If we deploy through JDeveloper then it will be deployed with default settings (i.e. nothing will be configured unless we have provided an “oc4j-ra.xml” file in the deployment). If we deploy through EM then we will be given the opportunity to configure the resource adapter at deployment time.

To get to the deployment screen on EM

Logon to EM
Select Applications tab
Select “Standalone Resource Adapters” view from the dropdown
Click deploy…
Note that if deploying from JDeveloper the adapter will be called by the name of the depoloyment profile, if deploying from EM you can choose a name.

If we decide not to configure the resource adapter we can always do so later. So lets leave it until later.

5. Configure the MQ Resource Adapter on OC4J
At this point we have created a description of MQ Series resources potentially available to an OC4J application but we have not actually configured any resources, so lets go ahead and do that.

I. Create a ConnectionFactory
Lets start by creating a ConnectionFactory using EM.

Logon to EM
Select Applications tab
Select “Standalone Resource Adapters” view from the dropdown
Select “Connection Factories” tab
Select “create”
A drop down list of the different types of connection factory available (the ones you registered in the ra.xml file) will appear. Select the type that you want and you will then be asked to provide the OC4J “JNDI Location” of this factory. This location is relative to the name of the resource adapter (“MQjms” in my case).

This screen will also show the “jndiLocation” of the resource in the MQ JNDI namespace (relative to the root context of the MQ JNDI namespace.

I created a connection factory at location “IBMMQjms/ConnectionFactory”. Although you can use arbitrary names it is a good idea to group all resources in a single adapter under a single tree so that you know where your resources are coming from.

II. Create Queues
There is no need to declare individual queue objects. We can just map the MQ JNDI namespace onto the OC4J namespace and let applications look up any Queue in the MQ namespace. To do this use the “Administered Objects” tab in EM and select “create”. Select the type of object you want to map into the OC4J namespace. Then enter the JNDI location where you want the IBM MQ Series queues defined in the MQ JNDI to appear.

I entered a value of “IBMMQjms/Queues”. The first part tells me (not OC4J) that this is an IBM MQ namespace, Queues tells me that I can access queue objects here. Individual queues in the MQ namespace (for example Queue at location “MQQ”) can be looked up by appending the IBM JNDI location to the OC4J prefix, in this case IBM “MQQ” will appear at “IBMMQjms/Queues/MQQ”

Completed!
We have now finished configuring everything. So lets summarise what we did.

Set up the objects we wanted in IBM MQ Series
Connection Factory “MQCF”
Queue “MQQ”
Created a Resource Provider “mqjmsrp” that provides access to the IBM JNDI name space.
Created a Resource Adapter “MQjms” that describes what MQ objects look like to OC4J.
Mapped objects in the MQ JNDI namespace into the OC4J namespace
Connection Factory “MQCF” mapped to “IBMMQjms/ConnectionFactory”
Queue “MQQ” mapped to “IBMMQjms/Queues/MQQ” – note that any other queues in the MQ JNDI namespace can be accessed in a similar way with no more configuration on the OC4J side.
Testing It
To test the configuration I created several servlets.

ListerServlet (“/list”) that displays the JNDI namespace. Use this to verify that you can see your connection factories and queue template directories.
Sample Output
JNDI Root ""

/jmsrouter_ejb_TimerHandlerBeanLocal(TimerHandlerBean_LocalHomeProxy_1nca7p1)

/admin_ejb_MBeanServerEjb(MBeanServerEjb_RemoteHomeProxy_1me2j7)

…

/IBMMQjms(javax.naming.Context)

/IBMMQjms/Queues(oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl)

/IBMMQjms/ConnectionFactory(oracle.j2ee.ra.jms.generic.ConnectionFactoryWrapper)

PosterServlet (“/send”) that submits a message onto a queue using a ConnectionFactory (“/send?CF=IBMMQjms/ConnectionFactory&Q=IBMMQjms/Queues/MQQ”)
Sample Output
Sent message 'Hello at Wed Apr 04 09:53:20 BST 2007'

'JMSCorrelationID'=null

'JMSDeliveryMode'=2

'JMSDestination'=oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl[queue://QM_workstationxp/default]

'JMSExpiration'=0

'JMSMessageID'=ID:414d5120514d5f776f726b737461746909251146200b2802

'JMSPriority'=4

'JMSRedelivered'=false

'JMSReplyTo'=null

'JMSTimestamp'=1175676800062

'JMSType'=null

'JMS_IBM_PutDate'='20070404'(java.lang.String)

'JMSXAppID'='JDeveloperjdkbinjava.exe'(java.lang.String)

'JMS_IBM_PutApplType'='11'(java.lang.Integer)

'JMSXUserID'='oracle '(java.lang.String)

'JMS_IBM_PutTime'='08532006'(java.lang.String)

'JMSXDeliveryCount'='0'(java.lang.Integer)

ReaderServlet (“/reader”) that reads a message from a queue using a ConnectionFactory (“/send?CF=IBMMQjms/ConnectionFactory&Q=IBMMQjms/Queues/MQQ”)
Sample Output
Received message 'Hello at Wed Apr 04 09:53:20 BST 2007'

'JMSCorrelationID'=null

'JMSDeliveryMode'=2

'JMSDestination'=oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl[queue://QM_workstationxp/default]

'JMSExpiration'=0

'JMSMessageID'=ID:414d5120514d5f776f726b737461746909251146200b2802

'JMSPriority'=4

'JMSRedelivered'=false

'JMSReplyTo'=null

'JMSTimestamp'=1175676800062

'JMSType'=null

'JMS_IBM_PutDate'='20070404'(java.lang.String)

'JMSXAppID'='JDeveloperjdkbinjava.exe'(java.lang.String)

'JMS_IBM_Format'='MQSTR '(java.lang.String)

'JMS_IBM_PutApplType'='11'(java.lang.Integer)

'JMS_IBM_MsgType'='8'(java.lang.Integer)

'JMSXUserID'='oracle '(java.lang.String)

'JMS_IBM_PutTime'='08532006'(java.lang.String)

'JMSXDeliveryCount'='1'(java.lang.Integer)

EnvironmentServlet (“/printenv” that displays the environment as seen from within the Java Virtual machine (useful for checking that you can see the directory with IBM MQ Series native libraries)
Sample Output
Java Environment

Absolute Default Directory C:OC4Jbin.

Canonical Default Directory C:OC4Jbin

Available Processors 1

…

MQ_JAVA_LIB_PATH C:Program FilesIBMWebSphere MQJavalib

…

lib C:Program FilesIBMWebSphere MQtoolslib

MQ_JAVA_DATA_PATH C:Program FilesIBMWebSphere MQ

…

MQ_JAVA_INSTALL_PATH C:Program FilesIBMWebSphere MQJava

…

Path C:Program FilesIBMWebSphere MQJavalib;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:Program FilesIBMWebSphere MQbin;C:Program FilesIBMWebSphere MQtoolsc\samplesbin

Sample Files
I have uploaded the following files.

ra.xml Resource adapter file for MQ series.
MQjms.rar (includes ra.xml file) MQ Series Resource Adapter. Deploy this and configure it to point to your own MQ resources.
WebTester.ear Sample JMS Test application. Deploy this to access the Servlets listed above.
What’s Left?
I haven’t covered the inbound use of JMS as a MessageListener. Maybe I will cover that in another post. In the meantime enjoy using MQ Series from within OC4J.

Oracle BPA Suite tips: #1. Installation of the client

2007-05-20T21:50:00.001+05:30

Oracle BPA Suite tips: #1. Installation of the client

I have been working with the BPA suite for a couple of weeks now. My previous experience with modeling is in UML with UML tools like Rational Rose, Sparx Enterprise Architect and Borland Together. The BPA suite is more geared towards enterprise architecture modeling and has more than 100 different types of models you can create. The architecture of the suite differs from ‘regular’ modeling tools as well. In this series I will talk about some tips and tricks about using the BPA Suite. If you have any tips or tricks of your own, drop me a note and I will add it to the series.
….Enough introductory mumbo jumbo, let’s talk tips!

When you install the BPA suite on your client machine (Windows in this case), it will put some stuff on your machine, that can mess up other installations, especially the PATH variable. After installing the BPA Suite the PATH variable will look something like this:
C:\Program Files\Oracle BPA Suite\LocalServer\JDK\bin;C:\Program Files\Oracle BPA Suite\LocalServer\OLITE; etc

When you install Oracle BI Enterprise Edition on your machine, it will do the same: it puts a (different) JDK on your path. At first the BPA suite seemed to be running fine. We ran into trouble when we tried to restore a database: we got a cryptic “ClassNotFound” error. Luckily the person who had BI Suite running on his machine figured it out quickly so we did not lose too much time looking for the cause of the problem.

I guess there are several solutions to this problem:

write a script that sets the path before starting BPA Suite, and a different one for Oracle BI Suite EE
Ask Oracle to fix this, for example by using named variables instead of putting everything on the path
use VMware images for the BI Enterprise Edition
I ended up doing the latter: I created a VMWare image for the BI Suite on my machine. This way I have a clean installation that does not conflict with any other Oracle installation.

I do hope Oracle will fix this problem because it is not unusual for developers to have different Suites or even different versions of Suites on one machine: this is something that should be possible without problems.
In fact it reminds me of the problems we used to have (back in the days..) installing Designer6 and Forms6 on the same machine.

Oracle BPA Suite first impressions

2007-05-20T21:46:00.000+05:30

Oracle BPA Suite first impressions

Enterprise architecture should be based on business drivers and strategy, constraints from the organization like budget and time, and architectural principles. When you model an architecture for a product or project, the same thing applies. It is important that the proposed architecture reflects business drivers and adheres to certain principles.
There are several tools available in the market to design or model architectures and applications. A modeling tool should be practical and help you reach your goal. To be helpful it should have the following characteristics:

It should adhere to standards (like UML, BPEL, XMI)
It should be possible to trace relationships between different perspectives (functional, data and application, technical for example) and between the architecture and the business strategy, and stakeholders and concerns.
It should be easy to learn and easy to use
It should be possible to publish (parts) of the model to html or rich text format, to communicate with the business and IT people
It should be possible to import and export the model to other tools, to prevent vendor lock-in
The tool I have been using the last year and a half is Enterprise architect. It adheres to UML (not BPEL or BPMN), generates reports in html or rtf and is easy to use and to learn. It works well in JEE environments, supports reverse engineering and mda and is not very expensive.

Until recently, all Oracle had to offer was Designer or JDeveloper to model.
The problem with Designer is that it does not adhere to standards like UML and BPEL or BPMN. It is very good fit for projects and organisations that use CDM or CDM fast track and have traditional monolothic applications. It is not very useful when you are in a JEE or service oriented architecture environment. There are a lot of options and fields you can fill out. This makes it hard to learn. Once the model is in Designer, you can’t export it to another tool anymore, nor can you communicate it easily to the rest of the business. All you can do is export it to another repository or generate the fysical datamodel, PL/SQL code and or forms application.

JDeveloper on the other hand, adheres to standards like UML, XMI, BPEL and ERM. The problem is that there is no way to link different models together or publish the model in a webpage or report. It has limited possibilities which makes it easy to learn, but not always easy to use. JDeveloper is useful as a design tool for certain modules in your application, not to model the entire application or enterprise architecture.

At Oracle World, Oracle announced they added a new suite to the Fusion Middleware toolbox: Oracle BPA suite. It is marketed like this: “Oracle Business Process Analysis (BPA) Suite speeds process innovation by rapidly modeling business processes and converting them into IT executables. Oracle BPA Suite, based on the market leading IDS Scheer ARIS Design Platform, delivers a comprehensive set of integrated products that allows business users to design, model, simulate, and optimize business processes to achieve maximum operational efficiency. ” To me that sounded like a tool that limits support to BPMN, BPML and BPEL. JDeveloper already supports BPEL, so I never bothered to try it. If you look at the roadmap and overview of the suite, it also looks like a very process oriented tool.

Last week, we were looking into several options for modeling an architecture and we decided to have a look at the BPA suite. To my surprise it supports much more than just business process analysis. It allows you to model business objectives, application architecture and several other aspects of the architecture using different methods and standards (UML, BPEL, BPMN, etc).
It is very easy to install: you double click the setup.exe and then all you need to do is “next”, “next”, “next” and within half an hour or so you are up and running. It uses a database as a repository, so it might not be very easy to integrate with repositories, versioning systems or document management systems in your enterprise.
It can import and export in XMI, save diagrams in emf, and generate reports concerning consistency and violations of rules. It also has a publisher component which publishes the content to communicate with the rest of the organization.

The way the integration with JDeveloper and the development process is pictured in the road map, seems very complex to me: have a look at Scott Amblers site about agile modeling, before you get lost in this new and cool modeling suite and forget what IT is all about: adding value to the business. In some situations all you need is a whiteboard or a pencil and some paper….

But if you do need a tool: don’t forget to take a look at the BPA suite!

Removed...

2007-05-13T22:58:00.001+05:30

Removed....by author

Performance problems running SOA Suite on VMWare

2007-05-13T21:12:00.000+05:30

For development and testing purposes i’m using vmware to run Oracle’s SOA suite on my laptop. I’ve installed it on Centos. When running this on my laptop, the performance isn’t really great, the oc4j processes are using a lot of cpu time (continuously 50%). My initial thought was that this was related to my situation: running it on a laptop and not giving it enough memory (the vmware instance has about 1Gb allocated, the laptop has 2Gb). But recently we’ve seen these performance problems at other locations, where the vmware instance has enough memory (2.5Gb). A search on google shows that more people have problems using Oracle’s SOA suite on vmware: Poor performance of oracle soa-suite in vmware.

Has anybody else experienced this problem? Have you found any solutions?

Clustering विथ Oracle ESB Product

2007-05-06T17:26:00.000+05:30

With multiple clustered ESB-Runtimes (RTs) - do I need to deploy only once or do I need to deploy once per RT (like it is for BPEL)?

You need to register your services to the ESB metadata server (aka DT server) only once. Each of the RTs will get notified of the metadata change via the Control Notification mechanism (with JMS as the underlying protocol). The RTs will then update/refresh their in-memory cache for only those services that they are currently hosting. You register your services only once to the DT server, and not multiple times to each cluster.

Do the ESB have in-memory session state (i.e. do I need to configure OC4J session replication)?
ESB messages are completely stateless. The global transaction rolls back if there are errors. In case of synchronous flows, the exception/fault is rolled back to the client. In case of asynchronous flows, the message is rolled back to the Asynchronous Topic. There is no session state replication required since these are stateless messages, hence no configuration is

Are ESB configuration changes be distributed across all cluster nodes?
All metadata and config changes are propagated to RTs via the Control Notification mechanism. You do not have to individually propagate them.

Of course a lot of this is documented in our documentation which is available at http://download-west.oracle.com/docs/cd/B31017_01/core.1013/b28939/toc.htm

Using Oracle BPEL instead of ESB??

2007-05-06T17:22:00.000+05:30

Using Oracle BPEL instead of ESB??
I did an quite interesting research today on my laptop ,
Can I use , Oracle ESB product to do integration code instead of Oracle BPEL..???????????????

Why?? Well we already know Oracle BPEL and quite simply didnt really want to learn/install/manage another product.... i.e. ESB

Well Yes its true that if your doing "integration" code then you could use Oracle BPEL and/or Oracle ESB. Actually before we had Oracle ESB you had to use Oracle BPEL and many customers have implemented integration hubs using Oracle BPEL quite successfully, so it why do we [oracle] need an ESB product...

Well the answer is in the description, Oracle BPEL can be used for integration code but its not designed/optimised for it.. Oracle BPEL is a Business Process Execution Language and as such its optimised for managing and coding business processes, whereas an ESB is quite simply a highly efficient intergration product. Its principle objective is to join two different services together quickly, efficiently and bi-directional.

Specifically an ESB moves data via

Connects services via different adaptors (WebServices, FTP,File,JDBC etc) and protocols (HTTP,JMS)
Enriches and transform data using XSL & domain value mapping lookups

Routes messages based on data in the message payload and/or header

and finally and often overlooked feature is that an ESB

Virtualises services, quite simply adds a facade layer to your infrastructure...
Its also worth noting that doing integration work with Oracle ESB is not only quicker to "build" but its also quicker in its execution. I've been told by some collegues in the US that an integration process in ESB product is approx twice the speed of same process in Oracle BPEL..

So to recap

Use ESB when

You want a really low cost solution

Only need connectivity, simple transformations and routing

Use BPEL+ESB when

You need to code complex business logic
Integration with Workflow
Complex transforms potentially involving the database

Have Long running processes which may or may not be stateful

Oracle Certified - 10g Oracle Application Server Administration

2007-04-08T20:45:00.000+05:30

LORD VINAYAKA blessed me once again!!!!!!!!!!!

YES the 7th(lucky number) of April ----------- Oracle Certified in 10g Oracle Application Server Administration.
Venue-Prometric Centre

A new feather in my cap in latest technology domain :)

Configuring email notifications when file based

2007-03-24T02:43:00.000+05:30

BEWARE!!!

Configuring email notifications when its file based basically demands configuring both ns_emails.xml and user-properties.xml.
When we add a new usser , then we need to add an entry into the user-properties.xml file.

Basic assembly model of Service Component Architecture (SCA)

2007-03-10T21:41:00.000+05:30

Service Component Architecture (SCA) specifications started as a joint effort by mainly IBM and BEA in 2004 soon got more acceptances in 2005 when other software companies like Oracle, IONA, SAP AG, Sybase, Xcalia and Zend also joined the effort. As of February 2007, seventeen key vendors (http://www.osoa.org/display/Main/Service+Component+Architecture+Partners) are working together to define a specification that can be a version 1.0. It has almost all major J2EE middleware vendors on its board. Offcourse, you won’t miss an absence of Microsoft.

Specifications:

Version 0.9 (Nov 2005)

http://www.oracle.com/technology/tech/webservices/standards/sca/pdf/SCA_AssemblyModel_V09.pdf

Version 0.96 (Nov 2006)

http://www.osoa.org/download/attachments/35/SCA_AssemblyModel_V096.pdf?version=1

Upcoming specification 1.0

A service, in case of web service defined in WSDL, is a heart of Service Oriented Architecture (SOA). Service can be implemented using different languages like Java, C++, PHP, etc and many follow different interaction protocols. Often services interact together to offer a business solution (thus becoming an application). However, there was no standard way to specific this dependencies and to assemble them together to form a composite application. Sun Microsystems had provided JBI to address some of the needs needs. However, JBI is Java centric. So cross platform component architecture was much needed. That’s where SCA stepped in.

SCA provides a way to specify the interaction of services and assemble them together to form a composite application. The specification does not dictate any runtime implementation but, just like WSDL is in XML, it express an assembly of a composite application composed of services implemented using different technologies like EJB, web services, C++, PHP and invoking internal or external services via different protocols. Thus making a deployable assembly of services. With this modular and uniform assembly of disparate services, platforms built on SCA would definitely provide service-based applications that are easy to deploy, configure, monitor and move. Thus, would reduce a Total Cost of Ownership (TCO).

Basics design blocks of SCA assembly:

Composite: As expressed in fig 1, a basic container block of SCA assembly is a Composite. A composite is composed of Services, entry points, references and wires linking them together. Composite is expressed in XML and it does not replace the definitional artifacts of software’s implementing the services. Composite has an entry point expressed as a Java or WSDL interface. These interfaces can be bound to different protocols like SOAP over HTTP, JMS, JCA, etc via bindings.

Component: One basic artifact of SCA is the component which implements services in using different implementations like BPEL, EJB, Annotated Java, and PHP etc. The implementation types are specified in the components definition. Services, implemented by components, can be consumed by other components and external software. The components may have settable properties.

References: Services provided by Components may depend on other services. The service depending on is specified as a reference.

Wires: Wires links components to references or other components.

Fig 1. SCA System assembly (source: SCA specifications)

Fig2. SCA Composite Assembly (source: SCA specifications)

Note that, though SCA assembly provides wirings between components and can be graphically depicted as a flow, SCA itself is neither an orchestration engine like BPEL nor a workflow.

Note that SCA assembly model provides a loose coupling and flexibility to change. You may notice that a referencing service need not know the implementation type of the referenced service. It only knows the interface. Similarly, one can always change the wires or bindings thus offering a flexibility. With this module composition of services and their implementation, we may see an overall increase of productivity.

All of these can be assembled together to make a composite as:

In addition to SCA assembly model, SCA defines specifications for client and implementations, bindings and policies.

Client and Implementation specs: SCA provides Client API and service implementation specifications (Java, PHP, BPEL, etc).

Bindings: Access interactions with outside a composite are defined by bindings. SCA specifications are working on various bindings like WSDL, JMS, RMI-IIOP, REST, etc.

Policies: SCA also working on defining a framework to define policies like transaction, reliable mesaging, secutity etc.

Characterset conversion

2007-03-10T21:39:00.002+05:30

Using the SOA Suite with the DBAdapter, even for Oracle EBunisses Suite (EBS), you must be ware of your character set you are using. The application server is running in Java and using XML, so it uses by default UTF-8.

If your database is configured not for UTF-8, it will convert the incoming payload to the character set of the database. Nine-out-of-ten it will run without any errors. But using special characters you could get errors when you insert data in the database.

This issue can be solved by using a PL/SQL function to convert the data from on characterset to another one.
PL/SQL using implicit the database character set. Using 'CONVERT()' function.

CONVERT(string, to-characterset, from-characterset);
Example:

SELECT CONVERT('Ä Ê Í Ó Ø A B C D E ', 'UTF8', 'WE8ISO8859P1') FROM DUAL;

Delete bulk BPEL instances

2007-03-10T21:39:00.001+05:30

It can take a while to purge the BPEL instances from the dehydration store. It can be done faster, if you would like. The following step is usefull in a developement environement. First stop the BPEL instance via Enterprise manager.

BTW: If you do not want a bulk delete, but instance by instance for a particular date and domain and revision, look here.

Then in sqlplus orabpel/password (note: 10.1.3.0.1):

truncate table cube_instance;truncate table cube_scope;truncate table work_item;truncate table wi_exception;truncate table document_ci_ref;truncate table document_dlv_msg;truncate table document_dlv_msg_ref;truncate table scope_activation;truncate table dlv_subscription;truncate table audit_trail;truncate table audit_details;truncate table sync_trail;truncate table sync_store;truncate table dlv_message;truncate table invoke_message;alter table cube_instance deallocate unused;alter table cube_scope deallocate unused;alter table work_item deallocate unused;alter table wi_exception deallocate unused;alter table document_ci_ref deallocate unused;alter table document_dlv_msg deallocate unused;alter table document_dlv_msg_ref deallocate unused;alter table scope_activation deallocate unused;alter table dlv_subscription deallocate unused;alter table audit_trail deallocate unused;alter table audit_details deallocate unused;alter table sync_trail deallocate unused;alter table sync_store deallocate unused;alter table dlv_message deallocate unused;alter table invoke_message deallocate unused;alter table cube_scope enable row movement;alter table cube_scope shrink space compact;alter table cube_scope shrink space;alter table cube_scope disable row movement;alter table cube_instance enable row movement;alter table cube_instance shrink space compact;alter table cube_instance shrink space;alter table cube_instance disable row movement;exec dbms_utility.analyze_schema('ORABPEL', 'Compute');Then in sqlplus orabpel/password (note: 10.1.2.0.2):
truncate table cube_instance;truncate table cube_scope;truncate table work_item;truncate table wi_exception;truncate table document;truncate table scope_activation;truncate table dlv_subscription;truncate table audit_trail;truncate table audit_details;truncate table sync_trail;truncate table sync_store;truncate table tx_inferior;truncate table tx_superior;truncate table dlv_message;truncate table dlv_message_bin;truncate table invoke_message;truncate table invoke_message_bin;alter table cube_instance deallocate unused;alter table cube_scope deallocate unused;alter table work_item deallocate unused;alter table wi_exception deallocate unused;alter table document deallocate unused;alter table scope_activation deallocate unused;alter table dlv_subscription deallocate unused;alter table audit_trail deallocate unused;alter table audit_details deallocate unused;alter table sync_trail deallocate unused;alter table sync_store deallocate unused;alter table tx_inferior deallocate unused;alter table tx_superior deallocate unused;alter table dlv_message deallocate unused;alter table dlv_message_bin deallocate unused;alter table invoke_message deallocate unused;alter table invoke_message_bin deallocate unused;alter table cube_scope enable row movement;alter table cube_scope shrink space compact;alter table cube_scope shrink space;alter table cube_scope disable row movement;alter table cube_instance enable row movement;alter table cube_instance shrink space compact;alter table cube_instance shrink space;alter table cube_instance disable row movement;exec dbms_utility.analyze_schema('ORABPEL', 'Compute');

Delete BPEL instances

2007-03-10T21:37:00.000+05:30

Running a production environment generates a huge amount of BPEL instances. Unless you have specified that you do not use dehydration :-).

It is possible to purge the instances all at once, as described in the article here. But this purges all the instances. This is nice during development. But in a production environment you want to have a controlled way. A nice way to do this is via good-old PLSQL. Use the package COLLAXA in the ORABPEL schema.

This package has some nice methods to call:

procedure delete_txs
Deletes all the transactions that belong to a particular cube instance.

procedure delete_ci
Deletes a cube instance and all rows in other Collaxa tables that reference the cube instance. Since we don't have referential integrity on the tables (for performance reasons), we need this method to help clean up the database easily.

You can make a query to select the BPEL instances to delete and call the package:

create or replacePROCEDURE purge_instances( p_domain IN VARCHAR2 DEFAULT '%', p_process_name IN VARCHAR2 DEFAULT '%', p_revision IN VARCHAR2 DEFAULT '%', p_older_than IN NUMBER DEFAULT 999)ISCURSOR c( b_domain IN VARCHAR2, b_process_name IN VARCHAR2, b_revision IN VARCHAR2, b_older_than IN VARCHAR2)ISSELECT cie.cikey cikey, dmn.domain_id domain_id, cie.process_id process_id, cie.revision_tag revision_tag, cie.modify_date modify_date, cie.domain_ref domain_refFROM cube_instance cie, domain dmnWHERE cie.domain_ref = dmn.domain_ref---- the name of the domainAND dmn.domain_id LIKE b_domain---- code 5 means completedAND cie.modify_date < TRUNC(sysdate)-b_older_than--AND cie.process_id LIKE b_process_nameAND cie.revision_tag LIKE b_revision;BEGIN FOR r in c ( p_domain , p_process_name , p_revision , p_older_than ) LOOP DBMS_OUTPUT.PUT_LINE ( 'Purge '||r.process_id||'('||r.revision_tag||')'|| ' at '||to_char(r.modify_date, 'YYYY-MM-DD HH24:MI:SS') ); collaxa.DELETE_CI(r.cikey); END LOOP; -- -- delete invoke calls -- invoked messages DELETE FROM invoke_message_bin imn WHERE EXISTS ( SELECT 1 FROM invoke_message ime , domain dmn WHERE ime.message_guid = imn.message_guid AND ime.domain_ref = dmn.domain_ref AND dmn.domain_id LIKE p_domain AND ime.state > 1 AND ime.process_id LIKE p_process_name AND ime.revision_tag LIKE p_revision AND ime.receive_date < TRUNC(sysdate)-p_older_than ); -- DELETE FROM invoke_message ime WHERE ime.domain_ref in ( SELECT dmn.DOMAIN_REF from domain dmn WHERE dmn.domain_id LIKE p_domain ) AND ime.state > 1 AND ime.process_id LIKE p_process_name AND ime.revision_tag LIKE p_revision AND ime.receive_date < TRUNC(sysdate)-p_older_than; -- DBMS_OUTPUT.PUT_LINE ('-> #invoke msg '||SQL%ROWCOUNT); -- -- -- delete callback calls DELETE FROM dlv_message_bin dmb WHERE EXISTS ( SELECT 1 FROM dlv_message dme , domain dmn WHERE dme.message_guid = dmb.message_guid AND dme.domain_ref = dmn.domain_ref AND dmn.domain_id LIKE p_domain AND dme.state > 1 AND dme.process_id LIKE p_process_name AND dme.revision_tag LIKE p_revision AND dme.receive_date < TRUNC(sysdate)-p_older_than ); -- DELETE FROM dlv_message dme WHERE dme.domain_ref IN ( SELECT dmn.DOMAIN_REF from domain dmn WHERE dmn.domain_id LIKE p_domain ) AND dme.state > 1 AND dme.process_id LIKE p_process_name AND dme.revision_tag LIKE p_revision AND dme.receive_date < TRUNC(sysdate)-p_older_than; -- DBMS_OUTPUT.PUT_LINE ('-> #callback msg '||SQL%ROWCOUNT);END;/

How to install and use the BpelConsole undeploy extension

2007-03-10T21:35:00.000+05:30

Note: While this article is changing code in the original files of the product, there is no guarantee of support provided.

During development you deploy and undeploy process to the BPEL PM. Sometimes you want undeploy more than one process. This article describes a solutions that adds an option in the BPEL console to undeploy all the BPEL processes at onces.

Make a copy the of the files; bulkUpdateProcess.jsp and doBulkUpdateProcess.jsp.
These files are located in the directory

$ORACLE_HOME/j2ee/oc4j_soa/applications/orabpel/console

Add the following code in the the file bulkUpdateProcess.jsp.
Add the code after the label:

<%= I18nUtil.getString("off", locale)%>

Process Undeploy:
Using this option all the selected processes can be undeployed at once.
The default for undeployment is none, but you can enable this bulk undeployment
by setting this value to all.
Note that if this option is selected,the other bulk update options (Process Lifecycle/State)are ignored.

NoneAll Replace the the code in the the file dobulkUpdateProcess.jsp.
The code can be found at the end of the article.

When you navigate to the BpelConsole after you have installed the undeploy extension files, you can now use the new feature. Select the BpelProcesses you want to undeploy or use the ‘Check_all’ option and press the ‘Bulk update’ button.

Now you see at the bottom of the page the new ‘Process Undeploy’ option which you can use to undeploy all the selected processes.

The doBulkUpdateProcess.jsp is here:

<%@page contentType="text/html; charset=UTF-8" %>
<%@page errorPage="reportError.jsp" %>
<%@page import="com.oracle.bpel.client.*" %>
<%@page import="com.oracle.bpel.client.ServerException" %>
<%@page import="com.oracle.bpel.client.util.*" %>
<%@page import="com.collaxa.cube.util.BuildInfo" %>
<%@page import="com.collaxa.cube.fe.util.ServletUtils" %>
<%@page import="com.collaxa.common.util.*" %>
<%@page import="com.collaxa.cube.rm.suitcase.*" %>
<%@page import="java.text.*" %>
<%@page import="java.util.*" %>
<%@include file="initI18n.jspf" %>

<%
int n0 = 0, n1 = 0;
Locator l = ServletUtils.getLocatorWithoutUrlRewrite(request, response);
request.setAttribute( "tab", "BPEL Processes" );

IBPELDomainHandle domain = l.lookupDomain();

String processIds = request.getParameter( "processIds" );
ArrayList list0 = CXStringUtils.split( processIds, ' ' );
n0 = list0.size();
ArrayList list1 = new ArrayList();
Iterator li = list0.iterator();

try {
String undeployMode = request.getParameter( "processDeploy" );
if (undeployMode.equalsIgnoreCase("all")) {
for( int size = list0.size(); size > 0; size-- )
{
list1.clear();
CXStringUtils.split( (String) li.next(), '~', list1 );
BPELProcessId pid = new BPELProcessId(domain.getDomainId(),
(String)list1.get(0), (String)list1.get(1));
domain.undeployProcess(pid);
n1++;
}
}
else {
int lifecycle = -1;
String processMode = request.getParameter( "processMode" );
if( ! CXStringUtils.isEmpty( processMode ) )
{
lifecycle = "open".equalsIgnoreCase( processMode )
? IBPELProcessConstants.LIFECYCLE_ACTIVE
: IBPELProcessConstants.LIFECYCLE_RETIRED;
}
int state = -1;
String processState = request.getParameter( "processState" );
if( ! CXStringUtils.isEmpty( processState ) )
{
state = "on".equalsIgnoreCase( processState )
? IBPELProcessConstants.STATE_ON
: IBPELProcessConstants.STATE_OFF;
}
for( int size = list0.size(); size > 0; size-- )
{
list1.clear();
CXStringUtils.split( (String) li.next(), '~', list1 );
BPELProcessHandle process = (BPELProcessHandle)
l.lookupProcess( (String) list1.get( 0 ),
(String) list1.get( 1 ) );
BPELProcessMetaData ri = process.getMetaData();

int i = 0;
if( lifecycle != -1 )
{
if( ( ri.isLifecycleActive() &&
lifecycle == IBPELProcessConstants.LIFECYCLE_RETIRED ) ||
( ! ri.isLifecycleActive() &&
lifecycle == IBPELProcessConstants.LIFECYCLE_ACTIVE ) )

{
ri.setLifecycle( lifecycle );
i++;
}
}
if( state != -1 )
{
if( ( ri.isStateOn() &&
state == IBPELProcessConstants.STATE_OFF ) ||
( ! ri.isStateOn() &&
state == IBPELProcessConstants.STATE_ON ) )
{
ri.setState( state );
i++;
}
}
if( i > 0 )
process.updateMetaData( ri );

n1++;
}
}
}
catch( Exception e )
{
e.printStackTrace();
}
%>

<%= I18nUtil.getString("title", BuildInfo.getVersion(), locale)%>

<%= I18nUtil.getString("bulk_update_processes_complete", locale)%>

<%= n1 == 1 ? I18nUtil.getString("one_process_updated",
Integer.toString(n1), l.getDomainId(), locale) :
I18nUtil.getString("many_process_updated",
Integer.toString(n1), l.getDomainId(), locale) %>
<%
if( n0 > 0 && n0 != n1 )
{
String mesg = "";
if(n0 == 1 && ((n1 - n0) == 1) )
mesg = I18nUtil.getString("one_process_one_error",
Integer.toString(n0), Integer.toString((n1 - n0)), locale);
if(n0 != 1 && ((n1 - n0) == 1) )
mesg = I18nUtil.getString("many_process_one_error",
Integer.toString(n0), Integer.toString((n1 - n0)), locale);
if(n0 == 1 && ((n1 - n0) != 1) )
mesg = I18nUtil.getString("one_process_many_error",
Integer.toString(n0), Integer.toString((n1 - n0)), locale);
if(n0 != 1 && ((n1 - n0) != 1) )
mesg = I18nUtil.getString("many_process_many_error",
Integer.toString(n0), Integer.toString((n1 - n0)), locale);
%>
<%= mesg%>
<%
}
%>

Overule the BPEL instance name

2007-03-10T21:28:00.000+05:30

When running BPEL processes, the BPEL consolse is showing the status of the process. This is nice, but when you have hundreds or even thousands process instances, is hard to known for which payload the process instance is running.

A nice feature is to manipulate the title of the process. The maximum lenght of the title is 50 characters.

Create a Java step after the first step in your process. You can use the data of the payload to put this in the title:

Element inVarElem = (Element)getVariableData("inputVariable"
, "payload"
, "/client:HelloWorldProcessRequest/client:input");
try
{
String inputdata = inVarElemOrpsId.getNodeValue();
String title = "HelloWorld " + inputdata;
setTitle(title);
addAuditTrailEntry("New Title is: >" + title + "<");
}
catch (Exception ex)
{
ex.printStackTrace();
}]]>

Access to SOAP Header from response payload

2007-03-07T23:48:00.000+05:30

As I was trying to explain the difference between SOAPElement (a.k.a. XMLElement or Element in the java world) and Document, I got to realized that this know-how could be usefull when you need to access the content of the soap:header that is comming back from the service endpoint on the response.

To illustrate this technique, I'll be using WS-Addessing and the .NET endpoint Microsoft exposes for testing purposes (http://131.107.72.15/WSAddressingCR_Service_WCF/WSAddressing10.svc).

In my test scenario, the request looks like this

http://example.org/action/echoIn

http://www.w3.org/2005/08/addressing/anonymous

http://131.107.72.15:80/WSAddressingCR_Service_WCF/WSAddressing10.svc/Soap12

test1132

For now, I'll assume that you can figure out the way to send the proper SOAP Header in the request, and point you at the documentation if you need further information about JAX-RPC handlers.

To construct the client, you can use the following ant target:

The trick to get access to the soap:header in the response is as follow:

use the databinding="false" option on the o:genProxy command - this will change the method signature of your java code, and give you access to the raw XML.
from the SOAPElement you are getting in return, get back to the containing XML Document - the soap:envelope. Once you have it, you can access any value from the soap:header
It's that simple. The draw back of this is on the java side - now, you have to construct the SOAP request and decode the SOAP response by hand. It's only a temporary solution, until we get to J2SE 6.0 and JAX-WS.

code snippet:
SOAPElement result = myPort.echo(input);
System.out.println("result as SOAPElement");
((XMLElement) result).print(System.out);
System.out.println("result as Document");
((XMLElement) result.getOwnerDocument().getDocumentElement()).print(System.out);

output:

result as SOAPElement
test1132
result as Document

http://example.org/action/echoOut

test1132

In this example, the a:Action header is not that usefull, but imagine you can gain access to a:RelatesTo or a:MessageID using the same technique.

Have fun!!!

WS 10.1.3.1 faultcode - env:Server UndeclaredThrowableException

2007-03-07T23:47:00.002+05:30

WS 10.1.3.1 faultcode of the day - env:Server UndeclaredThrowableException
Here is an error that I have seen a few time in the past days, for which I have not find an easy way around. Just a user error, hard to catch...

env:Server
Internal Server Error (Caught exception while handling request: java.lang.reflect.UndeclaredThrowableException)

In playing with the 'mapheaderstoparameters' option for the topDownAssemble target, I forgot to change the method signature on the implementation class before to repackage my application. When the code generated at deployement time does not match with the code packaged in your application, this is the error you may get.

Until we get smarter in the code generation and have dynamic services with pre-deployment check, the best remains to make a knot on your handkerchief.

SOAPFaultException: IllegalArgumentException: Decoding tip

2007-03-07T23:47:00.001+05:30

I have a new not-so-easy error to explain and share with you.

Here is how the error will reads from the client side, when using Oracle Web Services tech Stack on the 10gR3 releases:

javax.xml.rpc.soap.SOAPFaultException: Caught exception while handling request:
deserialization error: java.lang.IllegalArgumentException

The SOAP response will look something like that:

1 2 3 4 5 env:Client 6 Caught exception while handling request: deserialization 7 error: java.lang.IllegalArgumentException 8 9 10

In my case, the error was just because I was having an invalid value
for some XML Schema type - the incomming value was not in the set
defined in the schema.

1 6 ... 7 8 9 10 11 12 13 14 15 ...16

Hope it can help some of you out there, getting to the bottom
of your interoperability issues faster.

BPEL: java.lang.NullPointerException: domain was null

2007-03-04T00:07:00.000+05:30

Today 7 colleaques from different departments reported the following..

When we try to connect to a BPEL server from a j2ee application we get the following


java.lang.Exception: Failed to create "ejb/collaxa/system/DomainManagerBean" bean;
exception reported is: "java.lang.NullPointerException: domain was null
at com.evermind.server.rmi.RMIServer.addNode(RMIServer.java:779)
at com.evermind.server.rmi.RMIServer.getConnection(RMIServer.java:848)
at com.evermind.server.rmi.RMIInitialContextFactory.
getInitialContext(RMIInitialContextFactory.java:206)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

if we try the same from a local java app an connect to a standalone server, everything works fine ..

The solution:
setting the following property before using the Locator API
props.setProperty("dedicated.rmicontext","true");

Locator locator = new Locator("default","bpel", props);

BPEL: Scheduling reoccuring processes

2007-03-04T00:04:00.000+05:30

After seing some questions around periodically starting new BPELProcess instances, I thought to publish some ideas here...

Suppose you want to have a new process triggered every minute, what are the options?

Implement a master process, that has a
and a
that is configured for the time to make the process sleepling
- Advantage: It's BPEL
- Disadvantage: As it contains a wait and some other activities that might lead to (de)hydration, you fill you database

Use the Oracle RDBMS Job Scheduler (dbms_job package) that will start your process periodically
- Advantage: One time implemented, backed up with the DB, and pattform independend
- Disadvantage: It's bound to an Oracle DB, and you need to know at least some pl\sql, the rest is java

Use a Timer EJB (provided with a j2ee compliant java container)
- Advantage: it's a statefull bean, so it will get saved, and revovered when the container goes down, use java to implement
- Disadvantage: Dependend on the container you are using

Use QUARTZ, the open source scheduler
- Advantage: It's opensource and Oracle BPELPM uses it for scheduling

Stamp of approval on JDeveloper 10.1.3.1

2007-03-04T00:01:00.000+05:30

I have been working with the new developer release for a while now and have found it to be very stable. There are some really nice problems that were corrected from the previous version like XPath specifications in XSL document. You may ask, "what do I care about JDeveloper if I am using Siebel?" Good question, with lots of answers:

JDeveloper is FREE! Not only can you use it but so can your clients.
Editing XSD is a real pain without an editor. However, make sure you also set up the WS-I validation tool.
Editing WSDL is also a real pain unfortunately even with an editor. But hey, you really need to get to know this at a low level anyway. Once you get used to the JDeveloper editor it is pretty good. Unfortunately the validation is not as strong as I would like to see.
XSL TRANSFORMS!!! One of the biggest features is that you can use the XSL editor which is a huge time saver. I have to admit though that it is easy to confuse the editor via hand edits. Still working on how to avoid that.
Remote debugging. You need a real editor to debug you Siebel business servies. WHAT!? You say you are not using Java business services? Shame on you.

Hidden SOA Suite Downloads!

2007-03-03T23:57:00.000+05:30

Ever noticed when you go camping that you have almost finished putting your tent up and then you find that you are missing some crucial piece, like the guy ropes to stop it blowing away. Well that happened to me today with the SOA Suite downloads. I had downloaded the 1 disk install and that was great, had everything I needed for installing OC4J, BPEL, ESB and OWSM. I then went to install BAM and hit a problem. It didn't seem to be on the downlaod page. Turns out that likes the guy ropes it is tucked away under the instructions at the bottom of the bag, or to be more exact you need to clck the "see all" button to the right of the Linux and Windows SOA Suite downloads on the SOA Suite download page.

Whilst installing BAM I then started up JDeveloper only to realise it didn't have a JVM. I didn't have a 1.5 JVM on my machine so I looked at the downlaod I had and realised it was a generic platform download that didn't include a JVM. I went to the SOA Suite download page and click "all" next to the JDeveloper downlaod and found a version specifically for Windows that included a JDK 1.5.

It's amazing what you find hidden under the instructions!

Deploy OC4J Portal After the install

2007-03-03T23:56:00.002+05:30

This is the procedure for deploying the portal ,

1. Run the script ,

/home/ias904/mid/assistants/opca/launch.sh

2. Then create a file , say dd.txt with the following

UltrasearchAdmin=UltrasearchAdmin,/home/test/mid1/ultrasearch/webapp/ultrasearch_admin.ear,OC4J_Portal,ultrasearch/lib/ultrasearch_query.jar,ultrasearch/webapp/config,jlib/repository.jar,jlib/uix2.jar,jlib/ohw.jar,jlib/regexp.jar,j2ee/home/jazn.jar,jdbc/lib/nls_charset12.zip,RemoveEarfile
UltrasearchQuery=UltrasearchQuery,/home/test/mid1/ultrasearch/sample.ear,OC4J_Portal,ultrasearch/lib/ultrasearch_query.jar,ultrasearch/webapp/config,RemoveEarfile
UltrasearchPortlet=UltrasearchPortlet,/home/test/mid1/ultrasearch/webapp/ultrasearch_portlet.ear,OC4J_Portal,ultrasearch/lib/ultrasearch_query.jar,portal/jlib/ptlshare.jar,portal/jlib/pdkjava.jar,jdbc/lib/nls_charset12.zip,RemoveEarfile
portal=portal,/home/test/mid1/portal/jlib/portal.ear,/home/test/mid1/j2ee/properties/oc4j_portal.properties,OC4J_Portal,portal/jlib/wwjni.jar,j2ee/home/jazn.jar,portal/jlib/ptlshare.jar,opmn/jlib/optic.jar,RemoveEarfile
portal=jpdk,/home/test/mid1/portal/jlib/jpdk.ear,OC4J_Portal,portal/jlib/pdkjava.jar,portal/jlib/portaltools.jar,portal/jlib/ptlshare.jar,portal/jlib/tidy.jar
portal=portalTools,/home/test/mid1/portal/jlib/portalTools.ear,OC4J_Portal,portal/jlib/portaltools.jar,portal/jlib/pdkjava.jar,portal/jlib/ptlshare.jar,portal/jlib/tidy.jar,jlib/uix2.jar,jlib/share.jar,jlib/ohw.jar,RemoveEarfile
portal=portalHelp,/home/test/mid1/portal/jlib/portalHelp.ear,OC4J_Portal,jlib/regexp.jar,jlib/ohw.jar,RemoveEarfile
syndserver=syndserver,/home/test/mid1/syndication/j2ee/syndserver.ear,OC4J_Portal,syndication/lib/jr_dav.jar,jlib/regexp.jar,jlib/repository.jar,jlib/ldapjclnt9.jar,jlib/uix2.jar,jlib/share.jar,jlib/ohw.jar,RemoveEarfile,JAZN=LDAP
syndserver=syndprovider,/home/test/mid1/syndication/j2ee/syndprovider.ear,OC4J_Portal,syndication/lib/jr_dav.jar,jlib/regexp.jar,portal/jlib/pdkjava.jar,portal/jlib/portaltools.jar,portal/jlib/ptlshare.jar,jlib/uix2.jar,jlib/share.jar,jlib/ohw.jar,RemoveEarfile,JAZN=LDAP
orauddi=orauddi,/home/test/mid1/uddi/j2ee/orauddi.ear,OC4J_Portal,jlib/uix2.jar,jlib/share.jar,jlib/ohw.jar,jlib/regexp.jar,jlib/repository.jar,jlib/ldapjclnt9.jar,RemoveEarfile,JAZN=LDAP
orauddi=oraudrepl,/home/test/mid1/uddi/j2ee/oraudrepl.ear,OC4J_Portal,jlib/repository.jar,jlib/ldapjclnt9.jar,RemoveEarfile,JAZN=LDAP

3. Run the following command to deploy the above applications in OC4J_Portal

/home/test/mid1/jdk/bin/java -Djava.io.tmpdir=/tmp -mx512M -classpath /home/test/mid1/dcm/lib/dcm.jar:/home/test/mid1/dcm/lib/oc4j_deploy_tools.jar -Doracle.ias.sysmgmt.logging.logdir=/home/test/mid1/j2ee/home/log oracle.j2ee.tools.deploy.Oc4jDeploy -oraclehome /home/ias904/mid -verbose -inifile /tmp/dd.txt

4. Create the DAD from EM for the /pls/portal ,

restart the OHS and OC4J_Portal ,

The above steps will configure the portal after the install , (when you choose not to install the Portal at the install time )

How to use the DoNotReGenerateWrapperCode OC4J option

2007-03-03T23:56:00.001+05:30

First run the OC4J with the option ,

java -DKeepWrapperCode=true -jar oc4j.jar

This generates the .java files in say c:\oc4j904\j2ee\home directory

Now edit the appropiarte file , and add your own code and some System.out.println codes etc ,after this just save the files.

Now start the OC4J container , with the following options

java -DDoNotReGenerateWrapperCode=true -DKeepWrapperCode=true -jar oc4j.jar

After this redeploy the application again , you will see messages like ,

04/11/24 18:00:47 Skip re-gen of EmpHome_EntityHomeWrapper19.java
04/11/24 18:00:47 Skip re-gen of Dept_EmpLocal_ORCollection11.java
04/11/24 18:00:47 Skip re-gen of DeptHome_EntityHomeWrapper29.java
04/11/24 18:00:47 Skip re-gen of DeptLocalHome_EntityHomeWrapper27.java

Now run your application.

How the DCM and OPMN gets the database users and passwords from OID

2007-03-03T23:54:00.000+05:30

The RepAPI reads the file
$OH/config/ias.properties

It gets the values like ,

OIDhost=incq128ad.idc.oracle.com
OIDport=3060
OIDsslport=3131
SSLOnly=false

This try to connect to the OID using the above and looks for the database defined in ,

InfrastructureDBCommonName=ORCL

For example , cn=ORCL,cn=OracleContext

From the above it gets the connect string from the attribute , "orclnetdescstring"

After this REP Api issues the SSL ldap queryto find out ,

orclReferenceName=,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext

for example ,

orclReferenceName=ORCL,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext

From the above it gets the value for the DCM and portal password etc ,

OrclResourceName=DCM,orclReferenceName=ORCL,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext here it looks
for the attribute ,

"orclpasswordattribute" , usin this info the DCM connects to the database using the thin JDBC driver ,

Similiary the opmn will also connect to the database when the depandancies against the database are used.

BPM on SOA and the role of change management

2007-02-28T00:11:00.000+05:30

Bruce Silver wrote a nice post on BPM and SOA.I agree on his analysis that these 2 worlds are slowly merging. An Service Oriented Architecture will only be efficient when the business processes on top of it are efficient. It is good to see that the Oracle SOA Suite gets more and more tooling for Business Process Analysis (BPA), simulation and Business Activitity Monitoring (BAM). The tools you need for process improvement or BPM.
In my opinion change management also plays a central role in both BPM and developing a SOA. The changes IT has on the business is known. But why is IT only managing the changes in the software and not the changes it imposes on the organization? The currently known software development methodologies also don’t have an answer for this question.
In a recent post I showed the impact of a SOA implementation and the effect of an intervention on adoption of a new system and new business processes. It shows that the use of techniques from requirement engineering and change management pay off.
In the BPM world change management is more common ground. Only I also see an emphasis on tooling and techniques. I hope that with the merging of BPM, SOA and change management the gap between business and IT will be closed and we will add more value to the business. In the end this is the only Key Performance Indicator IT will be measured against.

Out of memory (java.lang.OutOfMemory) running Oracle BPEL Process Manager

2007-02-28T00:09:00.000+05:30

Running Oracle BPEL requires a lot of reflective data, i.e. class and method objects, to be held by the Java virtual machine. This type of data is stored in a memory structure called the “permanent generation”. The default size for the permanent generation (64M) is for most applications sufficiently large.
But if you deploy the Oracle BPEL Manager together with one or more JSP applications into a single Oracle container you will most probably hit an out of memory exception. Raising the maximum heap size using the option -Xmx does not prevent the exception from occuring, since this option will only effect the young generation and the tenured generation. The permanent generation will never be visited by a minor or full garbage collection!
You should increase the permanent generation by using the option -XX:MaxPermSize=. You can determine a correct maximum by running the container using the option -XX:+PrintHeapAtGC. This setting tells you something like the following:
PSPermGen total 61952K, used 61951K [0x851c0000, 0x88e40000, 0x891c0000)However, I’m sure that using a value of 256M will always be large enough.
For more info you should visit Tuning Garbage Collection

Application Server Control of Oracle SAO Suite not reachable

2007-02-28T00:06:00.000+05:30

When you install the Oracle SOA Suite (10.1.3.1) and navigate to the Enterprise Manager’s Application Server Control you will hit a 404 Page not found exception.Application Server Control has no routing relationship (see 10g3 New Features overview) with the Oracle HTTP Server by default. To establish this relationship you have to set the ohs-routing attribute to true (default false) in the default-web-site.xml file (/j2ee/home/config) of the home container:
Do not forget to restart the home container to let the changes take effect.

BPEL sample worklist

2007-02-28T00:05:00.000+05:30

When doing a BPEL project which processes contains user tasks – actions which need to be performed by the users – there are two options.1. Build your own worklist based on the Worklist API.2. Use the default worklist which is provided by Oracle in the SOA suite. Since the default worklist contains all functionality we need for our project we decided to save ourselves some time building our own and use the oracle default worklist. However some modifications are still necessary. We want to use jsso instead of the worklist login. We also want to change some visual aspects like branding and the look-and-feel.
Oracle describes all the steps to create your custom worklist application. It even includes documentation on how to make the application jsso enabled. However they assume you are working from the application server where the samples are installed and that you leave it there. For me, and I think for many people this is not an option.I copied the worklist from the app server to my desktop and created a JDeveloper workspace & project from it. I changed the code to make the worklist jsso enabled and created a deployment descriptor for easy deployment. It took me some gathering all the required library’s which are not documented by Oracle. Turns out you need the BI-Beans jars and uix2.jar for the graphs. What I want to do next is run my worklist application from the Jdeveloper embedded OC4J so I can do some developing/debugging. To do so I need to change the way the worklist connects to bpel from JAVA_CLIENT to REMOTE_CLIENT.I included the bpel jars to the project, created a wf_client_config.xml file on the classpath, changed the connection to remote and deployed. Whatever I do, I cannot get a connection to the worklist. For now I will settle deploying the worklist to the soa-oc4j as a child of orabpel.
When diving into the worklist code it strikes me the way the worklist is build. It is a Model 1 jsp servlet application with lots of scriplet code. This makes modification and maintenance quite hard. I thought we had had left this kind of programming behind us and moved on to Model 2 MVC applications. Especially Oracle with it’s own MVC framework (ADF) should be able to do better I think. After going through all the trouble of getting the sample worklist running I wonder if it might be smarter to build your own worklist.

Automaticly restarting BPEL processes

2007-02-28T00:03:00.000+05:30

At the moment we have a SOA/ BPEL project in production for quite some time. One of the lessons we have learned will be the topic of this post: automaticly restarting BPEL processes.
In this case a process is divided into one root process and a number of subprocesses. The root process is started when a custormer applies for a specific test in a laboratorium. After the application a number of tests (subprocesses) are carried out. After 30 to 50 days the results are returned to te customer. At the moment their are 180.000 process instances, of which approximately 25-30.000 are still active.
We (and the customer) are very pleased with the results Oracle BPEL is bringing. But the implementation of a new product can give you some headache (Out of memory ) As a result of this bug BPEL instances went on abort. The tasks disappair in the worklist and users start calling. They want their tasks back….
At first we kicked off the root BPEL process from the BPEL Console and acquired the tasks and entered the recovered data. We restarted the BPEL proces manualy. This is nice break for 1 or 2 tasks, but becomes expencive when 100 tasks have to be restarted within a few hours. Here is where our creativity came in.
We have developed a webservice to collect all data to kickoff the root BPEL process and data the users entered. The payload for kicking off the root BPEL process is assembled by looking at the xml structure in the BPEL Console.
SELECT '
02006'
decode(p_action,'RESET',a.nummer_aanvraag,0)' 'chr(10)
'' rle.nummer' 'chr(10)
'' kot.ID' 'chr(10)
'' avrg.aantal_verpakkingen ''chr(10)
'' lower(avrg.verpakkingsvorm) ' 'chr(10)
'' avrg.gewicht_totaal ' 'chr(10)
''decode(p_action,'RESET','HERSTEL;'substr(bmr.nummer,2),'MONSTERONTVANGST')''
INTO l_payload
FROM avrg_aanvragen avrg
, kot_keuringsobjecten kot
, kot_basismonsters bmr
, rle.rle_relaties rle
WHERE a.kot_id=b.id
AND c.avrg_id=a.id
AND c.nummer=upper(p_werkmonster)
AND a.rle_id=e.id
AND a.id=r_avrg.avrg_id;
The payloads of the task is found in the BPEL dehydration store. We are storing the process instance id of the root process in our data store. With this id you can find all the child processes in cube_instance in the dehydration database. For every child we fetch the taskid form pc_taskand collect the last payload in the table pc_taskpayload. This payload consists the data the user entered while updating the task. Before returning all payloads to the GUI the old process and subprocesses are deleted.
The GUI will first kick off the BPEL process. Then get the first task and give the collected payload too the taskhandler. This is repeated until the BPEL process is restarted.

High CPU Usage Java

2007-02-26T22:54:00.000+05:30

Add this variable to opmn.xml fileias-instance id="j2ee2.asdtbde.idc.oracle.com"environmentvariable id="TMP" value="/tmp"variable id="LD_ASSUME_KERNEL" value="2.4.1"variableFind out the java process using the commandopmnctl statusand not down the PIDopmnctl statusProcesses in Instance: j2ee2.asdtbde.idc.oracle.com-------------------+--------------------+---------+---------ias-component process-type pid status-------------------+--------------------+---------+---------DSA DSA N/A DownLogLoader logloaderd N/A Downdcm-daemon dcm-daemon N/A DownOC4J home 28370 AliveWebCache WebCache 28380 AliveWebCache WebCacheAdmin 28371 AliveHTTP_Server HTTP_Server 28373 AliveUse this command to find out the actual process ID , In this case the actual java process is ,28377.ps -ef grep 28370rac 28370 28354 0 11:23 ? 00:00:01 /home/rac/j2ee2/jdk/bin/javarac 28377 28370 0 11:23 ? 00:00:00 /home/rac/j2ee2/jdk/bin/javaRun the command ,watch "ps -eLo pid,ppid,tid,pcpu,comm grep 28377"Find out the therad ID which taking lot of CPU time ,i.e it should be there in the first columnNow take the thread dumpkill -3 28370 (process-id-from-opmn-status-output)Convert the Thread ID you got from the command ,ps -eLo pid,ppid,tid,pcpu,comm grep 28377hexadecimal and then search for this value in the thread dump.For the JDK 5.0 you do not need to the LD_ASSUME_KERNEL etc.Please also check the Articlehttp://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_18339

How to find which file is opened on windows (similar to fuser in linux)

2007-02-26T22:53:00.000+05:30

Download the tool from http://www.microsoft.com/technet/sysinternals/utilities/handle.mspxEver wondered which program has a particular file or directory open? Now you can find out. Handle is a utility that displays information about open handles for any process in the system. You can use it to see the programs that have a file open, or to see the object types and names of all the handles of a program. handle.exe > dd.txt will get all the fileshandle AppEvent.evtHandle v3.2Copyright (C) 1997-2006 Mark RussinovichSysinternals - www.sysinternals.comservices.exe pid: 1224 2D0: C:\WINDOWS\system32\config\AppEvent.evt

How to use UTL_DBWS in 10.2 Database

2007-02-26T22:52:00.000+05:30

Set the following in the init.ora file 1. java_pool_size big integer 96Mshared_pool_size big integer 104M2. Download the LATEST copy of the UTL_DBWS utility zip file from the Oracle Technology Network (OTN). This file, for a 10g database, is named dbws-callout-utility-10131.zip and can be obtained from here.http://download.oracle.com/technology/sample_code/tech/java/jsp/dbws-callout-utility-10131.zip3. Load this packages to the database using the command ,loadjava -u sys/welcome -r -v -f -s -grant public -genmissing sqlj/lib/dbwsclientws.jar sqlj/lib/dbwsclientdb102.jar 4. As a sys user run the following commands ,execute dbms_java.grant_permission('SCOTT','SYS:java.util.PropertyPermission','http.proxySet','write');execute dbms_java.grant_permission('SCOTT','SYS:java.util.PropertyPermission','http.proxyHost', 'write');execute dbms_java.grant_permission('SCOTT','SYS:java.util.PropertyPermission','http.proxyPort', 'write');execute dbms_java.grant_permission('SCOTT','SYS:java.lang.RuntimePermission', 'accessClassInPackage.sun.util.calendar','');execute dbms_java.grant_permission('SCOTT','SYS:java.lang.RuntimePermission','getClassLoader','');execute dbms_java.grant_permission('SCOTT','SYS:java.net.SocketPermission','*','connect,resolve');execute dbms_java.grant_permission('SCOTT','SYS:java.util.PropertyPermission','*','read,write');execute dbms_java.grant_permission('SCOTT','SYS:java.lang.RuntimePermission','setFactory','');commit;5. Start the 10.1.3.1 J2EE Container and deploy the application javacallout.ear 6. Run the following pl/sql command to check the pl/sql web servicesset serveroutput on size 999999declareservice_ sys.utl_dbws.SERVICE;call_ sys.utl_dbws.CALL;service_qname sys.utl_dbws.QNAME;port_qname sys.utl_dbws.QNAME;operation_qname sys.utl_dbws.QNAME;string_type_qname sys.utl_dbws.QNAME;retx ANYDATA;retx_string VARCHAR2(100);retx_len number;params sys.utl_dbws.ANYDATA_LIST;beginservice_qname := sys.utl_dbws.to_qname(null, 'HelloServiceEJB');service_ := sys.utl_dbws.create_service(service_qname);port_qname := sys.utl_dbws.to_qname(null, 'HttpSoap11');operation_qname := sys.utl_dbws.to_qname('http://oracle.j2ee.ws/javacallout/Hello/types', 'sayHelloElement');call_ := sys.utl_dbws.create_call(service_, port_qname, operation_qname);sys.utl_dbws.set_target_endpoint_address(call_, 'http://indl224ad.idc.oracle.com:8082/javacallout/javacallout');--sys.utl_dbws.set_property(call_, 'ENCODINGSTYLE_URI', 'http://schemas.xmlsoap.org/soap/encoding/');string_type_qname := sys.utl_dbws.to_qname('http://www.w3.org/2001/XMLSchema', 'string');sys.utl_dbws.add_parameter(call_, 'String_1', string_type_qname, 'ParameterMode.IN');sys.utl_dbws.set_return_type(call_, string_type_qname);params(0) := ANYDATA.convertvarchar('hello');retx := sys.utl_dbws.invoke(call_, params);retx_string := retx.accessvarchar2;dbms_output.put_line('PL/SQL DII client return ' retx_string);end;/

How to find the Symbols available in a DLL

2007-02-26T22:51:00.000+05:30

Download the utility Dependency Walker from http://www.dependencywalker.com/.Extarct the files in a c:\windows\system32 direcorty and open the.dll file. In the Second right hand side windows select all function nameand copy to clip board.