| Oracle® Application Integration Architecture Agile Product Lifecycle Management for SAP: Design to Release Install Guide Release 3.5 E73101-01 |
|
 Previous |
 Next |
| Oracle® Application Integration Architecture Agile Product Lifecycle Management for SAP: Design to Release Install Guide Release 3.5 E73101-01 |
|
Previous |
Next |
This chapter describes how to configure prerequisites and download the Agile Product Lifecycle Management for SAP: Design to Release pre-built integration installer.
Before installing the pre-built integration, you must make sure the SOA Core Extension (SCE) is configured properly.
To configure the SCE:
Update the AIAInstallProperties.xml file, located in <DOMAIN_LOCATION/soa/aia/bin as described in the following table:
Table 2-1 AIAInstallProperties.xml file
| Field | Value |
|---|---|
|
sharedlocation |
Used in clustering environment. No need to update CLUSTER_SHARED_LOCATION to your shared folder location. Installer will complete field. |
|
isencrypted |
Keep "false" value here. After post-install configuration, it will be updated to true. |
|
version |
SOA version |
|
adminhostname |
Hostname of Admin Server |
|
adminport |
Port of Admin Server |
|
domainname |
Domain Name of the SOA domain |
|
username |
User Name to log in to WebLogic Console and Enterprise Manager |
|
password |
Password for the user name. Keep "ADMIN_PASSWORD" value here. Post-install configuration script will ask for the password and write the encrypted password here. |
|
servertype |
In a clustered environment, enter Cluster. Otherwise enter Server. |
|
soaserver |
In a clustered environment, enter Cluster Name. Otherwise, enter the Managed Server name. |
|
soaserverhostname |
In a clustered environment, enter HTTP Proxy Host Name. Otherwise, enter the Managed Server Host name. |
|
soaserverport |
In a clustered environment, enter HTTP Proxy Port. Otherwise, enter the Managed Server port. |
|
jndiurl |
The URL should be in the format: t3://<managed server hostname>:<managed server port>. In a clustered environment, add all managed servers delimited with ","; for example, t3://<managed server1 hostname>:<managed server1 port>,<managed server2 hostname>:<managed server2 port> |
Update the AIAInstallProperties.xml file, located in <DOMAIN_LOCATION/soa/aia/bin as described in the following table:
Table 2-2 AIAInstallProperties.xml file
| Field | Value |
|---|---|
|
sharedlocation |
Used in clustering environment. No need to update CLUSTER_SHARED_LOCATION to your shared folder location. Installer will complete field. |
|
isencrypted |
Keep "false" value here. After post-install configuration, it will be updated to true. |
|
version |
SOA version |
|
adminhostname |
Hostname of Admin Server |
|
adminport |
Port of Admin Server |
|
domainname |
Domain Name of the SOA domain |
|
username |
User Name to log in to WebLogic Console and Enterprise Manager |
|
password |
Password for the user name. Keep "ADMIN_PASSWORD" value here. Post-install configuration script will ask for the password and write the encrypted password here. |
|
servertype |
In a clustered environment, enter Cluster. Otherwise enter Server. |
|
soaserver |
In a clustered environment, enter Cluster Name. Otherwise, enter Managed Server name. |
|
soaserverhostname |
In a clustered environment, enter HTTP Proxy Host Name. Otherwise, enter Managed Server Host name. |
|
soaserverport |
In a clustered environment, enter HTTP Proxy Port. Otherwise, enter Managed Server port. |
|
jndiurl |
The URL should be in the format: t3://<managed server hostname>:<managed server port>. In a clustered environment, add all managed servers delimited with ","; for example, t3://<managed server 1 hostname>:<managed server1 port>,<manabed server2 hostname>:<managed server2 port> |
Example 2-1 An example of a clustered environment
<?xml version="1.0" encoding="UTF-8"?>
<properties>
<aiaDomain>
<sharedlocation>CLUSTER_SHARED_LOCATION</sharedlocation>
<isencrypted>false</isencrypted>
</aiaDomain>
<fp>
<version>12.1.3.0.0</version>
<server>
<adminhostname>slc07rmp.us.oracle.com</adminhostname>
<adminport>7037</adminport>
<domainname>soa_domain</domainname>
<username>weblogic</username>
<password>ADMIN_PASSWORD</password> <!--Do not edit this property.-->
<servertype>Cluster</servertype>
<soaserver>soa_cluster</soaserver>
<soaserverhostname>slc07rmp.us.oracle.com</soaserverhostname>
<soaserverport>7777</soaserverport>
<jndiurl>t3://slc07rmp.us.oracle.com:8037,slc07rmq.us.oracle.com:8037</jndiurl>
</server>
</fp>
</properties>
|
Note: Shared Location is a remote network position/container that can be set for NFS, Drive Mapping or another technology. Shared Location is needed for PIP 3.4 and PIP 3.5 clustering and should be configured before installation to assure successful installation and deployment. In each SOA machine, the path to the shared location must be the same, and also must be Readable and Writeable. |
Run the following commands:
On Linux:
source <DOMAIN_LOCATION>/soa/aia/bin/aiaenv.sh
ant -f $SOA_HOME/aiafp/Install/config/FPPostInstall.xml
On Windows:
<DOMAIN_LOCATION>\soa\aia\bin\aiaenv.bat
ant -f %SOA_HOME%\aiafp\Install\config\FPPostInstall.xml
To install the Agile Product Lifecycle Management for SAP: Design to Release pre-built integration:
Navigate to the Oracle Software Delivery Cloud. [https://edelivery.oracle.com]
Select the Product Pack: Oracle Application Integration Architecture
Select your platform.
Click Go.
Click the Oracle Agile PLM for SAP: Design to Release Pre-built Integrations Release 3.5 Media Pack link for your platform.
Download the Oracle Agile PLM for SAP: Design to Release Pre-built Integrations Release 3.5 file.
Unzip the downloaded file.
Navigate to the Agile2SAPPIP3.5 directory.
Run the following installation file for your platform:
Linux: setup_lin.bin
Windows: setup_win.exe
The Agile PLM PIP Installer launches the Welcome screen.
Click Next.
Enter the Name and Path where the SOA Core Extension (SCE) is installed.
|
Note: If the AIA Home Path is not correct, the installation will not proceed. |
Click Next.
Complete the remaining screens as described in the following sections:
If the information displayed on the Pre-Installation Summary page is correct, click Install.
The following sections describe the fields on the Agile PLM PIP installer screens.
Use this screen to enter details about your SOA Admin Server. This screen contains the fields listed in Table 2-3.
Table 2-3 SOA Admin Server Details Screen Fields
| Field | Description |
|---|---|
|
Admin Hostname |
The value is the name/domain of the WebLogic admin server. To find this value contact your WebLogic administrator. The Admin Hostname is _________________________________. |
|
Admin Port |
This value is the port number of the WebLogic admin server. To find this value contact your WebLogic administrator. The Admin Port is ___________________________________. |
|
Admin User |
This value is the WebLogic admin user name. To find this value contact your WebLogic administrator. The Admin User is __________________________________ |
|
Admin Password |
This value is the WebLogic admin password. To find this value contact your WebLogic administrator. The password is _____________________________________ |
Use this screen to enter information about your managed or cluster SOA server.This screen contains the fields listed in Table 2-4.
Table 2-4 SOA Server Details Screen Fields (Standalone)
| Field | Description |
|---|---|
|
SOA Domain Name |
This is WebLogic server domain corresponding to the Admin Server. Example: The SOA Domain Name is _______________________________ |
|
SOA Installation Directory |
This value is the path where the SOA Domain is located. |
|
Managed Server Name |
This value is the name of the Managed Server for the domain. |
|
Managed Server Port |
This value is the port number of the managed server. |
Use this screen to enter details related to your SAP application server instance. The screen contains the fields listed in Table 2-5.
Table 2-5 SAP Application Server Details Screen fields
| Field | Description |
|---|---|
|
SAP Application Server Name |
Specifies the fully qualified system name of the SAP Application Server. The SAP application server name is _________________________ For example: example1.corp.oracle.com |
|
System Number |
This value specifies the system number of the SAP client. The System Number is _____________________________.. |
|
System ID |
This value specifies the system ID of the SAP server. The System ID is ______________________. |
|
Client ID |
This is the SAP client number, which is used for integration. The Client ID is _________________________. |
|
User Name |
Specifies the authorized name used to log on to the SAP system. The User Name is................................................. |
|
Password |
Authorized password to log on to the SAP system. |
|
Language |
Language page installed on the SAP server. |
|
Code Page |
Code page is used for double byte characters. If your file content has non-English characters, then you must specify the Code page. |
|
Gateway Service Name |
The SAP Gateway carries out Communication Programming Interface Communication services. These services enable SAP Systems and external programs to communicate with one another. The SAP Gateway Service name is ______________________________. |
|
Connection Pool Size |
The maximum number of connections which are maintained in the SAP system. The connection Pool size is ____________________. |
|
Gateway host |
Specifies the name of the host where the SAP gateway service identified in the sap-gateway-service. The gateway host is __________________________________________. |
|
Program ID |
This value is the Program ID of the SAP Server. The Program ID is ________________________________________. |
|
Sender Port |
Specifies the name of the port used to send the data from other systems through IDOCs. The Sender Port is __________________________________________. |
|
Receiver Port |
Specifies the name of the port used to receive the data from other systems through IDOCs. The Receiver Port is __________________________________________. |
|
Message Server Name |
This is the SAP message server name, if used. |
Use this screen to enter details related to your Agile PLM instance. The screen contains the fields listed in Table 2-6.
Table 2-6 Agile PLM Server Connect Details Screen fields
| Field | Description |
|---|---|
|
Agile PLM Hostname |
Specifies the system name. Example: Agile PLM Host is ________________________________ |
|
Agile PLM Port |
This is the http or https port if you are using Agile PLM 9.3.5 with Web Service Security enabled. This value depends on the web server port and operating system of your Agile PLM instance. To find this value, contact your Agile PLM administrator. Example: Agile PLM Port is ________________________________ |
|
Agile PLM Virtual Path |
This value is the same virtual path entered during the Agile PLM installation. Example: Agile PLM Virtual Path is _________________________ |
|
Agile PLM Integration User Name |
This is the Agile PLM admin access user name. Example: Agile PLM Integration Username is ________________ |
|
Agile PLM Integration User Password |
To find this value, contact your Agile PLM administrator. Agile PLM Integration User Password is ____________ |
Use this screen to enter details related to your Agile PLM server. The screen contains the fields listed in Table 2-7.
Use this screen to enter details related to your Pre-built Integration database instance.The screen contains the fields listed in Table 2-8.
Table 2-8 PIP Database Connect Details Screen fields
| Field | Description |
|---|---|
|
PIP Schema Database Hostname |
Specifies the system name. To find this value, contact the database administrator. Example: PIP Schema Database Host is ___________________ |
|
PIP Schema Database Port |
To find this value, contact the database administrator. Example: PIP Schema Database Port is ___________________ |
|
PIP Schema Database SID (System ID) |
To find this value, contact the database administrator. Example: PIP Schema Database SID is _________________________ |
|
Sys User Name |
Enter the name of the SYS database user. Default value is sys. |
|
Sys User Password |
Enter the password for the SYS database user. To find this value, contact the database administrator. |
Use this screen to enter details related to your new schema to be created for the pre-built integration queue tables. The screen contains the fields listed in Table 2-9
Use this screen to enter details related to the SAP to Agile PLM Initial Load instance. The screen contains the fields listed in Table 2-10.
Table 2-10 PIP Item Initial Load Data Locations
| Field | Description |
|---|---|
|
Location to store XML files with item data from SAP |
This is the location where AIA stores the XML files that contain Initial Load Item data from SAP. |
|
Location to read Item XML files to load into Agile PLM |
This is the location from where AIA picks up the Initial Load Item data XML files for loading into Agile PLM. This location option enables you to review and improve the data before loading into Agile. |
|
Location to store the failed Item data XML files |
This is the location of the Item Data XML files that failed to load into Agile. |
|
Location to store the successful Item data XML files |
This is the location of the Item Data XML files that were successfully loaded into Agile. |
The following tasks must be performed to install the SAP Adapter:
Install Java Development Kit (JDK) version 1.7_45 or later. Oracle Application Adapter for SAP R/3 is certified with JDK version 1.7_45.
JDK is installed with the WebLogic server installation. Go to Middleware_Home\jdk1.7_45\jre.
Ensure that the JDK is added to your system PATH or another predefined path.
Navigate to the Oracle Software Delivery Cloud [https://edelivery.oracle.com] and sign in with valid login credentials.
Select the Product Pack: Oracle Fusion Middleware for your specific platform to download the application adapters.
At the command prompt, run the command for your platform:
Table 2-11 SAP Adapter Launch Commands
| Platform | To launch the SAP Adapter Installer |
|---|---|
|
Linux Solaris SPARC HP-UX IBM AIX Based Systems |
-is javahome path of the JDK Installer iwora 11g.application-adapters.linux.bin or iwora11g.application-adapters.solaris.bin |
|
Microsoft Windows |
-is:javahome Path of the JDK Installer iwora 11.application-adapters.win32.exe |
The installation program uses the JDK version that is available in your system PATH or on a predefined path.
Click Next.
The Oracle SOA Integration Home screen is displayed to enter the path where Oracle SOA Suite is installed on your system. for example, C:\oracle_soa.
The installation program creates a subdirectory called Application Adapters under the Oracle SOA home where all the files for Oracle Application Adapter for SAP R/3 are installed.
After the installation is complete, an Install Confirmation screen is displayed. Click Finish.
The Oracle Application Adapter for SAP R/3 is now installed on your system in the following directory:
\Middleware_Home\Oracle_SOA1\soa\thirdparty\ApplicationAdapters
Navigate to \Middleware_Home\Oracle_SOA1\soa\thirdparty\ApplicationAdapters and apply patch 13509998 using the opatch apply command.
The Oracle Application Adapter for SAP R/3 is installed into the Application Adapters subdirectory of your Oracle WebLogic Integration home directory.
Table 2-12 Application Adapters Directory Structure
| Directory Structure | Description |
|---|---|
|
-uninst |
Contains the uninstallation files |
|
config |
Contains the J2CA_SampleConfig subdirectory and XML-file-based repository for OracleWLS Adapter J2CA |
|
etc |
Contains the ibse.ear, iwafjca.ear, iwafjca.rar, and iwse.ora files |
|
ibse.war |
Contains the BSE application and repository configuration |
|
iwafjca.rar |
Contains the J2CA Installation Verification Program (IVP) |
|
lib |
Contains library files |
|
tools |
Contains the Application Explorer graphical user interface |
Oracle Application Adapter for SAP R/3 requires you to copy library files to specific directories.
Copy the library files which are given in Table 2-13 or the adapter into this directory:
Middleware_Home/Oracle_SOA1/soa/thirdparty/ApplicationAdapters/lib.
Copy the library files which are given in Table 2-13 into the lib directory for your domain. For example, Middleware_home/user_projects/domains/domain_name/lib.
Use any archive tool and open the archive containing the SAP JCo, sapjco3.jar, and extract the run time files.
The file names can vary by operating system, but typically are contained in the root of the archive.
|
Note: All operating systems: You must place the sapjco3.jar file in the Middleware_Home\Oracle_SOA1\thirdparty\ApplicationAdapters\lib directory. Then, you must add the sapjco2.jar to the Oracle WebLogic Server classpath. |
On Windows, librfc32.dll should be placed in the %WINDIR%\system32 directory and sapjcorfc.dll should be placed in the same directory as sapjco3.jar:
Middleware_Home\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\lib
On other platforms, use the corresponding location for your platform.
Table 2-13 Library Files According to Operating System
| Adapter Version | Library Files |
|---|---|
|
Linux/Solaris/OS400 |
libsapjcorfc.so librfccm.so |
|
HP-UX |
librfccm.sl libsapjcorfc.sl |
|
AIX |
librfccm.so libsapjcorfc.so |
On UNIX platforms, the directory in which the shared library files are located must be added to the shared library variable applicable to the operating system.
Table 2-14 Associated Variables According to the Platform
| Platform | Variable |
|---|---|
|
AIX |
LIBPATH |
|
HP-UX |
SHLIB_PATH |
|
Other UNIX Platforms |
LD_LIBRARY_PATH |
Solaris: The following statements are the two supported methods for specifying the SAP library files:
Copy the SAP JCO files (sapjco3.jar, librfccm.so, and libsapjcorfc.so) to jdk/jre/lib/sparc/server.
Copy the SAP JCO files to /usr/j2sdk1.4.2_09/jre/lib/sparcv9/server.
Alternatively, you may add the path to these files to your environment variable definition using the Application Server Control Console. For details on application server administration options, see the Oracle Application Server Administrator's Guide.
See the Oracle Fusion Middleware Application Adapter for SAP R/3 User's Guide for Oracle WebLogic Server for any additional steps required for SAP R/3.
The Business Service Engine (BSE) exposes, as web services, enterprise assets that are accessible from the adapter regardless of the programming language or the particular operating system.
In addition, you can use BSE as a standalone Java application running in Oracle WebLogic Integration.
BSE Configuration is required in SAP adapter for SAP Inbound adapter configuration and JCA. Configuration is required for SAP Outbound adapter as well.
The J2CA runs in J2EE Connector Architecture compliant application servers and uses the Common Client Interface (CCI) to provide integration services using Oracle Application Adapter for SAP R/3. After you deploy the connector, you can access the adapter.
The default location for the repository on Windows is:
wls_home\ApplicationAdapters\ibse.war\ibserepo.xml
Execute the iwse.ora SQL script on the computer where the SOA database is installed. The iwse.ora SQL script is located in the following directory:
wls_home\ApplicationAdapters\etc.
Run the SQL script by connecting to database with user name and password
SQL > @ iwse.ora
Create the jcatransport.properties file and save it in the following directory: wls_home\ ApplicationAdapters \config\J2CA_SampleConfig
Enter values for iwafjca.repo.url, iwafjca.repo.user and iwafjca.repo.password fields in the newly created jcatransport.properties file, as shown in the following example:
iwafjca.repo.url=jdbc:oracle:thin:@DB IP address:port:orcl
iwafjca.repo.user=user name
iwafjca.repo.password=password
Navigate to the following directory: WLS_HOME\erp-adapters\iwafjca.rar\META-INF
Open the ra.xml file in a text editor.
Provide the JDBC connection information as a value for the IWAYRepo_URL property.
Provide a valid user name for the IWAYRepo_User property.
Provide a valid password for the IWAYRepo_Password property.
Save your changes to the ra.xml file.
Run the iwse.ora SQL script on the computer where the database is installed.
|
Note: The jcstransport.properties file is required. |
Run the iwse.ora SQL script on the computer where the database is installed.
The iwse.ora SQL script is located in the following directory:
wls_home\ ApplicationAdapters\etc
SQL>@ iwse.ora
Display the BSE configuration page in a browser:
http://host name: port/ibse/IBSEConfig where host name is the system where BSE is installed and port is the port number on which BSE is listening.
Configure the system settings. The following table lists the parameters with descriptions of the information to provide.
Table 2-15 Parameters to Configure the System Settings
| Parameter | Description |
|---|---|
|
Language |
Specify the required language |
|
Adapter |
Lib |
|
Directory |
Enter the full path to the directory where the adapter.jar files reside. Encoding Only UTF-8 is supported. |
|
Debug Level |
Spcify the debug level from the following options: None Fatal Error Warning Info Debug |
Configure the repository settings. BSE requires a repository to store transactions and meta data required for the delivery of web services.
Table 2-16 Parameters to Configure the Repository Settings
| Parameter | Description |
|---|---|
|
Repository |
Select either Oracle or File (Do not use for BSE in production environments.) |
|
Repository URL |
Enter the JDBC URL to use when opening a connection to the database. For example, the following repository URL format is used when connecting to Oracle: jdbc:oracle:thin@hostname:port:SID |
|
Repository Driver |
Provide the driver class to use when opening a connection to the database (optional). For example, the following repository driver format is used when connecting to Oracle: oracle:jdbc.driver.OracleDriver |
|
Repository User |
Enter a valid password that is associated with the user ID. |
|
Repository Password |
Enter a valid password that is associated with the user ID. |
|
Repository Pooling |
If selected, repository pooling is used. This option is disabled by default. |
Click Save.
Start Application Explorer.
Right-click the Configurations node in the left pane and select New. The New Configuration dialog box opens.
Type a name for the configuration and click OK.
Select JCA from the Service Provider list box and enter an HTTP target value in the Home field.
Use the following format for the HTTP target value:
http://host name:port/iwafjca/JCAServlet
For example: http://iwserv14:7777/iwafjca/JCAServlet
Click OK.
The new HTTP repository connection is added to the Configurations node.
Once you connect to the remote server, you can create new Adapter targets, generate WSDL documents, and store them in the remote server.
Oracle Adapter Application Explorer (Application Explorer), a GUI tool which uses SAP R/3 object repository metadata to build XML schemas and web services to handle adapter requests or event data.
On Windows, run the ae.bat file, which is found under wls_home\ApplicationAdapters\tools\iwae\bin, where wls_home is the directory where Oracle WebLogic Server is installed.
On UNIX, load the iwae.sh script file, which is found under wls_home/ ApplicationAdapters /tools/iwae/bin, where wls_home is the directory where Oracle WebLogic Server is installed.
To create a configuration for Oracle Adapter J2EE Connector Architecture (J2CA) using Application Explorer, you must first define a new configuration.
This is a prerequisite for deploying J2CA as a web application in Oracle WebLogic Integration.
To define a new configuration for J2CA:
Start Application Explorer.
Right-click Configurations and select New. The New Configuration dialog box is displayed.
Enter a name for the new configuration, for example, J2CA_SampleConfig, and click OK. The name of the J2CA configuration that is specified here is used during the J2CA deployment process.
From the Service Provider list, select JCA.
In the Home field, enter a path to your J2CA configuration directory where the repository, schemas, and other information is stored, for example
Middleware_Home\Oracle_SOA1\soa\thirdparty\ApplicationAdapters
Click OK.
A node representing the new configuration appears beneath the root configurations node. For example, Configurations: J2CA_SampleConfig
Locate the ra.xml file, which is located in the following directory: wls_home\erp-adapters\iwafjca.rar\META-INF\ra.xml
Open the ra.xml file in an editor.
Enter a value for the IWayHome property.
This is the folder where the adapter is installed. For example:
<Config-property>
<config-property-name>IWayHome</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>c:\Middleware_home\Oracle_SOA1\soa\thirdparty\ApplicationAdapters\</config-property-value>
</config-property>
Enter a value for the IWayConfig property.
This is the value that you specified when you created a new J2CA configuration using Application Explorer. For example:
<config-property>
<config-property-name>IWayConfig</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>J2CA_SampleConfig</config-property-value>
</config-property>
Enter a value for the Loglevel property.
This property can be set to DEBUG, INFO, or ERROR. For example:
<config-property>
<config-property-name>LogLevel</config-property-name>
Save the ra.xml file and exit the editor.
To deploy the J2CA Connector Application:
Start the Oracle WebLogic Server for the Oracle WebLogic Server domain that you have configured.
Open the Oracle WebLogic Server Administration Console in a web browser by entering the following URL: http://hostname:port/console where host name is the name of the computer where Oracle WebLogic Server is running and port is the port for the domain you are using. The port for the default domain is 7001
Log on to the admin console by entering your user name and password. In the Domain Structure section in the left pane, click Deployments. The Deployments page is displayed.
Click Install and the Install Application Assistant page is displayed
Browse to the following directory:
C:\Middleware_home\Oracle_SOA1\soa\thirdparty\Application-Adapters\iwafjca.rar.
Select Radio, next to iwafjca.rar and click Next.The Choose Targeting Style page is displayed.
Leave the default, Install this deployment as an application, selected and click Next. The Optional Settings page is displayed.
Click Next leaving the default values. The Summary page is displayed.
Click Finish. The Settings page for the J2CA (iwafjca) Connector Application opens.
Click Save.
In the Domain Structure section in the left pane, click Deployments.
Navigate through the table that lists all the deployed applications until you find the J2CA (iwafjca) Connector Application.
Select the check box next to iwafjca.
Click the Start submenu (down arrow) and select servicing all requests. The Start Application Assistant is displayed.
Click Yes to start the selected deployment.
From the list of deployed applications, select iwafjca.
Click the Testing tab. The Outbound Connection Pools and Connections Testing page is displayed.
Select the check box next to eis/OracleJCAAdapter/DefaultConnection and click Test. The Test Result column indicates Passed.
Start the Oracle WebLogic Server for the Oracle WebLogic Server domain that you have configured.
Open the Oracle WebLogic Server Administration Console in a web browser by entering the following URL: http://hostname:port/console where host name is the name of the computer where Oracle WebLogic Server is running and port is the port for the domain you are using. The port for the default domain is 7001
Click Install and the Install Application Assistant page is displayed
Log on to the admin console by entering your user name and password. In the Domain Structure section in the left pane, click Deployments. The Deployments page is displayed.
Browse to the following directory:
C:\ Middleware_home\Oracle_SOA\soa\thirdparty\Application-Adapters\iwafjca.rar.
Click Next. The Choose Targeting Style page is displayed.
Leave the default, Install this deployment as an application, selected and click Next. The Optional Settings page is displayed.
In the Name field, enter: Iwafjcatest. The Summary page is displayed.
Click Finish. The Settings page for the J2CA (iwafjca) Installation Verification Program (IVP) opens.
Click Save.
In the Domain Structure section in the left pane, click Deployments.
Navigate through the table that lists all the deployed applications until you find the J2CA (iwafjcatest) Installation Verification Program (IVP).
Select the check box next to iwafjcatest.
Click the Start submenu (down arrow) and select servicing all requests. The Start Application Assistant is displayed.
Click Yes to start the selected deployment.
From the list of deployed applications, select iwafjcatest.
Click the Testing tab. The Deployment Tests page is displayed. Click the links given in that page to verify the installation.
To connect to a new J2CA configuration:
Right-click the configuration to which you want to connect, for example, J2CA_SampleConfig.
Select Connect. Nodes appear for Adapters and Events. You can configure events using a J2CA configuration only.
Use the Adapters folder to create inbound interactions with Oracle Application Adapter for SAP R/3. For example, you can use the SAP node in the Adapters folder to configure a service that updates SAP R/3.
Use the Events folder to configure listeners that listen for events in SAP R/3.
You can now define new targets to Oracle Application Adapter for SAP R/3.
Defining a new configuration for BSE:
Start Application Explorer.
Right-click Configurations and select New. he New Configuration dialog box is displayed.
Enter a name for the new configuration, for example, BSE_SampleConfig, and click OK. The name of the BSE configuration that is specified here is used during the BSE deployment process.
From the Service Provider list, select iBSE.
In the iBSE URL field, accept the default URL or replace it with a different URL with the following format: http://host name:port/ibse/IBSEServlet where host name is the system on which Oracle WebLogic Integration resides and port is the HTTP port number where Oracle WebLogic Integration is listening.
Click OK. A node representing the new configuration appears beneath the root Configurations node.
Configuring settings for BSE:
Locate the web.xml file, which is located in the following directory:
wls_home\erp-adapters\ibse.war\WEB-INF\web.xml
Open the web.xml file in an editor.
Enter a value for the ibseroot parameter.
This is the folder where the BSE files are stored in subdirectories for each adapter.
For example:
<context-param>
<param-name>ibseroot</param-name>
<param-value>C:\ Middleware_home\Oracle_SOA1\soa\thirdparty\Application-Adapters\ibse.war</param-value>
<description>ibse root directory</description>
</context-param>
Enter a value for the iway.home parameter.
This is the folder where the adapter is installed.
For example:
<context-param>
<param-name>iway.home</param-name>
<param-value> C:\ Middleware_home\Oracle_SOA1\soa\thirdparty\Application-adapters /param-value>
<description>license file location</description>
</context-param>
Enter a value for the iway.config parameter.
This is the value that you specified when you created a new BSE configuration using Application Explorer.
For example:
<context-param>
<param-name>iway.config</param-name><param-value>BSE_SampleConfig</param-value>
<description>Base Configuration</description>
</context-param>
Save the web.xml file and exit the editor.
From the same directory, open the ibseconfig.xml file in an editor.
Enter a value for the afroot parameter, which is the path to the adapter lib directory.
For example:
<param name="afroot" type="string" required="false" value="c:\wls_home\erp-adapters\lib"/>
Enter a value for the afroot parameter, which is the path to the adapter lib directory.
For example:
<param name="afroot" type="string" required="false" value="c:\wls_home\erp-adapters\lib"/>
Start the Oracle WebLogic Server for the Oracle WebLogic Server domain that you have configured.
Open the Oracle WebLogic Server Administration Console in a web browser by enter the following URL: http://hostname:port/console where hostname is the name of the computer where Oracle WebLogic Server is running and port is the port for the domain you are using. The port for the default domain is 7001
Log on to the admin console by entering your user name and password.
In the Domain Structure section in the left pane, click Deployments. The Deployments page is displayed.
Click Install and the Install Application Assistant page is displayed
Browse to the following directory:
C:\ Middleware_home\Oracle_SOA1\soa\thirdparty\Application-adapters \ibse.war.
Select Radio, next to ibse.war and click Next.The Choose Targeting Style page is displayed.
Leave the default Install this deployment as an application selected and click Next.
The Optional Settings page is displayed. Click Next again leaving the default values. The Summary page is displayed.
Click Finish. The Settings page for the BSE (ibse) Connector Application opens.
Click Save. The following messages are displayed, which indicate a successful deployment.
In the Domain Structure section in the left pane, click Deployments.
Navigate through the table that lists all the deployed applications until you find the BSE (ibse) Application.
Select the check box next to ibse.
Click the Start submenu (down arrow) and select servicing all requests. The Start Application Assistant is displayed.
Click Yes to start the selected deployment.
From the list of deployed applications, select ibse.
Click the Testing tab.
Click the following link: http://soahostname:soaport/ibse.
Right-click the configuration to which you want to connect, for example, BSE_SampleConfig. Select Connect.
Nodes appear for Adapters, Events, and Business Services (also known as Webservices). The Business Services node is only available for BSE configurations. Events are not applicable when using a BSE configuration. You can configure events using a J2CA configuration only. As a result, you can disregard the Events node that appears for a BSE configuration.
As part of SAP Inbound adapter configuration, BAPI wsdls should be generated by following these steps:
Open Application Explorer (Oracle_Home/soa/thirdparty/ApplicationAdapters/tools/iwae/bin/ae.bat)
Navigate to SAP INBOUND and then right click to ”connect” to establish the connection to SAP. Connection to SAP establishes.
Navigate to ibse->Business Services->Services.
Right click on any service and click Save WSDL.
The following BAPI wsdls are generated with inline schema:
BAPI_MATERIAL_GET_ALL
BAPI_MATERIAL_GETALL
BAPI_STDMATERIAL_GETINTNUMBER
BAPI_MATERIAL_GET_DETAIL
CCAP_ECN_MAINTAIN
CCAP_REV_LEVEL_MAINTAIN
BAPI_MATERIAL_SAVEDATA
CSAP_MAT_BOM_CREATE
CSAP_MAT_BOM_MAINTAIN
CSAP_MAT_BOM_ALLOC_CREATE
CSAP_MAT_BOM_READ
BAPI_MAT_BOM_EXISTENCE_CHECK
Using inline schema code, XSD artifacts can be created per the location structure shown in the following table:
Table 2-17 List of SAP components for Item
| S. No | Path | Files |
|---|---|---|
|
1 |
/u01/app/oracle/Middleware/Oracle_Home/aia_12c/soainfra/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/SAP/Release1/Core/ABM/Item |
BAPI_MATERIAL_GET_ALL_request.xsd |
|
BAPI_MATERIAL_GET_ALL_response.xsd |
||
|
BAPI_MATERIAL_GET_DETAIL_request.xsd |
||
|
BAPI_MATERIAL_GET_DETAIL_response.xsd |
||
|
BAPI_MATERIAL_SAVEDATA_request.xsd |
||
|
BAPI_MATERIAL_SAVEDATA_response.xsd |
||
|
BAPI_STDMATERIAL_GETINTNUMBER_request.xsd |
||
|
BAPI_STDMATERIAL_GETINTINUMBER_response.xsd |
||
|
CCAP_REV_LEVEL_MAINTAIN_request.xsd |
||
|
CCAP_REV_LEVEL_MAINTAIN_response.xsd |
Table 2-18 List of SAP components for Bill of Material
| S.No | Path | Files |
|---|---|---|
|
2 |
/u01/app/oracle/Middleware/Oracle_Home/aia_12c/soainfra/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/SAP/Release1/Core/ABM/BillOfMaterial |
BAPI_MAT_BOM_EXISTENCE_CHECK_request.xsd |
|
BAPI_MAT_BOM_EXISTENCE_CHECK_response.xsd |
||
|
CCAP_ECN_MAINTAIN_request.xsd |
||
|
CCAP_ECN_MAINTAIN_response.xsd |
||
|
CCAP_REV_LEVEL_MAINTAIN_request.xsd |
||
|
CCAP_REV_LEVEL_MAINTAIN_response.xsd |
||
|
CSAP_MAT_BOM_ALLOC_CREATE_requestr.xsd |
||
|
CSAP_MAT_BOM_ALLOC_CREATE_response.xsd |
||
|
CSAP_MAT_BOM_READ_request.xsd |
||
|
CSAP_MAT_BOM_READ_response.xsd |
Table 2-19 List of SAP components for Change Order release
| S.No | Path | Files |
|---|---|---|
|
1 |
/u01/app/oracle/Middleware/Oracle_Home/aia_12c/soainfra/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/SAP/Release1/Core/ABM/EngineeringChangeOrder |
CCAP_ECN_MAINTAIN_request.xsd |
|
CCAP_ECN_MAINTAIN_response.xsd |
||
|
1 |
/u01/app/oracle/Middleware/Oracle_Home/aia_12c/soainfra/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/SAP/Release1/Core/Common |
IBSINFO_ADAPTEREXCEPTION.xsd |
|
XrefSchema.xsd |
Table 2-20 List of SAP components for Item Attribute updates
| S.No | Path | Files |
|---|---|---|
|
1 |
/u01/app/oracle/Middleware/Oracle_Home/aia_12c/soainfra/apps/AIAMetaData/AIAComponents/ApplicationObjectLibrary/SAP/V1/schemas |
MATMAS01 |
Once artifacts are created, create entry for all artifacts into UpdateMetadataDP.xml and register into MDS using the following script:
ant -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=$DOMAIN_LOCATION/soa/aia/MDSUtils/UpdateMetaDataDP.xml -DPropertiesFile=$DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml
