Skip Headers
Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations
Release 11.5

E40086-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

15 Configuring and Deploying Product MDM Base Pack

This chapter discusses how to configure and deploy the Oracle Product Master Data Management Integration Base Pack (Product MDM Base Pack).

This chapter includes the following sections:

15.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Product MDM Base Pack. Enter the details of the Product MDM Base Pack screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

15.1.1 Integration Server Details Screen

All artifacts associated with the integration infrastructure components deploy to the integration server. This screen contains the following fields:

Table 15-1 Integration Server Details Screen Fields

Field Description

Admin Host Name

This is where the admin server resides. This can be a remote server or the same computer where the AIA Pre-Built Integrations Installer is launched. Example: server1.company.com.

The Admin Host Name is _________________________________

Admin Port

This is the port number on which Weblogic Admin server is started. To find this value contact WebLogic administrator. Example: 7001.

The Admin Port is _____________________________________

Domain Name

This is WebLogic server domain corresponding to the Admin Server. Example: domain1

The Domain Name is _____________________________________

Admin User

This value is the WebLogic admin user name. To find this value contact your WebLogic administrator.

The User Name 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, Domain Name, Admin user name and Admin Password, this field gets populated with managed servers for the domain. Select the manager server from the list. If you are deploying the integration to a SOA cluster, you should select the cluster name in this field.

The Managed Server is _______________________________

Managed Port

This field gets updated automatically after you select the managed server. If you have configured a SOA Cluster the SOA Cluster port appears in the list.


15.1.2 Oracle PIM Server Details Screen

Use this screen to enter details related to your PIM server instance. The screen contains the following fields:

Table 15-2 Oracle PIM Server Details Screen Fields

Field Description

Oracle Product Hub Host Name

This is the computer name of the Oracle Product Hub (PIM) application. For example: rws60052rems.example.com. To find the value, contact your administrator.

Oracle Product Hub Host Name is _________________________________

Oracle Product Hub Port

This value is the PIM application port. For example: 1617. To find the value, contact your administrator.

Oracle Product Hub Port is _________________________________

Oracle Product Hub User Name

This is the user name for Oracle Product Hub. For example: mfg. To find the value, contact your administrator.

Oracle Product Hub User Name is _________________________________

Oracle Product Hub Password

This is the password for Oracle Product Hub. For example: welcome. To find the value, contact your administrator.

Oracle Product Hub Password is ________________________________

Workflow Business Event System Name

This is the Workflow Business Event System Name for the Oracle Product Hub. For example: SID.EXAMPLE.COM. To find the value, contact your administrator.

Workflow Business Event System Name is __________________


15.1.3 Oracle PIM Database Details Screen

Use this screen to enter details related to your PIM database instance. The screen contains the following fields:

Table 15-3 Oracle PIM database Details Screen Fields

Field Description

Oracle Product Hub Database Host

This value is typically the computer name. For example: rws60052rems.example.com. To find the value, contact your database administrator.

Oracle Product Hub Database Host is ______________________________

Oracle Product Hub Database Port

This is the Database port for Oracle Product Hub (PIM). For example: 8096. To find the value, contact your database administrator.

Oracle Product Hub Database Port is ______________________________

Oracle Product Hub Database Username

This is the database user name for Oracle Product Hub (PIM). For example: apps. To find the value, contact your database administrator.

Oracle Product Hub Database Username is _______________________

Oracle Product Hub Database Password

This is the password for Oracle Product Hub (PIM). To find the value, contact your database administrator.

Oracle Product Hub Database Password is _________________________

Oracle Product Hub Database SID

This is the Database SID for Oracle Product Hub. For example: orcl. To find the value, contact your database administrator.

Oracle Product Hub Database SID is _________________________________


15.2 Performing Predeployment Configurations

This section discusses predeployment configurations for the MDM Product Base Pack.

15.2.1 Configuring the Timeout Values

This section describes how to modify the JTA Transaction Value and the SyncMaxWaitTime values.

To modify JTA Transaction Value:

  1. Log in to the WebLogic Server console.

  2. Navigate to soa_domain >> Services >> JTA.

  3. Change the value of the property Timeout Seconds to 3600.

  4. Click Save and activate the changes.

To modify SyncMaxWaitTime values:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

  2. Expand the SOA folder and right-click soa-infra.

  3. Select SOA Administration, BPEL Properties.

  4. Click the More BPEL Configuration Properties link.

  5. Change the value of syncMaxWaitTime to 120.

  6. Click Apply.

Note:

These TimeOut values must be adjusted appropriately based on the environment configurations for each customer.

