Search This Blog
Friday, June 24, 2011
Friday, January 28, 2011
BPEL Checklists and Tracing the issues
A]Files not picked up
Reasons could be:
Same file name - Rename file
Process is turned OFF - Turn it ON
FTP Adapter shut down - Reset Polling timer
Server Error - Reboot server/ Redeploy process
B]Data not loaded
Check the DB Connection settings
ODIADM user id should be present and should have rights to loading tables
In case of Issues, the following trouble shooting methods can be followed:
Look into the details like:
- the email error notifictaion,
- if there was anything different from usual, was it larger size file etc
- Was the input file re-tried and loaded successfully or not? etc
- Input Data file that caused the error
- Log file (OPMN.log) detail
Configuration checklist:
JDBC configuration:
JNDI and DB Adapter
Connection pool, datasource
JNDI and DB Adapter
Logon to the console Applications View drop down Standalone Resource Adapters DB Adapters Connection Factories
(The JNDI Location property would need to match the JNDI Location property in the datasource settings of JDBC configuration )
Connection pool, datasource:
Logon to the console Administration Services JDBC Resources
(The connection pool and datasource name could be tested by clicking the Test_Connection icon)
FTP configuration:
FTP Adapter
Logon to the console Applications View drop down Standalone Resource Adapters FTP Adapters Connection Factories
(Click the JNDI used in the code. Properties like Userid and Password need to be checked.Also the SFTP hostname, port-number could be checked)
Build.properties file:
Verify all the parameters in the build.properties file
CommonHandler Service:
The CommonHandler service used for sending error notifications need to be deployed in the respective domain where the other BPEL objects are deployed.
Email File:
The ns_email.xml file in the BPEL domain need to be configured to include the email properties of the domain viz. From, alias name
Control File:
The control file for each of the BPEL transactions need to be present in the FTP directory
Wednesday, January 12, 2011
BPEL deploy.chunk.size Error
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{code=<code>null</code>
,summary=<summary>file:/usr/local/cny/cu7/bp1013/product/10.1.3.1
Error occured while translating content from file ftpxfr/140001/SA1_10008 [Caused by: For input string: "[undef:deploy.chunk.size]"]
; nested exception is:
ORABPEL-11008
Error while translating.
Error occured while translating content from file ftpxfr/140001/SA1_10008 [Caused by: For input string: "[undef:deploy.chunk.size]"]
Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
</summary>
,detail=<detail>null</detail>
}}
Solution:
The chunk size in the build.properties file was undefined/missing. Deploy the BPEL process with chunk size with some number.
Tuesday, September 15, 2009
How BPEL adds value to PeopleTools 8.48?
One of the key enhancements delivered in PeopleTools 8.48 was integration with Oracle BPEL Manager. Oracle's description of BPEL is:
Oracle BPEL Process Manager, a member of the Oracle Fusion Middleware family of products, enables enterprises to orchestrate disparate applications and Web services into business processes. The ability to quickly build and deploy these processes in a standards-based manner delivers critical functionality for developing a Service-Oriented Architecture (SOA).
Now... how this translates into real-world cases?
Recently, we had to design for one of our customers a Web Service based integration of PeopleSoft Financials with a Third Party Billing system. One of the integrations consisted in the Third Party system sending information to PeopleSoft Financials in order to perform the following actions:
Create the customer if it was not present.
Create the invoice as a pending item in PeopleSoft Receivables module.
Run Receivables Update process.
Create the deposit and apply it to the item.
Run Receivables Update process again to update customer's balance.
Before BPEL, if we wanted to create this integration, a solution would have to create a Web Service in PeopleSoft that encapsulates all these activities. The problem of this approach is that this new Web Service would not easily reusable, as most consumer applications will only require part of the operations performed in it.
With BPEL, we can keep Web Services at the right granularity to help making them reusable. Following with the example, we would just make sure the following Web Services exist (taking into account that some of them may be already available in the delivered product):
· Customer creation.
· Pending item creation.
· Receivables update processing.
· Deposit creation and application.
BPEL would then be used to orchestrate these Web Services, without requiring to build aggregated and poorly reusable Web Services in PeopleSoft.
In summary, BPEL seems to bring PeopleSoft applications to the next level in what relates to integration with Third Party applications. Also, being BPEL one of the keystones of Oracle Fusion Architecture, it seems a wise decision to gain some BPEL experience as this might be a highly demanded skill in the near future.
Note: Although Oracle ships its BPEL Manager product together with PeopleTools 8.49, this license only covers design-time use. For runtime use, you should purchase Oracle BPEL Manager separately. For more information, please refer to:
http://download.oracle.com/docs/cd/E05453_01/psft/acrobat/pt849_lic_notes.pdf
CTY: Javier Delgado |