Application Adapter Troubleshooting 101 – 11.1.1.4 (PS3) or Higher

Overview

Although the SOA Suite 11g Application Adapters are capable of integrating with PeopleSoft, SAP R/3, Siebel, and J.D. Edwards OneWorld, there is only one installer which supports all the applications. However, the installer does not contain all the necessary “application specific” binaries that are necessary for the adapter to connect and interact with the various applications. These binaries are packaged and provided by the application vendor (e.g., SAP R/3) and therefore introduces some manual steps to complete the application adapter installation and configuration. It is the manual steps where a misconfiguration is most commonly found. The following are the high-level steps for doing an application adapter installation (details are located in the Oracle Fusion Middleware On-line Library):

  1. Install any required patches.

  2. Install the Oracle® Fusion Middleware Application Adapters in an existing SOA 11g installation.

  3. Manually copy the Enterprise Information System (EIS) binaries to the appropriate locations for both the Adapter Application Explorer and the deployable adapter.

  4. Create a JCA configuration using the Adapter Application Explorer.

  5. Setup the database repository for the new JCA configuration (best practice and only supported configuration for production).

  6. Update the deployable adapter to reflect the JCA configuration and database repository.

  7. Deploy the adapter and the adapter test web application to WebLogic Server.

As you can see, steps 3 through 6 are prone to human error and are many times why the Adapter Application Explorer and/or the deployed adapter do not function correctly. If something is not working as expected, you will need to verify the following before digging deeper:

  1. Are the correct binaries for the EIS copied in the correct locations for the Adapter Application Explorer ([Adapter Home]/lib) and for the deployable adapter ([Adapter Home]/iwafjca.rar and [Domain Home]/lib)?

  2. Is the Adapter Application Explorer configured for the database repository?

  3. Does the deployable adapter contain the correct information in the ra.xml file corresponding to the Adapter Application Explorer configuration?

When these three steps have been done and you know everything is configured correctly, then you can be confident that there are other more complicated issues at hand. This process of validating the installation can be done manually or you can use a utility I pulled together that will programmatically do the validation for you:

NAME

adapterutilPS3.jar

SYNOPSIS

java -jar adapterutilPS3.jar [-h] -s SOA_HOME -d DOMAIN_HOME -c command

[-n configuration name] [-t EIS type]

DESCRIPTION

There adapter configuration utility I put together is very straightforward: you provide some information about your installation (e.g., Adapters Home, Domain Home, Adapter Configuration name, EIS type) and it will use that information to check files, locations, configuration settings, etc. Any discrepancies it finds will be displayed in the command/terminal window.

There are three mandatory parameters which are the ADAPTERS_HOME, DOMAIN_HOME, and command. One could argue that the ADAPTERS_HOME and DOMAIN_HOME are only necessary for one of the three supported commands and this modification may show up in a future release ;)

The utility is driven by an embedded properties file that is packaged in the adapterutilPS3.jar (adapterutil.properties which also contains comments on how it is structured).  It is possible to create your own properties file and override the embedded one by specifying a -Dproperties.filename=[custom properties file] on the command-line.  This is useful when new versions of EIS are certified and not yet represented in the embedded properties.

The following detail the command-line options:

-h

--help, Provides the usage for the utility. (optional)

-a

--adaptershome, This is the fully qualified path to the adapters installation location

-d

--domainhome, This is the fully qualified path to the WebLogic Server domain that the adapter will be deployed to.

-c

--command, One of three commands that are supported by the utility:


configs

This command will provide a list of known EIS configurations and correspond to the officially supported versions of EISs for 11.1.1.4 (PS3) or higher. One of the configurations listed from this command will be used as the value for the -t option.


list

This command will display the files associated with the know EIS configurations or a single EIS configuration if the -t option is specified.


validate

This command will validate a single EIS configuration (i.e., -t option is required for this command) and display details about the configuration with any discrepancies that may be found. Discrepancies will include missing files (there will be a “?” placed next to the missing file) and mismatches between the ra.xml and jcatransport.properties.

-n

--configuration, This is the adapter configuration name which was provided when the configuration was created using the Application Explorer.

-t