15.3 Overall Configuration and Deployment of MDM Product Integrations

The overall MDM Product integration consists of four component integrations: MDM Product Base Pack (OPH) and three other options: MDM Product Siebel, MDM Product E-Business Suite and MDM Product BRM. The overall MDM Product integration can be configured and deployed by selecting any integration or integration combination. The configuration and deployment process consists of the following steps:

  1. Configure and deploy the MDM Product component integrations. Section 15.4 discusses configuring and deploying the Product MDM Base Pack. For detailed instructions on the other MDM Product integrations, see your specific integration chapters in Part II, "Configuring and Deploying Pre-Built Integrations" of this guide.

  2. Deploy the MDM Product Routing Rules following the instructions discussed in Chapter 19, "Deploying Product MDM: Routing Rules". Routing Rules wire the integration services, depending on the integrations deployed.

15.4 Configuring and Deploying the MDM Product Base Pack

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

15.4.1 Configuring the MDM Product Base Pack

The screens that appear prompt you to enter the data that is required for successful configuration of the MDM Product Base Pack. Keep the completed worksheets of the MDM Product Base Pack screens ready before you launch the DCW.

To configure the MDM Product Base Pack:

Note:

If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.

  1. 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.

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

  4. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure installation environment.

  5. 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.

  6. Click Next.

  7. Select Oracle Product Master Data Management Integration Base Pack under Product Master Data Management Pre-Build Integration

  8. Click Next.

15.4.1.1 Specify Integration Server Details

To specify integration server details:

  1. Enter information related to your integration server in the Integration Server Details screen.

  2. Click Next.

15.4.1.2 Specify Oracle PIM Server Details

To specify Oracle PIM Server details:

  1. Enter server information about Oracle PIM in the Oracle PIM Server Details screen.

  2. Click Next.

15.4.1.3 Specify Oracle PIM Database Details

To specify Oracle PIM Database details:

  1. Enter information about your Oracle PIM Database in the Oracle PIM Database Details screen.

  2. Click Next.

15.4.1.4 Complete Configuration

To complete configuration:

  1. 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 integration. You can configure using the steps described in Section 15.4.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.

  2. Click Configure to accept this configuration and begin the installation.

    The system displays progress of 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.

  3. When the configuration process finishes without errors, click Next.

  4. When the AIA DCW displays the Configuration Complete screen, click Finish to close the DCW.

15.4.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

  3. 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.

  4. 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.

15.4.3 Deploying the MDM Product Base Pack

To deploy the integration to Fusion Middleware server:

  1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems to configure the environment.

  2. Run the command for your platform.

    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 integrations are not displayed.

    Table 15-4 Deployment Commands for the MDM Product Base Pack

    Platform Deployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/pips/MDMProductPIM/DeploymentPlans/deployPIM.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\MDMProductPIM\DeploymentPlans\deployPIM.bat
    

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/MDMProductPIM_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.

Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator and AID. These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.

Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy 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".

15.5 Performing Postdeployment Configurations

This section discusses post deployment configuration for MDM Product Base Pack. This section includes:

15.5.1 Configuring Endpoint URLs for Oracle PIM Web Services

Configure PIM web-services on a FMW application server. The details of this configuration are available in the note 888696.1 on My Oracle Support.

If you have installed the PIM web-services on the FMW where the Product MDM Base Pack is installed, you do not require any configuration changes.

If you have installed the PIM web-services on a different application server, follow the below steps to update endpoint URLs in the AIA layer after the installation of the integration.

  1. Log in to Weblogic Console.

  2. Under Domain Structure , click Deployments.

  3. Select the PIM-Webservice deployed. For example, PIMWebServices-Valueset-WS. Click Testing tab.

  4. Expand ValueSetService and click ?WSDL under Test Point

  5. Note the URL that opens in your browser. Open the AIAConfigurationProperties.xml file located in

    <AIA_INSTANCE>/AIAMetaData/config.

  6. In the AIAConfigurationProperties.xml file, search the ServiceConfiguration section for the SyncSpecificationValueSetListPIMReqABCSImpl service. In this section, locate the property Routing.ValueSetService.PIM_01.EndpointURI

  7. The hostname:port points to the AIA FMW server. Update the hostname:port path to the server on which PIM web services have been deployed.

    Verify that the Routing.ValueSetService.PIM_01.EndpointURI is same as the URL noted in step 5.

  8. Repeat steps 1 to 7 for the following service/property-names.

    1. Deployed Webservice - PIMWebServices-ICC-WS

      Service: SyncItemCatalogCategoryPIMReqABCSImpl

      Property:Routing.ItemCatalogCategoryService.PIM_01.EndpointURI

    2. Deployed Webservice - PIMWebServices-Item-WS

      Service: QueryItemListPIMAdapter

      Property: Routing.ItemService.PIM_01.EndpointURI

    3. Deployed Webservice - PIMWebServices-Item-WS

      Service: QueryBillOffMaterialsListPIMAdapter

      Property: Routing.ItemService.PIM_01.EndpointURI

