|
Oracle® Application Server Integration InterConnect User's Guide
10g Release 2 (10.1.2) B14069-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Integration InterConnect User's Guide
10g Release 2 (10.1.2) B14069-02 |
|
|
Previous |
Next |
This appendix describes common problems that you might encounter when using OracleAS Integration InterConnect and explains how to solve them. It also gives detailed instructions on how to diagnose OracleAS Integration InterConnect problems. It contains the following topics:
This section describes common problems and solutions. It contains the following topics:
DB Adapter Does Not Pick Up Messages That Have Been Published from the Database
FTP Adapter Cannot Match Incoming Message with Any D3L Definiton
iStudio is not connecting to the repository. For example, a message pops up saying "Failed to connect to the repository".
Problem 1
Incorrect hub database parameters entered in the Hub Information dialog box.
Solution 1
iStudio uses the user name, password, and connect string entered in the 'Hub Information' dialog box to establish a connection with the respository. Ensure that you have provided the correct hub database parameters, hostname:tns_listener_port:db_sid, for connecting to the Infrastructure Database. For example, myhost.us.mycompany.com:1521:orcl.
|
See Also: Section 2.5.1, "Creating a New Project" for more details on the hub database parameters |
Problem 2
Repository is down.
Solution 2
Ensure that the repository is properly started and check the $ORACLE_HOME/intergration/interconnect/repository/reposlog.txt file for any problems.
Problem 3
Repository is running behind a firewall.
Solution 3
Ensure that you configure the repository to use a specific RMI communication port. Specify a port number in the repo_admin_port parameter of the repository.ini file located at $ORACLE_HOME/integration/interconnect/repository. You also need to open the seven ports on the firewall starting from the port number specified in repo_admin_port parameter of the repository.ini file.
I have changed the mapping, but the adapter(s) still seem to use the old information.
Problem 1
Metadata is not refreshed.
Solution 1
In the File menu, select Sync Adapters. This pushes the updated metadata to the adapters.
Solution 2
Alternatively, you could perform the following steps to change the behavior after transformation:
Stop the adapters.
In the adapter.ini file, set the value of the parameter agent_delete_file_cache_at_startup to True, to delete all cached metadata at startup.
This parameter specifies whether to delete the cached metadata during startup. If any of the agent caching methods such as metadata caching, DVM table caching, or lookup table caching is enabled, then metadata from the repository is cached locally on the file system. However, if you change some metadata or DVM table using iStudio and you want the Adapter to use those changes the next time it is started, then you can either delete the cache files or set this parameter to true before restarting.
Restart the adapters.
The metadata is not editable in iStudio as the "Edit" option is greyed out.
Problem 1
The metadata in the repository might belong to a different metadata owner than the one specified in the $ORACLE_HOME/integration/interconnect/repository/repository.ini file.
Solution 1
Ensure that the "owner" of the data is same in both repositories. Data types have an owner, usually, that is "OAI". But you can change it in the repository.ini file. Only data that is owned by the local repository owner may be edited.
The metadata owner information is stored along with the objects at the time of their creation. If the repository owner name does not match the creation time owner name, then you will notice that the edit buttons are greyed out. You will need to edit the repository.ini file to change the owner name to the one used during creation and restart the repository. You will also need to reestablish the iStudio connection to the repository.
The subscribing adapter is not able to pickup any message from the hub queue (oai_hub_queue). The messages are queued up in the hub queue but aren't subscribed by the subscribing adapter.
Problem 1
The value for the application, agent_subscriber_name, and agent_message_selector parameter in the $ORACLE_HOME/integration/interconnect/adapters/adapter_name/adapter.ini file doesn't match the application name in iStudio.
Solution 1
Ensure that the value for the application, agent_subscriber_name, and agent_message_selector parameter in the $ORACLE_HOME/integration/interconnect/adapters/adapter_name/adapter.ini file match the application name in iStudio.
Problem 2
Subscriber name or application name may be longer than 20 characters.
Solution 2
Apply patch 2659228.
If an adapter successfully received a message from the hub, but encounters a problem while transforming the message or delivering the message to the spoke application, then it will try to reprocess/resend the message in a certain interval until the problem has been resolved and the message has been successfully delivered. In most cases, this unfortunately means that all other pending messages that need to be processed to the spoke application won't get delivered until this one message has cleared out of the system.
Problem
OracleAS Integration InterConnect guarantees in-order-delivery of messages, meaning that if an adapter encounters a problem while processing a message, it will try to re-send the message until the problem has been resolved and the message can be delivered successfully. All other pending messages can't get delivered as this would change the order of delivery.
Solution 1
Refer to the error message and the oailog.txt file in $ORACLE_HOME/integration/interconnect/adapters/adapter_name/logs/ directory, to resolve the error message.
Solution 2
Use the $ORACLE_HOME/integration/interconnect/adapters/adapter_name/ignoreErrors script to drop the problem message out of the system. The ignoreErrors script will reconfigure the adapter, so that it ignores a specific error code. The adapter will then drop all messages that fail with that specific error code rather than trying to resend them, which ensures that other pending messages can be processed.
|
Note: When you useignoremessage script, the messages are permanently deleted from the system. These messages cannot be recovered.
|
The OracleAS Integration InterConnect repository does not start properly and there are java excpetions in the $ORACLE_HOME/integration/interconnect/repository/reposlog.txt file. For example, "Could not register with the hub database. Please check your hub database parameters." Error message: "Retrying in 10 sec.java.sql.SQLException: Io exception: The Network Adapter could not establish the connection".
Problem 1
The information in the $ORACLE_HOME/integration/interconnect/hub/hub.ini file is not valid.
Solution 1
Provide the correct information in the $ORACLE_HOME/integration/interconnect/hub/hub.ini file.
[Database]
hub_username=ichub
encrypted_hub_password= encrypted_password use $ORACLE_HOME/integration/interconnect/bin/encrypt for encryption
hub_host=hub_host_name
hub_instance=database_sid
hub_port=tns_listsner_port
hub_use_thin_jdbc=true
[Repository Info]
repository_name=InterConnectRepository1012
Problem 2
The hub schema does not exist on the hub database.
Solution 2
Run the $ORACLE_HOME/integration/interconnect/repository/hubschema script to create the hub schema.
The database adapter does not pick up messages that have been published from the database, even though the publshing PL/SQL procedure was performed successfully and the message object record exists in the MESSAGEOBJECT table.
Problem
You might have published the message for the wrong application. The value provided for srcAppName+partition id parameter in the publishing PL/SQL procedure pub_eventorprocedure_name_metadata_owner_version does not match the application parameter value in the $ORACLE_HOME/integration/interconnect/adapters/adapter_name/adapter.ini file.
Solution
Ensure that the value provided for the srcAppName+partition id parameter matches the value of the application parameter in the $ORACLE_HOME/integration/interconnect/adapters/adapter_name/adapter.ini file.
The database adapter is not publishing the messages.
Problem 1
The application name specified in the trigger that publishes the message to the OAI scheme does not match with the application name specified in the application parameter of the adapter.ini file.
Solution 1
Ensure that the application name specified in the trigger that publishes the message to the OAI schema and the application name specified in the application parameter of the adapter.ini file are same. If the partition parameter in the adapter.ini file contains a value, then, in the trigger, the application name should be specified as the value of the application parameter followed by the value of the partition parameter. In addition, ensure that the parent-child relationships are properly handled according to the structure created in iStudio.
Problem 2
The value of the db_bridge_schema1_num_readers parameter specified in the adapter.ini file is incorrect.
Solution 2
The value of the db_bridge_schema1_num_readers parameter in the adapter.ini file should be greater than zero.
The FTP adapter throws an error message that it cannot match the incoming message with any of the D3L defintions, and drops the message.
Problem 1
The ota.d3ls parameter is either empty or points to the wrong D3L file(s).
Solution 1
Provide a valid D3L file for ota.d3ls (or list of D3L files).
Problem 2
The D3L header does not contain the correct information for OracleAS Integration InterConnect event mapping.
Solution 2
Ensure that the
name tag in the D3L header matched the BusinessObject event name in iStudio.
Object Name field in the Define application View window of the Publish/ Subscribe/Invoke/Implement wizard is not empty.
object tag matches the value of the Object Name field in the Define application View window of the Publish/Subscribe/Invoke/Implement wizard.
The AQ adapter does not pick up message that have been enqueued to a spoke AQ.
Problem 1
You have not provided the name of the spoke queue in the Deploy Tab in iStudio for this integration point.
Solution 1
Provide the name of the spoke queue. The AQ adapter log file should contain a line timestamp: AQ Adapter created a reader for queue queue_name.
Problem 2
The spoke queue might be a multiconsumer queue (JMS Topic) and you might connect to it with an incorrect consumer name.
Solution 2
Ensure that the aq_bridge_consumer_name parameter in the $ORACLE_HOME/integration/interconnect/adapters/adapter_name/adapter.ini file is correct and matches the name of the consumer that the message was enqueued for.
Problem 3
The message structure defined in iStudio does not match the message you are trying to publish.
Solution 3
Ensure that the message structure defined in iStudio matches the message you are trying to publish.
The FTP adapter is not publishing or subscribing to the messages.
Problem 1
The Transport properties of the FTP adapter might not be correct.
Solution 1
Specify 2 as the value of the log level parameter agent_log_level in the adapter.ini file of the FTP adapter. Restart the adapter and try to publish a message or subscribe to a message. You can see a log starting with TransportProperties.TransportProperties(). This log contains all the transport properties for the FTP adapter in the form of name value pairs. Ensure that the values of these properties are correct.
Problem 2
You might not have created a publish or subscribe event in iStudio for the FTP adapter that corresponds to the message structure. The FTP adapter is not able to match the message data to any of the events defined during design time and therefore cannot publish or subscribe the message.
Solution 2
Create a publish or subscribe event for the FTP adapter in iStudio corresponding to the message structure.
Problem 3
The FTP server is not based on RFC standards.
Solution 3
Ensure that the FTP server is based on RFC standards.
The HTTP adapter is not publishing or subscribing to the messages.
Problem 1
The Transport properties of the HTTP adapter might not be correct.
Solution 1
Specify 2 as the value of the log level parameter agent_log_level in the adapter.ini file of the HTTP adapter. Restart the adapter and try to publish a message or subscribe to a message. You can see a log starting with TransportProperties.TransportProperties(). This log contains all the transport properties of the HTTP adapter in the form of name value pairs. Ensure that the values of these properties are correct.
Problem 2
You might not have created a publish or subscribe event in iStudio for the HTTP adapter that corresponds to the message structure. The HTTP adapter is not able to match the message data to any of the events defined during design time and therefore cannot publish or subscribe the message.
Solution 2
Create a publish or subscribe event for the HTTP adapter in iStudio corresponding to the message structure.
Problem 3
The transport servlet is not deployed properly.
Solution 3
Ensure that the transport servlet that receives the messages over HTTP and directs these messages to the HTTP receiver through RMI is deployed properly. In addition, you should never change the http.receiver.instance_name parameter in the adapter.ini file after the adapter installation.
Problem 4
The send endpoint defined by the ota.send.endpoint parameter in the adapter.ini file or in iStudio is incorrect.
Solution 4
Ensure that the send endpoint defined in the adapter.ini file or iStudio is correct. If the send endpoint expects the message in some particular form, then you can customize the outgoing messages using the SenderCustomizer parameter.
I created an event with the name ProdRelease. The root element name is BatchProdRelease. When I restart the adapter, it displays the following error:
"An exception occured while evaluating the CBR expression: (ProdRelease_CO:OAI_META/V1.BatchProdRelease_CO:OAI_META/V1.Header.PlantCode == "GFL"). Following is a detailed message. oracle.oai.agent.common.AgentRuntimeException: Specified attribute (BatchProdRelease_CO:OAI_META/V1) does not exist in Data Type (ProdRelease_CO:OAI_META/V1)."
Problem
The root element name is a substring of the event name.
Solution
Ensure that the root element name does not have a substring of the event name. The root element name in this situation is BatchProdRelease and the event name is ProdRelease. This causes the adapter to fail. A workaround for this is to change either the root element name or event name.
How can I configure Oracle Workflow with OracleAS Integration InterConnect?
Solution
To configure Oracle Workflow with OracleAS Integration InterConnect, perform the following steps:
Navigate to your Oracle Workflow home page.
Click Global Workflow Preferences. The Global Workflow Preferences page is displayed.
Ensure that System Status is set to Enabled.
Open the http://host-name/pls/DAD location/wf_setup.check_all URL where host-name is the name of your computer. For example,
http://workflowinstall-pc/pls/wf/wf_setup.check_all
The Check Setup page is displayed.
Schedule listeners for the WF_ERROR and WF_IN agents in the Listeners for Local Inbound Agents group. To schedule a listener for the WF_ERROR agent:
In the Listeners for Local Inbound Agents group, click Create for the WF_ERROR agent. The Edit Listener page is displayed.
In the Edit Listener page, enter 10 in the Seconds field.
Click Submit.
A listener for the WF_ERROR agent has been scheduled. Similarly, schedule a listener for the WF_IN agent.
|
Note: It is recommended that you set the listener to run every 10 seconds. To obtain faster response times, schedule additional listeners rather than lowering the interval between runs. For information about scheduling listeners, refer to Oracle Workflow Administrator's Guide. |
In the Check Setup page, under the Database Init.ora Parameters group, ensure that the value of aq_tm_processes is greater than or equal to 1. Similarly, ensure that the value of job_queue_processes is greater than or equal to 5.
In the Event Subscriptions group, create subscriptions for the following events:
oracle.apps.wf.event.agent.create
oracle.apps.wf.event.event.create
oracle.apps.wf.event.subscription.create
To add subscriptions for an event, click Add Subscription at the bottom of the Check Setup page. The Edit Subscription page is displayed.
To create a subscription for the oracle.apps.wf.event.agent.create event, specify the following values:
Select your Oracle Workflow system from the System list. You can search by % to locate registered systems.
Select External from the Source Type list.
Enter the event for which you are creating the subscription in the Event Filter field. For example, if you are creating a subscription for the oracle.apps.wf.event.agent.create event, enter oracle.apps.wf.event.agent.create.
Select Enabled from the Status list.
Select Key from the Rule Data list.
Enter wf_event_functions_pkg.receive in the Rule Function field.
A subscription for the oracle.apps.wf.event.agent.create event has been created. Similarly, create subscriptions for the oracle.apps.wf.event.event.create and the oracle.apps.wf.event.subscription.create events. The subscriptions that you create are displayed in the Check Setup page. The configuration of Oracle Workflow with OracleAS Integration InterConnect is complete.
You can find more solutions on Oracle MetaLink, http://metalink.oracle.com. If you do not find a solution for your problem, log a service request.
|
See Also:
|
