Oracle Applications Integration Architecture Agile PLM ... · Objects (EBOs) that are NOT in scope...

<Insert Picture Here>

Oracle Applications Integration Architecture

Agile PLM Integration Pack for Oracle E-Business Suite

Licenses and Troubleshooting

• Licenses

• Troubleshooting

• Common Issues

• Location of Logs

• Generic Process for Gathering Information for a Run Time Error BPEL.

• Generic Process for Gathering Information for Install and Configuration Issues.

Agenda

© 2011 Oracle Corporation – Proprietary and Confidential2

What Technology and Application Products are included?

Process Integration Packs

• Includes Restricted Use License (RUL) of:

• WebLogic Suite

• SOA Suite

• Oracle Database EE

• Oracle Applications Adapter *

• Oracle Data Integrator *

• AIA Foundation Pack

Base application enhancements

BPA Suite Business Process Publisher

• Does NOT include Participating applications or modules


AIA Foundation Pack

SOA

Suite

WebLogic

Suite

Oracle Database EE

ODI

Oracle Applications Adapter

Runtime Components

* Optional, not used in every integration

Licenses

What Triggers Full Use License of Technology Products?

Two Scenarios

1st Scenario:

Customer wishes to add a new application system (Oracle or non-Oracle) that is NOT one of the original integrating apps

Full Use Licenses required:

WebLogic Suite (for IAS EE)

SOA Suite

Oracle Database EE

Oracle Applications Adapter *

Oracle Data Integrator *


AIA Foundation Pack

SOA

Suite

WebLogic

Suite

Oracle Database EE

Runtime Components


ODI


Licenses

What Triggers Full Use License of Technology Products?

Two Scenarios

2nd Scenario:

Customer uses Enterprise Business Objects (EBOs) that are NOT in scope of the delivered integration

Full Use Licenses required:

AIA Foundation Pack

WebLogic Suite (for IAS EE)

SOA Suite

Oracle Database EE

Oracle Applications Adapter *

Oracle Data Integrator *


AIA Foundation Pack

SOA

Suite

WebLogic

Suite

Oracle Database EE

Runtime Components


ODI


Licenses

Direct Integrations

What Technology and Application Products are included?

• Includes Restricted Use License (RUL) of:

• WebLogic Suite *

• SOA Suite or BPEL PM *

• Oracle Applications Adapter *

• Oracle Data Integrator *

Base application enhancements

• Does NOT include Participating applications or modules

Direct Integrations

SOA

Suite or

BPEL PM

WebLogic

SuiteODI


Runtime Components


• Full use license is triggered Customer wishes to add a new entity/data object

synchronization that is NOT in scope of the delivered integration

Licenses

• Issue: Once the ECO/MCO/SCO has been released in Agile, the queue does not

display any corresponding entry for the change order.

1. Check that the transmission of the ATO that was created and released in Agile was

successful. Check the status on the “Where Sent” tab of the ATO.

• Create an Advanced Search in Agile to find the ATO associated with the ECO.

Troubleshooting




• Check the status on the “Where Sent” tab of the ATO.

• Agile had an issue sending the ATO to FMW, if the “Transmission Status” says

Failure.

Troubleshooting




2. Alternatively, to find other ATOs that may have errored. Login to the Java Client.

3. Select the “Advanced Search” button. Choose ATO as the Object Type, Selected Content

Search as the Search Type, and Changes as the With Related Content.

Troubleshooting




4. Select the “Where.Sent.Transmission Status” and select all statuses other than Success.

Click Run.

Troubleshooting


• Issue: Once the ECO/MCO/SCO has been released in Agile, the queue does

not display any corresponding entry for the change order.

5. To reset the destination, go to Admin, System Settings, Agile Content Services, and

Destinations.

6. Select the particular destination and click the “Reset” button on the top.

Troubleshooting


• Issue: The status of the concurrent program request for one of the Reverse

flows in Ebiz is “Error”

1. If the concurrent program request shows an error status, in the “View Request” tab,

select the row with the error and click on the “View Log” button.

Troubleshooting




2. The error message is displayed there. If further details are required on the process

instance that caused the error, note the BPEL process instance that appears in the log

file.

Troubleshooting




3. Navigate to the BPEL Console: http://<SOAHOST>:<SOAPORT>/BPELConsole

4. Click on the “Instances” tab and search for the specific instance ID.

Troubleshooting




5. Click on the Instance Name and go to the “Flow” link. In the BPEL flow shown, find the

element at which the error has occurred.

Troubleshooting




6. Click on the element to view the Activity Audit trail which will have the details of the error.

Troubleshooting


• Issue: Create ECO flow gives the error message “following user does not have the

PersonalId attached to it”.

1. Check whether Ebiz Integration user specified in the AIAConfigurationProperties.xml is correct

user or not.

<ModuleConfiguration moduleName="Ebiz">

<Property name="USER">sysadmin</Property>…

2. If the user is correct then check whether the integration user has a person name assigned in

system Administrator responsibility.

3. If the user is not assigned please assign the valid user.

Troubleshooting


• Issue: Unable to establish connection to “EbizConnectionPool”.

1. Login to http://<SOAHOST>:<SOAPORT>/em and go to oc4j_soa, Administration, JDBC

Resources, Connection Pools, select “EbizConnectionPool”.

2. Click Test Connection, if the connection does not validate, check the connection pool details

(username, password, host, port…)

3. Also verify the details for “EbizDBPool” (should be the same as “EbizConnectionPool”).

Troubleshooting


• Issue: Create an ECO fails with an error “The SQL Exception is:

“javax.resource.ResourceException: RollbackException: Transaction has been

marked for rollback: Timed out””.

1. Increase the timeout values: For example, for 100 Affected Items [without any BOM Data]

being created in Ebiz through a Change Order released from Agile.

• <SOA_ORACLE_HOME>/bpel/domains/<domain_name>/config/domain.xml

• Property to modify: syncMaxWaitTime, Sample Value=120

• <SOA_ORACLE_HOME>/integration/esb/config/esb_config.ini

• Properties to Modify:

• xa_timeout, Sample Value=120

• jms_receive_timeout, Sample Value=120

• <SOA_ORACLE_HOME>/j2ee/<domain_name>/application-

deployments/orabpel/ejb_ob_engine/orion-ejb-jar.xml

• Property to Modify: transaction-timeout, Sample Value=120

• <SOA_ORACLE_HOME>/j2ee/<domain_name>/config/transaction-manager.xml

• Property to Modify: transaction-timeout, Sample Value=120

Troubleshooting


• Issue: Concurrent Program Failed

1. Check whether the Profile values for EBS Integration Proxy Server Host, EBS Integration

Proxy Server Port are configured correctly in the profiles screen.

2. If not then fill in the fields below:

• EBS Integration Proxy Server Host - set it to the <soahost>

• EBS Integration Proxy Server Port – set it to the <soaport>

• EBS Integration Server Domain – set it to the word “default” (no quotes)

• EBS Integration Server Host:Port – set it as http://<soahost>:<soaport>

• EBS Integration Debug Directory – set it to the directory location where you’d want

debug logs to be printed out.

• EBS Integration Option – set it to “yes” (no quotes) if you want logging turned on.

Troubleshooting


• Issue: After an unsuccessful installation/uninstallation FP cannot be reinstalled

to the same directory location and complains that FP is already installed.

1. Stop SOA Server

2. Go to <SOA_ORACLE_HOME>/opmn/conf/opmn.xml

• Go to process-type (defines the JVM) under /opmn/process-manager/ias-instance/ias-

component corresponding to the SOA JVM in use.

• Delete the entire line: -Daia.home=<AIA_HOME>

3. Start SOA Server

Troubleshooting


• Location of Logs

1. FMW

• <SOA_ORACLE_HOME>/opmn/logs/default_group~oc4j_soa~default_group~1.log

• oc4j_soa being your managed server name

2. Agile

• OAS

• <AGILE_HOME>/agile/Domain/log/agile.log

• WLS

• <OAS_HOME>/j2ee/home/log/*.log

3. Ebiz

• Set the following Ebiz Profile Options in Ebiz UI:

• EBS Integration Debug Directory - see the previous slide

• EBS Integration Debug Option – see the previous slide, if left blank, logging is

disabled.

• Once logging is enabled it will generate a log file in the path mentioned in EBS

Integration Debug Directory. The file name will be EBS<ddmmyyyyhh24miss>.log .

Troubleshooting



1. Check the queue (for ECO/MCO/SCO, Process or Validate)

• If record is ERRORED, click the “ERRORED” link to see the error message and note

the Id Number (e.g. 390031)

Troubleshooting



2. Check the BPEL Console, To determine where the actual error message is coming from in

the flow. Search for the Instance Id

Troubleshooting



3. Open the instance and drill Into the flow and find the activity that errored.

4. Sometimes in Ebiz, the ECOService returns an error in the InvokeECOService activity, but

activity doesn’t show as errored. Open the activity to see the error.

Troubleshooting



5. Following these steps, doesn’t necessarily show you anymore details about the error. But

these steps will help you gather the information necessary for an SR and will help your SR

move faster. These are the following details that should be included:

• PIP Patches that have been applied

• Error you are receiving and the BPEL Flow that gives it (i.e. saying you got ERRORED

in the Queue App is not helpful).

• Include the payload that is in the Receive operation of the erroring ABCS. For ECOs

also include the payload for the Receive operation on the CreateQueueService. Or

also include the Raw XML.

Troubleshooting


• Generic Process for Gathering Information for Install and Configuration Issues.

• It’s hard to define an exact structure for what to look for since the issues vary

across customers. Each one will be different and most environmental (i.e. not

able to reproduce in every environment).

1. Know all the versions of the applications in use: Database, Agile, Ebiz, SOA, FP/PIP.

2. Know what patches have been applied.

3. Attach Agile, Ebiz, FMW logs when relevant. (e.g. Agile giving an error when connecting to

FMW, send Agile logs, an error in an activity of a BPEL flow, send FMW logs, etc…)

Troubleshooting


Oracle Applications Integration Architecture Agile PLM ... · Objects (EBOs) that are NOT in scope...

Documents

Transcript of Oracle Applications Integration Architecture Agile PLM ... · Objects (EBOs) that are NOT in scope...