15.5.2 Suppressing Auto-Retry and Preventing Multiple Error Notifications

To suppress auto-retry and prevent multiple error notifications:

  1. Set the GlobalTxMaxRetry property for outbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Click More SOA Infra Advanced Configuration Properties.

    5. Search for the GlobalTxMaxRetry property and set the value as 0 (zero).

  2. Set the GlobalInboundJcaRetryCount property for inbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select Administration, System Mbean Browser.

    4. Search for oracle.as.soainfra.config, expand <Server>, expand AdapterConfig.

    5. Select Adapter.

    6. Search for the GlobalInboundJcaRetryCount property and set the value as 0 (zero).

  3. Change Audit Level from Development to Production for soa infrastructure:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Choose Production from the Audit Level list.

    5. Click Apply.

  4. Stop and Start the SOA and Admin Server so that your changes can take effect.

15.6 Verifying Deployment

To verify the MDM Product Base Pack deployment:

  1. Open the log files from the following location and look for warnings and error messages:

    • For Linux x86, Solaris SPARC (64-bit), HP-UX 11i (64 bit) and IBM AIX Based Systems (64-bit): Review the install log located at <AIA_HOME>/aia_instances/<instance name>/logs to verify whether the integration is successfully installed.

    • For Microsoft Windows (32-bit): Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify whether the integration is successfully installed.

  2. Confirm that the MDM Product Base Pack components were successfully installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • QueryBillOffMaterialsListPIMAdapter

    • QueryItemListPIMAdapter

    • SyncItemCatalogCategoryPIMEventConsumer

    • SyncItemCatalogCategoryPIMReqABCSImpl

    • SyncItemListPIMEventConsumer

    • SyncItemListPIMReqABCSImpl

    • SyncSpecificationValueSetListPIMEventConsumer

    • SyncSpecificaitonValueSetListPIMReqABCSImpl

For more information about the DVMs to be verified, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.

15.6.1 Validating Security Policies

All SOA composites are protected by Global Policies provided by Foundation Pack as defined in the Security section of the Developer Guide. Additionally individual services for this integration have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen and find the client policy

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 15-5 Saml Opt On Client Policy Attachments for MDM Product Base Pack

      Composite Reference Client Policy

      SyncItemListPIMReqABCSImpl

      PublicationService

      oracle/wss_username_token_client_policy

      SyncItemListPIMReqABCSImpl

      GetListofTargetSystems

      oracle/wss_username_token_client_policy

      SyncItemCatalogCategoryPIMReqABCSImpl

      ItemCatalogService

      oracle/wss_username_token_client_policy

      SyncItemCatalogCategoryPIMReqABCSImpl

      PublicationService

      oracle/wss_username_token_client_policy


For integration implementation, see Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.

15.6.2 Validating User Credentials for PublicationService

To validate user credentials for PublicationService, perform these steps:

  1. Login to EM console: http://<hostname>:<port>/em

  2. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the requestor. For example, SyncItemCatalogCategoryPIMReqABCSImpl.

  3. In the Dashboard tab, scroll down to Services and References.

  4. Select PublicationService, and then navigate to Policies tab.

  5. Under Directly Attached Policies, select oracle/wss_username_token_client_policy.

  6. Under Security Configuration Details, note the current value of csf-key. For example, PIMServicesKey.

  7. Navigate to Farm_soa_domainWebLogic Domain, right-click soa_domain, select Security--> Credentials and expand <xxx>.wsm.security.

  8. Select and edit the csf-key. Update the key with appropriate username/password.

    Note:

    The user credentials must match the PH4C development manager responsibility credentials.

  9. Click OK to save it.

  10. Restart the soa_domain and re-test the flow.

15.7 Undeploying the MDM Product Base Pack

To undeploy the integration from Fusion Middleware Server:

  1. 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.

  2. Run the command for your platform.

    Table 15-6 Undeployment Command for the Product MDM Base Pack

    Platform Undeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/pips/MDMProductPIM/DeploymentPlans/undeployPIM.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\MDMProductPIM\DeploymentPlans\undeployPIM.bat
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".