| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.1 Part Number E23118-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.1 Part Number E23118-04 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy Oracle Serialization and Tracking Integration Pack for Oracle Pedigree and Serialization Manager and Oracle E-Business Suite (Serialization and Tracking: OPSM - EBS).
This chapter includes the following sections:
Section 34.1.1, "Creating Oracle Data Integrator Repositories"
Section 34.3, "Configuring and Deploying the Serialization and Tracking: OPSM - EBS"
Section 34.6, "Undeploying Serialization and Tracking: OPSM - EBS"
To run AIA Pre-Built Integrations Installer you must have ODI access with Supervisor privileges.
For install purposes, the ODI software must reside on the same server where Foundation Pack is installed. After the Serialization and Tracking: OPSM - EBS installation is complete, the ODI software can be installed on another server (if desired) connecting to the master and work repositories used during the Serialization and Tracking: OPSM - EBS installation.
You can use an existing master repository if it exists on an Oracle database and its ID is not 200. If its ID is 200, AIA advises that you create a new master repository.
You can use an existing work repository if it exists on an Oracle database and its ID is not 900. If its ID is 900, AIA advises that you create a new master repository.
When you run the DCW, it inserts or updates the integration artifacts into these repositories.
AIA recommends that you take a backup of the master and work repositories before you start the install process.
For information about creating Oracle Data Integrator Master and Work repositories, see the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator, "Administering the Oracle Data Integrator Repositories."
Perform the following steps to apply the required patches to your ODI 11.1.1.5.0.
To install prerequisite installer patch #10288265:
Access My Oracle Support [https://support.oracle.com]
Navigate to the Patches & Updates tab
In the Patch Name or Number field, write 10288265
Select your platform
Click Search
Download and install patch #10288265
Access My Oracle Support [https://support.oracle.com]
Navigate to the Patches & Updates tab
In the Patch Name or Number field, write 12837214
Select your platform
Click Search
Download and install patch #12837214
After applying the patches, launch the ODI Installer:
Go to Topology.
Go to Physical Architecture.
Find the XML technologies and expand it.
You should see data sources for all DVM's used in your ODI flows.
Select each DVM data source.
Go to the JDBC tab.
Append this to the end of the URL "&back_compat_specific_keywords=true"
Test the data source to make sure the connection is successful.
Save your changes.
For a screenshot of this screen in ODI Installer, see Appendix B, "Oracle Data Integrator Screen".
The DCW screens prompt you to enter the data required for successful configuration of Serialization and Tracking: OPSM - EBS. Enter the details of Serialization and Tracking: OPSM - EBS screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.
All artifacts associated with the integration infrastructure components deploy to the PIP server. This screen contains the following fields:
Table 34-1 PIP Server Details Screen Fields
| Field | Description |
|---|---|
|
Admin Host Name |
Specifies where the admin server resides. This can be a remote server or the same system where the AIA Pre-Built Integrations Installer is launched. Example: The Admin Host Name is _________________________________ |
|
Admin Port |
This is the port number on which the Weblogic Admin server is started. To find this value contact the WebLogic administrator. Example: The Admin Port is _____________________________________ |
|
Domain Name |
This is WebLogic server domain corresponding to the Admin Server. Example: The Domain Name 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 _____________________________________ |
|
Managed Server |
After you enter the Admin Host Name, Admin Port and Admin User, this field populates with managed servers for the domain. Select the managed server from the list. If you are deploying the PIP to a SOA cluster, you should select the cluster name in this field. The Managed Server is _______________________________ |
|
Managed Port |
This field is automatically updated after you select the managed server. If you have configured a SOA Cluster, the SOA Cluster port appears in the list. |
Use this screen to enter details related to your Oracle Pedigree and Serialization Manager database instance. The screen contains the following fields:
Table 34-2 Oracle Pedigree and Serialization Manager Database Details Screen Fields
| Field | Description |
|---|---|
|
OPSM Database Host |
Specifies the fully qualified system name of the OPSM database. Example: OPSM Database Host is ______________________ |
|
OPSM Database Port |
To find this value, contact the database administrator. Example: OPSM Database Port is _________________ |
|
OPSM Database Username |
To find this value contact the database administrator. Example: OPSM Database Username is ______________________ |
|
OPSM Database Password |
To find this value, contact the database administrator. OPSM Database Password is ______________________ |
|
OPSM Database SID (System ID) |
To find this value, contact the database administrator. Example: OPSM Database SID is ______________________ |
|
OPSM Database Schema |
To find this value, contact the database administrator. The database schema name should be in upper case. Example: OPSM Database Schema is _________________________ |
Use this screen to enter details related to your Oracle E-Business Suite server instance. The screen contains the following fields:
Table 34-3 Oracle E-Business Suite Server Details Screen Fields
| Field | Description |
|---|---|
|
E-Business Suite Host Name |
Specifies the fully qualified system name of the Oracle E-Business Suite application. Example: E-Business Suite Host Name is ____________________ |
|
E-Business Suite Port |
This value is the Oracle E-Business Suite application port. To find this value, contact the administrator. Example: E-Business Suite Port is ___________________________ |
|
E-Business Suite User Name |
To find this value, contact the administrator. E-Business Suite User Name is _____________________ |
|
E-Business Suite Password |
To find this value, contact the administrator. E-Business Suite Password is ______________________ |
|
Workflow Business Event System Name |
This is the Workflow Business Event System Name of the E-Business Suite Server. For example: Workflow Business Event System Name is ___________________________ |
|
E-Business suite version |
This is the version of the E-Business Suite application. |
Use this screen to enter details related to your Oracle E-Business Suite database instance. The screen contains the following fields:
Table 34-4 Oracle E-Business Suite Database Details Screen Fields
| Field | Description |
|---|---|
|
E-Business Suite Database Host |
Specifies the system name. To find this value, contact the database administrator. Example: E-Business Suite Database Host is ___________________ |
|
E-Business Suite Database Port |
To find this value, contact the database administrator. Example: E-Business Suite Database Port is ___________________ |
|
E-Business Suite Database Username |
To find this value, contact the database administrator. Example: E-Business Suite Database Username is ______________ |
|
E-Business Suite Database Password |
To find this value, contact the database administrator. E-Business Suite Database Password is ______________ |
|
E-Business Suite Database SID (System ID) |
To find this value, contact the database administrator. Example: E-Business Suite Database SID is ____________________ |
|
E-Business Suite Database Schema |
To find this value, contact the database administrator. The database schema name should be in upper case. Example: E-Business Suite Database Schema is _______________________________ Note: All the database credentials are used for creating the connection pool URL and data source URLs. |
Use this screen to enter details for accessing Oracle Data Integrator. This screen contains the following fields:
Table 34-5 Oracle Data Integrator Access Information Details Screen Fields
| Field | Description |
|---|---|
|
ODI_HOME |
Provide the path to the ODI_HOME up to the oracledi folder (included). To find this value, contact your administrator. Example: ODI_Home is ___________________________ |
|
ODI User |
To find this value, contact your administrator. Example: ODI User is ____________________________________ |
|
ODI Password |
To find this value, contact your administrator. Example: ODI Password is _________________________________ |
|
Path for exported DVMs |
Enter the path to the directory where you want to export domain value mappings (DVMs). Example: One of the steps for setting up the integration is to export some DVMs to a location. The Installer must have this location to configure ODI artifacts during the install. It is recommended that you select a location in the same server where the ODI software runs. Path for exported DVMs is _______________________ |
You must set up an ODI Master Repository before installing the Serialization and Tracking: OPSM - EBS. This master repository must be created in an Oracle database.
The install process appends integration artifacts into this master repository.
Use this screen to enter details to access the Oracle Data Integrator master repository. If the master repository is configured, field values in the screen populate automatically.
The screen contains the following fields:
Table 34-6 Oracle Data Integrator Master Repository Details Screen Fields
| Field | Description |
|---|---|
|
Database Host Name |
To find this value, contact your database administrator. Example: Database Host Name is _______________________________ |
|
Database Port Number |
To find this value, contact your database administrator. Example: Database Port Number is ________________________________ |
|
Database Username |
To find this value, contact your database administrator. Example: Database Username is _______________________________ |
|
Database Password |
To find this value, contact your database administrator. Example: Database Password is _________________________________ |
|
Database SID (System ID) |
To find this value, contact your database administrator. Example: Database SID is __________________________________ |
You must set up an ODI Work Repository before installing the Serialization and Tracking: OPSM - EBS. The install process imports the Serialization and Tracking: OPSM - EBS ODI artifacts into an ODI work repository. You can provide an existing ODI work repository or provide an empty one that has been created specifically for the PIP. It is recommended that you use an empty repository.
Use this screen to enter details related to the ODI work repository. If the master repository is configured, field values in the screen populate automatically.
The screen contains the following fields:
Table 34-7 Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS Details Screen Fields
| Field | Description |
|---|---|
|
ODI Work Repository Name |
Enter the name you gave to the ODI work repository for PIP Artifacts. Example: ODI Work Repository Name is ___________________________ |
|
ODI Work Repository ID |
Enter the ID number that you used for the ODI work repository. It should be between 1 and 899. Example: Do not use 900. Also do not use the ID used for other work repositories. ODI Work Repository ID is ______________________________ |
|
ODI Work Repository Database Host |
To find this value, contact your database administrator. Example: ODI Work Repository Database Host is_______________________________ |
|
ODI Work Repository Database Port |
To find this value, contact your database administrator. Example: ODI Work Repository Database Port is________________________________ |
|
ODI Work Repository Database SID |
To find this value, contact your database administrator. Example: ODI Work Repository Database SID is__________________________________ |
|
ODI Work Repository Database Username |
To find this value, contact your database administrator. Example: ODI Work Repository Database Username is_______________________________ |
|
ODI Work Repository Database Password |
To find this value, contact your database administrator. ODI Work Repository Database Password is_________________________________ |
|
ODI Work Repository Database Schema |
To find this value, contact your database administrator. The database schema name should be in upper case. Example: ODI Work Repository Database Schema is __________________________________ |
This section discusses the integration configuration and deployment process. There are two steps:
Configure your integration using the deployment DCW.
Deploy the integration to the Fusion Middleware server.
The screens that appear prompt you to enter the data that is required for successful configuration of Serialization and Tracking: OPSM - EBS. Keep the completed worksheets of Serialization and Tracking: OPSM - EBS screens ready before you launch the DCW.
Note:
If you are harvesting content to OER, perform the first three steps. Else start from step 4.
To configure Serialization and Tracking: OPSM - EBS:
Navigate to /slot/emsxxxx/oracle/Middleware/user_projects/domains/soa_domain/bin/ and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.
Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".
Restart the server.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh for Linux based systems and aiaconfig.bat for Microsoft Windows.
This launches the AIA DCW.
Click Next.
Select Serialization and Tracking: OPSM - EBS.
Click Next.
To specify PIP Server details:
Enter information related to your PIP server in the PIP Server Details screen.
Click Next.
To specify Oracle Pedigree and Serialization Manager Database details:
Enter information about your Oracle Pedigree and Serialization Manager Database instance in the Oracle Pedigree and Serialization Manager Database Details screen.
Click Next.
To specify Oracle E-Business Suite Server details:
Enter information about your Oracle E-Business Suite Server in the E-Business Suite Server Details screen.
Click Next.
To specify Oracle E-Business Suite Database details:
Enter information about your Oracle E-Business Suite Database in the E-Business Suite Database Details screen.
Click Next.
To specify Oracle Data Integrator Access details:
Enter information about your Oracle Data Integrator Access installation in the Oracle Data Integrator Access Information screens.
Oracle Data Integration Access Information is captured in three screens. Enter the following information in the screens.
Specify ODI Home.
Click Next.
Enter ODI User and ODI Password.
Click Next.
To specify Oracle Data Integrator Master Repository details:
Enter information about your Oracle Data Integrator Master Repository installation in the Oracle Data Integrator Master Repository screen.
Click Next.
To specify Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS details:
Enter information about your Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS installation in the Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS screen.
Click Next.
Review the configuration information on the Configuration Summary screen.
Note:
If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.
You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the PIP. You can configure using the steps described in Section 34.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.
Click Configure to accept the configuration.
The system displays progress of the configuration in the Configuration Progress screen.
The system displays any warnings or errors as necessary. You can review the configuration log for additional details. The configuration log location is displayed in Configuration Progress screen.
When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.
Click Finish to close the DCW.
To configure using the response file:
Open the response file.
When you create a response file through OUI, passwords get stored as <SECURE>.
Replace the password fields with actual passwords in the response file.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh <Response File Location and Name> for Linux based systems and aiaconfig.bat <Response File Location and Name> for Microsoft Windows.
To deploy the integration to Fusion Middleware server:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Run the command for your platform.
Note:
When you copy and paste the command in the command line, ensure that there is space between .xml and -. Ensure that there is space between these two when you run undeployment command too.
Table 34-8 Deployment Commands for the Serialization and Tracking: OPSM - EBS
| Platform | Deployment Command |
|---|---|
|
Linux Solaris SPARC IBM AIX Based Systems. HP-UX |
ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbizDP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbiz.log |
|
Microsoft Windows |
ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizDP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -l <AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizDP.log |
Note:
In Windows 2008, 2008 R2 and Vista, run the command prompt as an administrator (elevated mode). If the command prompt is invoked in normal mode, the PIPs are not displayed.
Review the log file in the location specified in the command to verify successful deployment.
Oracle AIA ships artifacts in AIA Lifecycle Workbench which can be used in your integrations. These artifacts are created using FMW technologies such as, BPEL and Mediator and are natively supported by AIA Foundation Pack tools such as, Project Lifecycle Workbench, Harvester, Deployment Generator, AIA Deployment Driver (ADD). These are called native artifacts and they include SOA artifact types such as, composites, DataSources, DVM, xRef, and so on. These artifacts can be modified or new natively supported artifacts can be added using the AIA Lifecyle Workbench and a BOM.xml file can be generated.
AIA PIP development teams, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, integration may require artifacts such as, Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.
For more information on deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".
This section discusses postdeployment configurations for the Serialization and Tracking: OPSM - EBS integration. The section includes:
Section 34.4.2, "Launching the Serialization and Tracking: OPSM - EBS Agent"
Section 34.4.3, "Stopping the Serialization and Tracking: OPSM - EBS Agent"
Section 34.4.5, "Configuring Web Services for Serialization and Tracking: OPSM - EBS (Optional)"
Section 34.4.6, "Verifying the Database Connection (Optional)"
Section 34.4.9, "Maintaining Serialization and Tracking: OPSM - EBS"
Configure the following environment variables:
The Serialization and Tracking: OPSM - EBS agent should be up and running before you execute any scenario from ODI or OPSM.
To start the Serialization and Tracking: OPSM - EBS agent, navigate to <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/Agent_Files directory and run the start_odi_agent.bat file (or start_odi_agent.sh in Linux) command.
The agent is launched as a listener.
Note:
Ensure that the executable permission is enabled on all the shell scripts.
When you are not using integration, you can stop the Serialization and Tracking: OPSM - EBS agent.
To stop the Serialization and Tracking: OPSM - EBS agent, navigate to <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/Agent_Files directory and run the stop_odi_agent.bat file (or stop_odi_agent.sh in Linux).
A number of variables must be configured in ODI to support the Serialization and Tracking: OPSM - EBS. Many variables are configured when you install the integration. Configure the following variables using the ODI Designer. After the variables are defined in the ODI Designer, run the Regenerate All Scenarios package to reconfigure the main integration packages.
Table 34-10 ODI Variables to be Configured for the Serialization and Tracking: OPSM - EBS
| ODI Variable | Description |
|---|---|
|
PVV_FROM_EMAIL_ADDRESS |
Email address for notification result queries. |
|
PVV_TO_EMAIL_ADDRESS |
Email addresses of individuals to be notified of integration results. Separate multiple email addresses with a comma. |
|
PVV_PIP_HOME |
Home directory of the PIP. Default value is <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1 |
|
PVV_MAIL_SERVER |
Mail server to which email is to be forwarded for notification. |
All the ODI scenarios must be regenerated if any variable value is changed. To regenerate the ODI scenarios:
Open ODI Operator.
Expand the Scenarios tab.
Right click the scenario you want to regenerate.
Click Regenerate option.
Click OK twice.
Configure the following services:
CreateShipmentReceiptListEbizJMSProducer
CreateShipmentReceiptListEbizJMSConsumer
CreateShipmentReceiptListEbizReqABCSImpl
ShipmentReceiptEBS
CreateShipmentReceiptListPASProvABCSImpl
CreateShipmentReceiptListPASJMSProducer
CreateAdvanceShipmentNoticeListEbizJMSProducer
CreateAdvanceShipmentNoticeListEbizJMSConsumer
CreateAdvanceShipmentNoticeListEbizReqABCSImpl
AdvanceShipmentNoticeEBS
CreateAdvanceShipmentNoticeListPASProvABCSImpl
CreateAdvanceShipmentNoticeListPASJMSProducer
SyncItemLotListEbizJMSProducer
SyncItemLotListEbizJMSConsumer
SyncItemLotListEbizReqABCSImpl
ItemLotEBS
SyncItemLotListPASProvABCSImpl
SyncItemLotListPASJMSProducer
To configure the above Web Services, see Oracle Serialization and Tracking Integration Pack for Oracle Pedigree and Serialization Manager and Oracle E-Business Suite Implementation Guide.
To verify the database connection:
Open ODI Topology Manager.
Navigate to Technologies, Oracle in the Physical Architecture tab and expand the Oracle node.
Select PASDS.
Right click and select Open.
Click Test Connection.
The Test Connection window appears.
Click Test.
If successful connection message does not appear, verify the connection information in the Definitions and JDBC tabs.
Repeat steps 1 - 6 for the following data sources:
OracleEbizDS
WorkRepDS
To configure the Remote OPSM JMS Queue in Serialization and Tracking: OPSM - EBS:
Navigate to Administration Console (http://<server name>:<port number>/console).
Log in with the server admin user name. For access details, contact the system administrator.
Navigate to Domain Structure, soa_domain, Deployments.
Click AIA_JmsAdapter_Config in the Deployments table.
Select Configuration Tab.
Select Outbound Connection Pools tab.
Click eis/wlsjms/AIAPASCF instance in the Outbound Connection Pool Configuration Table.
Update the following properties and leave the rest of the properties with their default values:
Table 34-11 Properties to be Updated for Configuring the Remote OPSM JMS Queue
| Property Name | Property Type | Property Value |
|---|---|---|
|
ConnectionFactoryLocation |
Java.lang.String |
oracle/apps/jms/pas/OPSMCF |
|
FactoryProperties |
Java.lang.String |
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://<OPSM server host >:<SOA port number> |
Click Save.
Navigate back to soa_domain, Deployments.
Select AIA_JmsAdapter_Config and click Update.
Select the option Update this application in place with new deployments plan changes…….
Click Finish.
Cross Domain Security establishes trust between two WebLogic Server domain pairs by using a credential mapper to configure communication between these WebLogic Server domains.
To configure Cross Domain Security between the OPSM Weblogic Server domain and the PIP WebLogic Server domain:
Enable Cross Domain Security.
Open Administration Console: http://<server name>:<port number>/console.
Log in with the server admin user name. For access details, contact the system administrator.
Navigate to Domain Structure, soa_domain.
Open the Security: General tab in the console.
Check Cross Domain Security Enabled.
Click Save.
Repeat steps a to f for the OPSM WebLogic Server domain.
Configure a Cross Domain User.
Cross-domain security in WebLogic Server uses a global security role named CrossDomainConnector with resource type remote and a group named CrossDomainConnectors, which is assigned the CrossDomainConnector role. Invocation requests from remote domains are expected to be from users with the CrossDomainConnector role. By default, the CrossDomainConnectors has no users as members. You must create one or more users and add them to the group CrossDomainConnectors. Typically, such a user is a virtual system user and preferably should have no privileges other than those granted by the CrossDomainConnector security role.
Open Administration Console: http://<server name>:<port number>/console.
Log in with the server admin user name. For access details, contact the system administrator.
Navigate to Domain Structure, soa_domain, Security Realms.
Click the name of your security realm (default is myrealm).
Open the Users and Groups tab in the console.
Click New to create a user.
Enter the Name, Description, and Password for the new user and click OK.
On the Users and Groups: Users tab, click the name of the user you just created.
Open the Groups tab.
Find the CrossDomainConnectors group in the list of available parent groups on the left and click the shuttle button to move that group into the chosen group list on the right.
Click Save.
Repeat these steps for the OPSM WebLogic Server domain to create a cross domain user in that domain.
Configure a Credential Mapping for Cross Domain Security.
In each WebLogic Server domain, you must specify a credential to be used by each user on each remote domain to be trusted. Do this by configuring credential mappings for each domain in the connection.
Open Administration Console: http://<server name>:<port number>/console.
Log in with the server admin user name. For access details, contact the system administrator.
Navigate to Domain Structure, soa_domain, Security Realms.
Click the name of your security realm (default is myrealm).
Open the Credential Mappings: Default tab and click New.
On the Creating the Remote Resource for the Security Credential Mapping:
Select Use cross-domain protocol.
In the Remote Domain field, enter the name of the remote domain that must interact with the local domain.
Leave blank the Protocol, Remote Host, Remote Port, Path, and Method parameters.
Click Next.
On the Create a New Security Credential Mapping Entry page, enter the following:
Local User: cross-domain
Remote User: User configured in the Remote Domain that is authorized to interact with the Local Domain.
Password: The password for the Remote User.
Click Finish.
Repeat the steps for the OPSM WebLogic Server domain to create a credential mapping for cross domain security on that domain.
Serialization and Tracking: OPSM - EBS integration files are maintained in the <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1 (PIP_HOME) directory. This directory contains DVM xml files, Agent files, and error log files used by the ODI flows.
DVM xmls: Serialization and Tracking: OPSM - EBS integration is delivered with the location and work order status DVM xml files with their defaults mapping values. DVM files are maintained in the DVM_XMLS directory, which is available under the PIP_HOME directory. You can add additional mapping values by editing these xml files. The table below is an example of the Location DVM xml.
Agent files: Agent files are maintained in the Agent_Files directory, which is available under the PIP_HOME directory. To execute an ODI flow you must start an agent from this location.
Error logs: Error log files are used by the ODI flows. These logs are maintained in the ODI_Error_Records directory, which is available under PIP_HOME directory.
Add read,write and execute permissions for group, owner and others to all the files that are available under following folders:
<AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/Agent_Files
<AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/DVM_XMLS
<AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/ODI_Error_Records
To verify Serialization and Tracking: OPSM - EBS deployment:
Open the log files from the following location and look for warnings and error messages:
For Linux, Solaris SPARC, HP-UX and IBM AIX Based Systems: Review the install log located at <AIA_HOME>/aia_instances/<instance name>/logs to verify that the integration is successfully installed.
For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify that the integration is successfully installed.
Confirm that the Serialization and Tracking: OPSM - EBS components were successfully installed.
Log in to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).
Log in with the server admin user name. For access details, contact the system administrator.
Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:
AdvanceShipmentNoticeEBS
CreateAdvanceShipmentNoticeListEbizJMSConsumer
CreateAdvanceShipmentNoticeListEbizJMSProducer
CreateAdvanceShipmentNoticeListEbizReqABCSImpl
CreateAdvanceShipmentNoticeListPASJMSProducer
CreateAdvanceShipmentNoticeListPASProvABCSImpl
CreateShipmentReceiptListEbizJMSConsumer
CreateShipmentReceiptListEbizJMSProducer
CreateShipmentReceiptListEbizReqABCSImpl
CreateShipmentReceiptListPASJMSProducer
CreateShipmentReceiptListPASProvABCSImpl
ItemLotEBS
ShipmentReceiptEBS
SyncItemLotListEbizJMSConsumer
SyncItemLotListEbizJMSProducer
SyncItemLotListEbizReqABCSImpl
SyncItemLotListPASJMSProducer
SyncItemLotListPASProvABCSImpl
Confirm that the Serialization and Tracking: OPSM - EBS queues (JMS) are installed.
Log in to the Administration Console (http://<server name>:<port number>/console).
Log in with the server admin user name. For access details, contact the system administrator.
Navigate to soa_domain, Services, Messaging, JMS Modules, AIAJDBCJMSModule.
Verify that the following queues exist in the summary of Resource table.
AIA_EbizItemLotJMSQueue: This queue is used between the SyncItemLotListEbizJMSProducer and SyncItemLotListEbizJMSConsumer.
AIA_EbizAdvanceShipmentNoticeJMSQueue: This queue is used between the CreateAdvanceShipmentNoticeListEbizJMSProducer and CreateAdvanceShipmentNoticeListEbizJMSConsumer.
AIA_EbizShipmentReceiptJMSQueue: This queue is used between the CreateShipmentReceiptListEbizJMSProducer and CreateShipmentReceiptListEbizJMSConsumer.
AIAEbizCF: This connection factory is used to connect AIA_EbizItemLotJMSQueue, AIA_EbizAdvanceShipmentNoticeJMSQueue, and AIA_EbizShipmentReceiptJMSQueue.
AIAPASCF: This connection factory is used to connect the JMS Queues that are available in the OPSM application which are OPSMLotSynchQueue and OPSMCreateTransactionQueue.
Confirm that the necessary configuration properties exist.
Log in to AIA home. For example, http://<host_name>:<port>/AIA/faces/aiaHomeLogin.jspx.
Navigate to Setup, AIAConfiguration and check that the following configuration properties are listed:
CreateShipmentReceiptListEbizReqABCSImpl
CreateShipmentReceiptListPASProvABCSImpl
CreateAdvanceShipmentNoticeListEbizReqABCSImpl
CreateAdvanceShipmentNoticeListPASProvABCSImpl
SyncItemLotListEbizReqABCSImpl
SyncItemLotListPASProvABCSImpl
Verify Integration Scenarios.
Log in to AIA home. For example, http://<host_name>:<port>/AIA/faces/home.jspx.
Find Project Lifecycle Workbench and click Go.
On the AIA Project Lifecycle Workbench page, select industry as core and click Search.
Click the link in the Bill Of Material column to view the following artifacts included in this integration.
AdvanceShipmentNoticeEBS
CreateAdvanceShipmentNoticeListEbizJMSConsumer
CreateAdvanceShipmentNoticeListEbizJMSProducer
CreateAdvanceShipmentNoticeListEbizReqABCSImpl
CreateAdvanceShipmentNoticeListPASJMSProducer
CreateAdvanceShipmentNoticeListPASProvABCSImpl
CreateShipmentReceiptListEbizJMSConsumer
CreateShipmentReceiptListEbizJMSProducer
CreateShipmentReceiptListEbizReqABCSImpl
CreateShipmentReceiptListPASJMSProducer
CreateShipmentReceiptListPASProvABCSImpl
ItemLotEBS
ShipmentReceiptEBS
SyncItemLotListEbizJMSConsumer
SyncItemLotListEbizJMSProducer
SyncItemLotListEbizReqABCSImpl
SyncItemLotListPASJMSProducer
SyncItemLotListPASProvABCSImpl
Verify the following connections are accurate in the Physical Architecture tab.
Launch ODI Topology Manager and navigate to Physical Architecture tab.
Expand XML node under Technologies and double click LocationDS.
Click JDBC tab and check for the connection <PVV_PIP_HOME>/DVM_XMLS/ LOCATION.xml.
Similarly, find the following data servers based on the technology name.
Verify the context in the Contexts tab.
Launch ODI Topology Manager and navigate to Contexts tab.
Double click EBIZ_01 and navigate to Schemas tab.
Table 34-14 Verifying Context in the Serialization and Tracking: OPSM - EBS
| Context | Description |
|---|---|
|
EBIZ_01 |
Holds the correlation between logical schemas and physical ones. Verify the following schema association is set up. You may see more schemas than the one that is here. The integration processes ignore these additional schemas. Location OracleEbiz PAS WorkOrderStatus WorkRep |
Verify the following Logical Data Servers are imported in the Logical Architecture tab.
Launch ODI Topology Manager and navigate to Logical Architecture tab.
Expand XML node and double click Location logical schema.
Select Definition tab and verify that the EBIZ_01 context has the LocationDS physical schema associated with it.
Similarly, find the following logical data servers based on the technology.
Launch the ODI Designer and verify that the OracleEbiz To PAS Model folder is imported in the Models tab. Expand the OracleEbiz To PAS Model folder and verify that the following models are present:
Location DVM Model
OracleEbiz Model
PAS Model
Work Order Status Model
Launch the ODI Designer and verify that the OracleEbiz To PAS Project project is imported in the Project tab. Expand the OracleEbiz To PAS Project project and verify that the following project folders are present:
OracleEbiz To PAS Bulk Lot Folder
OracleEbiz To PAS Product Serialization Folder
OracleEbiz To PAS Product Synchronization Folder
Expand the OracleEbiz to PAS Product Synchronization folder.
Double-click the Load Location DVM XML procedure.
Double-click the command Load Location DVM in the Details tab.
Under Definition tab, click Command on Source sub tab.
Verify that the path to LOCATION.xml is accurate.
Using the same procedure verify the path for the Load Work Order Status DVM XML.
Verify that the WSDL URL for the InvokeAIASyncErrorHandling step name is accurate for the AIAAsyncErrorHandlingBPELProcess in the Load OracleEbiz DiscreteMfg Bulk Lot Data to PAS package.
Launch ODI Designer.
Navigate to Projects tab.
Expand the OracleEbiz To PAS Bulk Lot Folder.
Double click Load OracleEbiz DiscreteMfg Bulk Lot Data to PAS Pkg.
Select the Diagram tab.
Click the InvokeAIAAsyncErrorHandling icon.
In the Properties frame under the General tab verify that the WSDL URL user and password are accurate.
Verify that the error log location for the Error Notification Step is accurate in the Load OracleEbizDiscreteMfg Bulk Lot Data to PAS Package.
Click Email Notification step in Load OracleEbiz DiscreteMfg Bulk Lot Data To PAS package.
In the properties frame under the General tab verify that the attachment url is accurate.
Verify the OPSM database connection in the Load Error Records step.
Double click the Load Error Log step in the Load OracleEbiz DiscreteMfg Bulk Lot to PAS Pkg.
In the properties frame under the General tab verify that the JDBC URL is pointing to OPSM database.
Repeat steps 10 - 13 for all the packages under the following folders.
OracleEbiz To PAS Bulk Lot Folder
OracleEbiz To PAS Product Serialization Folder
All SOA composites are protected by the Global Policies provided by Foundation Pack as defined in the Security section of the Foundation Pack Developer's Guide. Additionally, individual services for this integration have locally attached security policies.
To validate locally attached security policies:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Navigate to Weblogic domain, soa_domain. In the window to the right, select the WebLogic Domain, then navigate to Web Services, Policies.
Verify Service Policy attachment.
Find the service policy in the list of policies.
Click the number in Attachment Count column.
The Usage Analysis screen appears.
Change the Subject Type list box to SOA Service.
Validate that all the composites are listed with local attachment to this service policy.
Verify Client Policy attachment.
Navigate back to the Policies screen and find the client policy.
Click the number in Attachment Count column.
The Usage Analysis screen appears.
Change the Subject Type list box to SOA Reference.
Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.
Table 34-16 No Authentication Service Policy Attachments for Serialization and Tracking: OPSM - EBS
| Composite | Service Policy |
|---|---|
|
CreateAdvanceShipmentNoticeListEbizJMSProducer |
oracle/no_authentication_service_policy |
|
CreateShipmentReceiptListEbizJMSProducer |
oracle/no_authentication_service_policy |
|
SyncItemLotListEbizJMSProducer |
oracle/no_authentication_service_policy |
Table 34-17 Saml or User Name or Http Opt On Client Policy Attachments for Serialization and Tracking: OPSM - EBS
| Composite | Reference | Client Policy |
|---|---|---|
|
CreateAdvanceShipmentNoticeListEbizReqABCSImpl |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON |
|
CreateAdvanceShipmentNoticeListEbizProvABCSImpl |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON |
|
CreateShipmentReceiptListEbizReqABCSImpl |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON |
|
CreateShipmentReceiptListEbizProvABCSImpl |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON |
|
SyncItemLotListEbizReqABCSImpl |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON |
|
SyncItemLotListPASProvABCSImpl |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON |
For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."
For implementation, see Oracle Serialization and Tracking Integration Pack for Oracle Pedigree and Serialization Manager and Oracle E-Business Suite Implementation Guide.
To undeploy the Serialization and Tracking: OPSM - EBS from Fusion Middleware Server:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Run the undeployment command for your platform.
Table 34-18 Undeployment Command for Serialization and Tracking: OPSM - EBS
| Platform | Undeployment Command |
|---|---|
|
Linux Solaris SPARC IBM AIX Based Systems. HP-UX |
ant Uninstall -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<AIA_Instance_name>/config/AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbizUndeployDP.xml -l <AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbizUndeployDP.log |
|
Microsoft Windows |
ant Uninstall -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<AIA_Instance_name>\config\AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizUndeployDP.xml -l <AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizUndeployDP.log |
Restart the SOA server.
Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
