Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.2 Part Number E26495-05 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy Oracle Product Master Data Management Integration Option for Siebel CRM (Product MDM: Siebel CRM).
This chapter includes the following sections:
Section 16.3, "Overall Configuration and Deployment of MDM Product Integrations"
Section 16.4, "Configuring and Deploying Product MDM: Siebel CRM"
The DCW screens prompt you to enter the data required for successful configuration of Product MDM: Siebel CRM. Enter the details of Product MDM: Siebel CRM 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 integration server. This screen contains the following fields:
Table 16-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: 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: 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 Admin 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. |
Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:
Table 16-2 Siebel CRM Server Details Screen Fields
Field | Description |
---|---|
Siebel HTTP Host name |
This is a computer name of the Siebel host. For example: Siebel HTTP Host name is _____________________________ |
Siebel HTTP Port |
This value is the Siebel application port. For example: Siebel HTTP Port is ________________________________ |
Siebel Internet Protocol |
Specifies the Siebel host internet protocol. For example: http://. Siebel host internet protocol is _____________________________ |
Siebel EAI Application User |
The Siebel application user is used for making EAI web service calls. For example: Siebel EAI Application User is ___________________________ |
Siebel EAI Application Password |
This is the password for the EAI user. For example: Siebel EAI Application Password is ________________________ |
Siebel Enterprise Server Name |
This is the Siebel server name. For example: Siebel Enterprise Server Name is __________________________ |
Siebel Version |
This is the version of the Siebel CRM application. |
Siebel Language |
This is the language used by the Siebel application. For example, enu. Siebel Language is ________________________ |
Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:
Table 16-3 Siebel CRM Database Details Screen Fields
Field | Description |
---|---|
Siebel Database Host |
This value is typically the computer name. For example: Siebel Database Host is _________________________________ |
Siebel Database Port |
This is the Siebel database port. For example: Siebel Database Port is _________________________________ |
Siebel Database Username |
Specifies a database user that has access to loading the EIM tables Siebel. To find this value, contact the database administrator. Example: Siebel Database Username is ______________________ |
Siebel Database Password |
This is the Siebel Database Password. For example: Siebel Database Password is _____________________ |
Siebel Database SID |
This is the Siebel database system ID. For example: Siebel Database SID is ________________________________ |
The Session Pool Manager (SPM) details are optional and required only when your Siebel server is outside of the firewall. If all your servers are within the network, leave these fields blank.
In the java.net
application programming interface (API) used by SPM, proxies are supported through two system properties: http.proxyHost
and http.proxyPort
. They must be set to the proxy server and port respectively. This value is only set when ProxySettings_Enabled
is set to TRUE.
Table 16-4 Session Pool Manager Details Screen Fields
Field | Description |
---|---|
Proxy host url |
This determines the server to be set in the system properties for Proxy host url is ___________________________ |
Proxy port |
This determines the port to be set in the system properties for the Proxy port is ______________________________ |
Caution:
These fields are optional so leave the values blank. These values are required only if the Siebel server is outside of the firewall.
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 Customer integration can be configured and deployed by selecting any integration or integration combination. The configuration and deployment process consists of the following steps:
Configure and deploy the MDM Product component integrations. Section 16.4 discusses configuring and deploying the Product MDM: Siebel CRM. For detailed instructions on the other MDM Product integrations, see your specific integration chapters in Part I, "Configuring and Deploying Pre-Built Integrations" of this guide.
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.
This section discusses the integration configuration and deployment process. There are two steps:
Configure your integration using the 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 Product MDM: Siebel CRM. Keep the completed worksheets of Product MDM: Siebel CRM 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 Product MDM: Siebel CRM:
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 installation 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 Oracle Product Master Data Management Integration Option for Siebel CRM under Product Master Data Management Pre-Build Integration
Click Next
To specify integration server details:
Enter information related to your integration server in the Integration Server Details screen.
Click Next.
To specify Siebel CRM Server details:
Enter information about your Siebel CRM application in the Application Details - Siebel CRM screen.
Click Next.
To specify Siebel CRM Database details:
Enter information about your Siebel CRM database in the Siebel CRM Database Details screen.
Click Next.
To specify Session Pool Manager details:
Enter information related to your Session Pool Manager installation in the Session Pool Manager Details 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 integration. You can configure using the steps described in Section 16.4.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 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.
When the configuration process finishes without errors, click Next.
When 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:
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 16-5 Deployment Commands for Product MDM: Siebel CRM
Platform | Deployment Command |
---|---|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductSiebel/DeploymentPlans/deploySiebel.sh |
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductSiebel\DeploymentPlans\deploySiebel.bat |
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 integration 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 includes the postdeployment configurations required for the Product MDM: Siebel CRM.
This integration uses the Session Pool Manager utility. Configure Session Pool Manager after you install the integration. For information on how to configure Session Pool Manager for your integration environment and needs, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".
To update the Product.Source.PIP property value:
Edit the AIAConfigurationProperties.xml file located in <AIA_INSTANCE>/AIAMetaData/config.
Locate the Product.Source.PIP
property and change the value as follows:
From: <Property name="Product.Source.PIP">O2C</Property>
To: <Property name="Product.Source.PIP">MDM</Property>
In item sync with pricelists scenario, SyncItemListPIMReqABCS service waits for a response. The response from the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service is sent to the requester through CommunicationsPriceListResponseEBSV2. Therefore, after you deploy the Siebel CRM services, you must update the following integration services:
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl
SyncItemCompositionListSiebelCommsProvABCSImpl
To update the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl service:
Edit the AIAConfigurationProperties.xml file that is located in <AIA_INSTANCE>/AIAMetaData/config.
Ensure that the following properties are listed in the AIAConfigurationProperties.xml file:
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.SyncPriceListListResponse.Address">http://HOST_NAME:PORT_NAME/soa-infra/services/default/CommunicationsPriceListResponseEBSV2/CommunicationsPriceListResponseEBSV2_ep</Property>
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.SyncPriceListListResponse.PortType">{http://xmlns.oracle.com/EnterpriseServices/Core/PriceList/V2}CommunicationsPriceListResponse</Property>
<Property name="EBSOverride.CommunicationsPriceListResponseEBS.SyncPriceListListResponse.ServiceName">{http://xmlns.oracle.com/EnterpriseServices/Core/PriceList/V2}CommunicationsPriceListResponse</Property>
To update the SyncItemCompositionListSiebelCommsProvABCSImpl service:
Edit the AIAConfigurationProperties.xml file that is located in <AIA_INSTANCE>/AIAMetaData/config.
Ensure that the following properties are listed in the AIAConfigurationProperties.xml file:
<Property name="EBSOverride.CommunicationsItemCompositionResponseEBSV1.SyncItemCompositionListResponse.Address">http://HOST_NAME:PORT_NAME/soa-infra/services/default/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
<Property name="EBSOverride.CommunicationsItemCompositionResponseEBSV1.SyncItemCompositionListResponse.PortType">{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/V1}ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
<Property name="EBSOverride.CommunicationsItemCompositionResponseEBSV1.SyncItemCompositionListResponse.ServiceName">{http://xmlns.oracle.com/ABCSImpl/Siebel/Industry/Comms/ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl/V1}ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl</Property>
To verify the Product MDM: Siebel CRM deployment:
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.
Confirm that the Product MDM: Siebel CRM services were installed.
Navigate 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:
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl
SyncBillOfMaterialsListSiebelProvABCSImpl
SyncClassificationSchemeListSiebelProvABCSImpl
SyncItemCompositionListSiebelCommsProvABCSImpl
SyncProductSiebelProvABCSImpl
SyncSpecificationValueSetListSiebelProvABCSImpl
For more information about the DVMs to be verified, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.
Verify whether Session Pool Manager is successfully installed and ensure that the Siebel server is active.
Log in to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).
Expand Farm_soa_domain, SOA, soa-infra (soa_server1), Default and click AIASessionPoolManager on the left panel.
Click Test.
Enter Operation = Start
.
Under the collapsible section titled Security, select WSS Username Token and enter the WLS admin user name and password.
Enter Input Argumemt Host Id = SEBL_01
.
Click Test Web Service.
You should see a successful initialization response message. For more information and troubleshooting steps, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".
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:
Log in to Oracle Enterprise Manager Fusion Middleware Control
Navigate to WebLogic Domain, soa_domain, Web Services, Policies.
Verify Service Policy attachment.
Find the service policy in the list of policies.
Click the number in Attachment Count column.
This opens Usage Analysis screen.
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 Policies screen and find the client policy
Click the number in Attachment Count column.
This opens Usage Analysis screen.
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 16-6 Service Policy Attachments for Product MDM Siebel CRM
Composite | Service Policy |
---|---|
ReloadProcess |
oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON |
AIAB2BInterface |
oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON |
AIAErrorTaskAdministrationProcess |
oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON |
AIASessionPoolManager |
oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON |
Table 16-7 No Authentication Service Policy Attachments for Product MDM Siebel CRM
Composite | Service Policy |
---|---|
SyncClassificationSchemeListSiebelProvABCSImpl |
oracle/no_authentication_client_policy |
SyncSpecificationValueSetListSiebelProvABCSImpl |
oracle/no_authentication_client_policy |
SyncBillOfMaterialsListSiebelProvABCSImpl |
oracle/no_authentication_client_policy |
SyncItemCompositionListSiebelCommsProvABCSImpl |
oracle/no_authentication_client_policy |
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl |
oracle/no_authentication_client_policy |
SyncProductSiebelProvABCSImpl |
oracle/no_authentication_client_policy |
Table 16-8 Saml Opt On Client Policy Attachments for Product MDM Siebel CRM
Composite | Reference | Client Policy |
---|---|---|
AIAB2BInterface |
X12ProcessSalesOrderReqB2BCSImplService |
oracle/aia_wss10_saml_token_client_policy_OPT_ON |
AIAReadJMSNotificationProcess |
AIAErrorTaskAdministrationProcess |
oracle/aia_wss10_saml_token_client_policy_OPT_ON |
For integration implementation, see Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.
To undeploy the integration 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 command for your platform.
Table 16-9 Undeployment Command for Product MDM: Siebel CRM
Platform | Undeployment Command |
---|---|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductSiebel/DeploymentPlans/undeploySiebel.sh |
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductSiebel\DeploymentPlans\undeploySiebel.bat |
Restart the SOA server.
Uninstall the integration following the instructions in Chapter 39, "Uninstalling Oracle AIA".