--type, This is one of the known EIS configurations from the list produced using the configs command.

EXAMPLES

C:\Users\Oracle\bin>java -jar adapterutilPS3.jar -a C:\Oracle\soa\PS3\Oracle_SOA1\soa\thirdparty\ApplicationAdapters -d C:\Oracle\soa\PS3\user_projects\domains\SOADevDomain -c configs

Known Configurations:
sap2
sap3
Siebel-6.3.x
Siebel-7.0.3
Siebel-7.5.2
Siebel-7.7-8.0
jde_XE
jde_ERP-8.0
jde_EnterpriseOne-8.9
jde_EnterpriseOne-8.10
jde_EnterpriseOne-8.11
jde_EnterpriseOne-8.12
jde_EnterpriseOne-9.0
PeopleSoft-8.1x
PeopleSoft-8.4x
PeopleSoft-8.5x


C:\Users\Oracle\bin>java -jar adapterutilPS3.jar -s C:\Oracle\soa\PS3\Oracle_SOA1\soa\thirdparty\ApplicationAdapters -d C:\Oracle\soa\PS3\user_projects\domains\SOADevDomain -t sap3 -c list

Known configurations and associated files

Configuration Type: sap3

Application Explorer:
  C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/iwmysap30.jar
  C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/sapjco3.jar
  C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/sapjco3.dll
Adapter:
  C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/iwafjca.rar/iwmysap30.jar
  C:/Oracle/soa/PS3/user_projects/domains/SOADevDomain/lib/sapjco3.jar
  C:/Oracle/soa/PS3/user_projects/domains/SOADevDomain/lib/sapjco3.dll


C:\Users\Oracle\bin>java -jar adapterutilPS3.jar -s C:\Oracle\soa\PS3\Oracle_SOA1\soa\thirdparty\ApplicationAdapters -d C:\Oracle\soa\PS3\user_projects\domains\SOADevDomain -n JCA_SampleConfig -t sap3 -c validate

Validating sap3 ...
   C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/iwmysap30.jar
   C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/sapjco3.jar
   C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib/sapjco3.dll
   C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/iwafjca.rar/iwmysap30.jar
 ? C:/Oracle/soa/PS3/user_projects/domains/SOADevDomain/lib/sapjco3.jar
 ? C:/Oracle/soa/PS3/user_projects/domains/SOADevDomain/lib/sapjco3.dll

*** Configuration files need review


ra.xml ...
IWayHome:         C:/Oracle/soa/PS3/Oracle_SOA1/soa/thirdparty/ApplicationAdapters
IWayConfig:       JCA_SampleConfig
IWayRepoDriver:
IWayRepoURL:      jdbc:oracle:thin:@localhost:1521:orcl
IWayRepoUser:     ps3_adapters
IWayRepoPassword: welcome1
LogLevel:         DEBUG


Application Explorer Configuration ...
Is File Repository:      false
Is DB Repository:        true
Contains repository.xml: false
iwafjca.repo.url:        jdbc:oracle:thin:@localhost:1521:xe
iwafjca.repo.user:       ps3_adapters
iwafjca.repo.password:   welcome1


Application Explorer Configuration compared to ra.xml ...

ra.xml:
*** IWayRepoURL mismatch
    Current:   jdbc:oracle:thin:@localhost:1521:orcl
    Should be: jdbc:oracle:thin:@localhost:1521:xe

Application Explorer Configuration:
No issues found.

Comments:

Great post, thanks !

This utility jar is very helpful.

Posted by guest on March 26, 2012 at 12:34 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About


This is the blog for the Oracle FMW Architects team fondly known as the A-Team. The A-Team is the central, technical, outbound team as part of the FMW Development organization working with Oracle's largest and most important customers. We support Oracle Sales, Consulting and Support when deep technical and architectural help is needed from Oracle Development.
Primarily this blog is tailored for SOA issues (BPEL, OSB, BPM, Adapters, CEP, B2B, JCAP)that are encountered by our team. Expect real solutions to customer problems, encountered during customer engagements.
We will highlight best practices, workarounds, architectural discussions, and discuss topics that are relevant in the SOA technical space today.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today