This chapter describes tasks to perform after installing, configuring, and deploying Oracle Application Integration Architecture (Oracle AIA) pre-built integrations.
After installing Oracle AIA and configuring and deploying the pre-built integrations, you must perform different post-installation tasks depending on the pre-built integrations that you deployed.
Some tasks are required for more than one pre-built integration. Table 6-1 lists the tasks required for each pre-built integration.
Table 6-1 Post-Installation Tasks for Pre-Built Integrations
| Pre-Built Integration | Post-Installation Tasks |
|---|---|
|
Order to Cash |
Post-Installation Tasks for All Pre-Built Integrations If you are using Siebel CRM: |
|
Agent Assisted Billing Care |
Post-Installation Tasks for All Pre-Built Integrations Enabling UTC Date Format in Siebel CRM Configuring Session Pool Manager Agent Assisted Billing Care Post-Installation Tasks If Agent Assisted Billing Care is co-deployed with Order to Cash: |
The tasks described in "Development Post-Installation Tasks" are not required immediately after installation, but you may need to perform them while customizing your deployment and environment.
The post-installation tasks described in this section are required for all pre-built integrations.
Before you can use JDeveloper to customize Oracle AIA content, you must import the Oracle AIA XPath functions into the JDeveloper library.
To import the Oracle AIA XPath functions:
Open JDeveloper.
From the Tools menu, select Preferences.
The Preferences screen appears.
Select the SOA node.
The SOA Expression Builder appears.
Click Add.
Select the MW_home/soa/aiafp/lib/aia.jar file and click Open.
The Oracle AIA library, including the Oracle AIA XPath functions, are added.
Save and close the file.
To customize Oracle AIA processes:
Copy the Oracle AIA composites and .jpr project files from Comms_home to the JDeveloper workspace.
Modify the composites as required for your environment.
Review your changes and copy the contents back to the Oracle AIA home directory in the same folder where you copied it from.
This ensures that the modified code is made available to subsequent deployments in other environments.
Deploy the composites using the AIA PIP deployment scripts.
For information about developing and deploying applications using JDeveloper, see Oracle Fusion Middleware Developing Applications with Oracle JDeveloper.
Note:
If you are maintaining source control for Comms_home contents, you must check the composites in to version control after copying them over to the Comms_home directory.
To set up Oracle AIA users and groups in Oracle WebLogic Server:
Log in to the WebLogic Server Administration Console.
Create an AIAApplicationUser group.
Users in this group can access the Composite Application Validation System (CAVS). This group corresponds to a role in JDeveloper.
Add the AIAApplicationUser group to the Administrators.
Create and add users as needed to the newly-created group.
Create an AIAIntegrationAdmin user.
This user is for configuring email notification for Oracle AIA errors.
See the WebLogic Server Administration Console help for information about creating groups, adding groups to other groups, creating users, and adding users to groups.
To suppress auto-retry and prevent multiple error notifications and trouble tickets:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
In the Target Navigation pane, expand the SOA folder.
Right-click soa_infra.
Select SOA Administration, then select Common Properties.
Click More SOA Infra Advanced Configuration Properties.
Search for the GlobalTxMaxRetry property and set the value to 0 (zero).
Click Apply.
In the Target Navigation pane, right-click soa_infra.
Select Administration, then select System Mbean Browser.
Expand oracle.as.soainfra.config, then expand the SOA managed server, then expand AdapterConfig.
Select Adapter.
Search for the GlobalInboundJcaRetryCount property and set the value to 0 (zero).
Click Apply.
In the Target Navigation pane, right-click soa_infra.
Select SOA Administration, then select Common Properties.
From the Audit Level list, select Production.
Click Apply.
Stop and Start the SOA server and the administration server as described in the discussion of controlling server state in Oracle Fusion Middleware Administering Oracle WebLogic Server with Fusion Middleware Control.
Configuring email notification for Oracle AIA involves the following tasks:
To updated the SOA workflow properties and messaging driver:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
In the Target Navigation pane, expand the SOA folder.
Right-click soa_infra.
Select SOA Administration, then select Workflow Properties.
From the Notification Mode menu, select Email.
In the Email: FromAddress field, do one of the following:
To use the default Oracle AIA sender address, enter AiaAdmin@server.com.
Enter a custom address.
Note:
If you enter a custom address, you must use the same custom address for the messaging driver as described below and update the value of the FROM.EMAIL.ID property in the AIAConfigurationProperties.xml file to the same custom address as described in "Updating Oracle AIA Configuration Properties".
Click Apply.
Click the Go to the Messaging Driver page link.
In the Associated Drivers region, in the row for the User Messaging Email Driver driver type, click the pencil icon in the Configure Driver column.
The Email Driver Properties page appears.
Click Create.
Do one of the following:
To use the default sender address (AiaAdmin@server.com), select the Use Sender Address option and leave the Sender Address field blank.
To use a custom sender address, select the Use Sender Address option and enter the same sender address as you entered in the Workflow Properties Email: FromAddress field.
Note:
If you use a custom address, you must also update the value of the FROM.EMAIL.ID property in the AIAConfigurationProperties.xml file to the custom address as described in "Updating Oracle AIA Configuration Properties".
Enter the required information for your environment, including outgoing mail server, port, and user credentials.
See the Enterprise Manager Fusion Middleware Control Help or the discussion of configuring Oracle User Messaging Service in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite for more information about the fields on this page.
In the Target Navigation pane, expand the User Messaging Service folder.
Restart the usermessagingdriver-email and usermessagingserver elements as follows:
Right click the element and select Control, then select Shut Down.
A confirmation window appears.
Click Shutdown.
Right click the element and select Control, then select Start Up.
Create the SOA User Messaging Preferences user and email channel as described in "Creating the SOA User Messaging Preferences Oracle AIA User and Email Channel".
To create the SOA User Messaging Preferences user and email channel:
As the AIAIntegrationAdmin user, log in to the SOA User Messaging Preferences console at the following location:
http://SOA_host:SOA_port/sdpmessaging/userprefs-ui
Create an email channel for the user who will receive Oracle AIA email notifications and make it the default. Use AIAIntegrationAdmin as the name.
See Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite for more information about creating a channel.
Update the Oracle AIA configuration properties as described in "Updating Oracle AIA Configuration Properties".
To update the Oracle AIA configuration properties for error notifications:
Download the AIAConfigurationProperties.xml file from the Oracle Metadata Services (MDS) repository, as described in "Downloading Files from the MDS Repository".
In the module configuration element for the ErrorHandler module, search for the following:
<Property name="EH.INVOKE.NOTIFY">
Set the value of the property to true. For example:
<Property name="EH.INVOKE.NOTIFY">true</Property>
If you used a custom sender address, do the following:
In the module configuration element for the ErrorHandler module, search for the following:
<Property name="FROM.EMAIL.ID">
Change the value of the property from Email:AiaAdmin@server.com to the custom sender address you used in Fusion Middleware Control, prefixed by Email:. For example:
<Property name="FROM.EMAIL.ID">Email:youremail@yoursite.com</Property>
Save and close the file.
Upload the changed AIAConfigurationProperties.xml file to the MDS repository as described in "Uploading Changed Files to the MDS Repository".
If you are reinstalling Oracle AIA, applying patches, or adding new pre-built integration options to an existing Oracle AIA deployment, you must reapply any backed up customizations with the new ready-to-use Oracle AIA objects.
Reapply any of the following customizations that you have backed up:
Extensible style sheet language transformations (XSLTs): Reapply any XSLTs that you have developed for custom integrations.
Enterprise Business Services (EBS) Web Service Definition Language (WSDL): Merge any EBS WSDL changes with the new ready-to-use EBS WSDLs.
Routing rules: Merge any EBS to which you added new routing rules with the new ready-to-use EBS.
The AIAConfigurationProperties.xml file: Add any custom additions and change any properties in the new ready-to-use file to match the backed up file and upload it to the MDS repository.
AIAConfigurationProperties.xml is located in the following directory:
Comms_home/source/soainfra/apps/config
The post-installation tasks described in this section are required for some pre-built integrations. See Table 6-1 for information about which tasks are required for which pre-built integrations.
You must configure Siebel CRM for the following pre-built integrations:
Order to Cash for Siebel CRM
Agent Assisted Billing Care
Configure Siebel CRM as described in the topic about configuring communications, Order to Cash, and Master Data Management integration in Siebel Communications Guide.
This includes:
Setting system preferences
Setting up integration users
Enabling component groups
Activating workflows
Configuring Oracle Advanced Queuing
Configuring Oracle Fusion Middleware URLs
Configuring Session Pool Manager
Specific tasks for Order to Cash
You must enable UTC date format in Siebel CRM for the following pre-built integrations:
Order to Cash for Siebel CRM
Agent Assisted Billing Care
You enable UTC date format by changing the value of the UTCCanonical process property to Y for workflows related to Oracle AIA. See the discussion of activating workflows for order to cash in Siebel Communications Guide for more information about changing this property, including the list of workflows for which it must be changed.
You must configure the Session Pool Manager utility for all pre-built integrations that involve Siebel CRM.
For information about configuring Session Pool Manager, see Oracle Communications Application Integration Architecture Utilities Guide.
Each pre-built integration is installed with its own set of routing rules for its enterprise business services.
The enterprise business services and their default routing rules are deployed when you deploy a single option or the Agent-Assisted Billing Care option with any of the Order to Cash options.
When you deploy multiple other options, such as any of the Order to Cash options, the enterprise business services and routing rules used by only one option are deployed, but the enterprise business services and routing rules used by more than one option are not deployed. You must manually configure the routing rules as appropriate for your combination of options.
The installation log provides information about any enterprise business services for which you must manually configure routing rules. For example, the log includes:
EBM_name is already deployed. The routing rules for PIP option_name have not been added. COMMS_HOME/pips/option_name/EBS contains Oracle Delivered EBS with routing rules for this PIP.
In the example, EBM_name is the name of the enterprise business message, option_name is the name of the pre-built integration option, and PIP is a pre-built integration option.
For more information about using routing rules, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Core Extension and Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
If you enabled multiple or split cross-reference tables when configuring the Agent Assisted Billing Care pre-built integration, you must create a view for the collections integration flow.
To create the view:
Navigate to the following directory:
Install_home/comms_home/bin
Run one of the following commands:
On UNIX:
source commsenv.sh
On Windows:
source commsenv.bat
This command sources the aiaenv script and sets the COMMS_HOME environment variable to Install_home/comms_home.
Navigate to the following directory:
Install_home/comms_home/pips/Communications/AABC/DeploymentPlans
Run one of the following commands:
On UNIX:
createMultiTableXREFViewForCollections.sh
On Windows:
ant -f %COMMS_HOME%\pips\Communications\AABC\DeploymentPlans\AABCDeploy.xml MultiTableXREFViewForCollections
Verify that the view was created in the log file. The following is the default log file:
domain_home/soa/aia/logs/AABC-MultiTableXREFViewForCollections_Deployments_timestamp.log
where timestamp is the date and time that the log was created.
This section describes the post-installation tasks for the Order to Cash pre-built integration.
If you are using the Order to Cash for Siebel CRM pre-built integration option, you must disabled the ENABLE_PRODUCT_ATTRIBUTE_VALIDATION model variable in the OSM Order to Activate cartridges.
See the discussion of enabling or disabling product attribute validation in Oracle Communications Order and Service Management Cartridge Guide for Oracle Application Integration Architecture for information about disabling this model variable.
For the Order to Cash for Siebel CRM, OSM, and BRM pre-built integration options, you must add the singleton property to the ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer service.
To add the singleton property:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
In the Target Navigation pane, expand the SOA folder, then soa-infra, then default.
Select the ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer link.
From the SOA Composite menu, select Services/Reference Properties, then select the Consume_PFOBAL service.
Select the Properties tab.
Click Add.
Click Search.
The Property Names dialog appears.
Select singleton.
In the Value column, enter true.
Click Apply.
For all Order to Cash pre-built integration options, you must configure the Oracle AIA queues to support prioritizing messages based on JMS Priority.
To configure the Oracle AIA queues to support JMS Priority:
Log in to the Oracle WebLogic Server Administration Control.
In the domain structure panel, expand Services, then Messaging, then JMS Modules.
Select AIAJMSModule.
In the Summary of Resources table, click New.
The Create New JMS System Module Resource page appears.
From the list of JMS resources, select Destination Sort Key.
Click Next.
The Destination Key Properties page appears.
In the Name field, enter AIA_SALESORDERJMSPRIORITY_KEY.
Click OK.
Click AIA_SALESORDERJMSPRIORITY_KEY link.
From the Sort Key list, select JMSPriority.
From the Key Type list, select Int.
From the Direction list, select Descending.
Click Save.
In the domain structure panel, click AIAJMSModule.
For each of the following queues:
AIA_CRTBO_OUT_JMSQ
AIA_CRTCUST_OUT_JMSQ
AIA_CRTFO_OUT_JMSQ
AIA_FOPROV_OUT_JMSQ
Do the following:
Click the queue name.
From Destination Keys section, select AIA_SALESORDERJMSPRIORITY_KEY.
Click Save.
For the Order to Cash for BRM pre-built integration option, update the BRM internal ID in the Oracle AIA Application Registry.
To update the BRM internal ID:
On the system where BRM is installed, navigate to the following folder:
./portal/7.4/sys/eai_js
Open the payloadconfig_crm_sync.xml file in a text editor.
Under the ProductInfoChange element, search for the following text:
Attribute Tag="InstanceId" Value=
Make note of the InstanceID value. For example:
Attribute Tag="InstanceId" Value="Portal"
In a web browser, navigate to the following page:
http://host:port/sce/faces/sceHomeLogin.jpsx
where host and port are the WebLogic Server host and port on which you deployed Oracle AIA.
In the Setup area, click Go.
Select the Systems tab.
In the Internal Id field, enter BRM_01.
Click Search.
In the table, change the value in the Internal Id column from BRM_01 to the value that you noted for InstanceId in the payloadconfig_crm_sync.xml file.
Click Save.
For the Order to Cash for OSM pre-built integration option, add the No Authentication security policy to either the QueryProductClassAndAttributesSCECommsReqABCSImpl or QueryProductClassAndAttributesSCECommsReqABCSImplV2 service, depending on your version of OSM.
To add the security policy:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
In the Target Navigation pane, expand the SOA folder, then soa-infra, then default.
Do one of the following:
If you are using OSM 7.3 or later, select the QueryProductClassAndAttributesSCECommsReqABCSImplV2 link.
If you are using an earlier version of OSM than 7.3, select the QueryProductClassAndAttributesSCECommsReqABCSImpl link.
In the Services and References region, do one of the following:
If you are using OSM 7.3 or later, select the QueryProductClassAndAttributesSCECommsReqABCSImplV2 link.
If you are using an earlier version of OSM than 7.3, select the QueryProductClassAndAttributesSCECommsReqABCSImpl link.
Click the Policies tab.
In the Directly Attached Policies region, click Attach/Detach.
In the Available Policies table, select oracle/no_authentication_service_policy.
Click Attach.
Click OK.
The oracle/no_authentication_service_policy appears in the Directly Attached Policies table.
Restart the administration server and all managed servers.
The Order to Cash pre-built integration includes a test orchestration process. You can run a sample order using the test orchestration process to test the integration between Siebel CRM and BRM if you are not using the Order to Cash for OSM pre-built integration option.
The test orchestration process cannot support a production system. After testing the integration, you must replace the test orchestration process with your order management system.
To replace the test orchestration process with your order management system:
Log on to Oracle Enterprise Manager Fusion Middleware Control.
In the Target Navigation pane, expand the SOA folder, then soa-infra, and then default.
For each of the following services: or the BillingResponseConsumer, CustomerResponseConsumer, OrderOrchestrationConsumer, and TestOrderOrchestrationEBF services:
BillingResponseConsumer
CustomerResponseConsumer
OrderOrchestrationConsumer
TestOrderOrchestrationEBF
Do the following:
Right click the service name.
Select SOA Deployment and then select Undeploy.
The Undeploy SOA Composite: Confirmation page appears.
Review the information on the page and click Undeploy.
Processing messages are displayed. When undeployment is complete, the SOA Infrastructure Deployed Composites page appears with a message at the top confirming that the composite has been undeployed.
Configure your order management system to interact with Oracle AIA through the JMS queues described in Table 6-2. You can see these queues in the WebLogic Server Administration Console under the AIAJMSModule in JMS Modules.
Table 6-2 Oracle AIA JMS Queues for Interactions with Custom Order Management Systems
| JMS Queues | Description |
|---|---|
|
jms/aia/AIA_CRTFO_IN_JMSQ |
This is the inbound queue from which your order management system picks up incoming sales orders from Siebel CRM. The sales order message is of type ProcessSalesOrderFulfillmentEBM and is wrapped into the SOAP envelope as follows: <tns:Envelope xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/"><tns:Body><crtfo:CreateOrder xmlns:crtfo="http://xmlns.oracle.com/communications/ordermanagement"><sord:ProcessSalesOrderFulfillmentEBM xmlns:sord="http://xmlns.oracle.com/EnterpriseObjects/Core/Custom/EBO/SalesOrder/V2">...</sord:ProcessSalesOrderFulfillmentEBM> </crtfo:CreateOrder></tns:Body></tns:Envelope> |
|
jms/aia/AIA_CRTCUST_OUT_JMSQ |
This is the outbound queue from your order management system for creating customers in BRM. The message must confirm to the ProcessFulfillmentOrderBillingAccountListEBM schema. Your order management system must wait for a response before continuing communication with BRM for the current order. |
|
jms/aia/AIA_UPDCUST_IN_JMSQ |
This is the response queue that corresponds to the jms/aia/AIA_CRTCUST_OUT_JMSQ queue. It contains the success response message from Oracle AIA in the ProcessFulfillmentOrderBillingAccountListResponseEBM schema. |
|
jms/aia/AIA_CRTBO_OUT_JMSQ |
This is the outbound queue from your order management system for creating billing orders in BRM. The message must confirm to the ProcessFulfillmentOrderBillingEBM schema. Your order management system must wait for a response before continuing communication with BRM for the current order. |
|
jms/aia/AIA_UPDBO_IN_JMSQ |
This is the response queue that corresponds to the jms/aia/AIA_CRTBO_OUT_JMSQ queue. It contains the success response message from Oracle AIA in the ProcessFulfillmentOrderBillingResponseEBM schema. |
|
jms/aia/AIA_UPDSO_OUT_JMSQ |
This is the outbound queue from your order management system for updating order information in Siebel CRM. The message must confirm to the UpdateSalesOrderEBM schema. This is an asynchronous flow, so no response is sent back to your order management system. |
By default, Siebel CRM allows unformatted phone numbers. To allow unformatted phone numbers in BRM, add the following phone number validation format by using the Field Validation Editor application in BRM Configuration Center:
###-###-####
See Oracle Communications Billing and Revenue Management Managing Customers and the Field Validation Editor Help for more information about validating phone number formats.
The tasks described in this section are not required immediately after installation, but you may need to perform them while customizing your deployment and environment.
You can optionally change the passwords that you specified in the Installer after completing installation using the UpdateStore utility.
This utility assumes that the AIAInstallProperties.xml file exists in the domain_home/soa/aia/bin directory and that the password being changed exists in the file.
Note:
This utility only changes encrypted passwords in the Oracle AIA installation. It does not change passwords of the SOA server or the database schemas.
To change passwords:
Navigate to the following directory:
Comms_home/bin
Run the following command:
source commsenv.sh
Navigate to the following directory:
MW_home/soa/aiafp/util
Run the following command:
ant -f updateStore.xml updateStore -DAdminUsername=weblogicadminuser -DAdminPassword=weblogicadminpassword
where weblogicadminuser and weblogicadminpassword are the user name and password for the WebLogic Server administration user.
The Update AIA Keystore screen appears.
Enter information in the following fields:
Existing Username: The user name for which you want to change credentials.
Existing Password: The password corresponding to the user name entered in the Existing Username field.
New Username: The new user name that you want to use. Use the same value as in Existing Username if you want to change the password only.
New Password: The new password that you want to use. Use the same value as in Existing Password if you want to change the user name only.
XPath: The XPath from the AIAInstallProperties.xml file to the password you want to change.
For example:
/properties/pips/o2c/password
Click OK.
A success message is displayed.
Upload the changed file to the MDS repository as described in "Uploading Changed Files to the MDS Repository".
To add Oracle AIA to a new node of an existing SOA cluster:
Add a new node to the SOA cluster as described in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.
Download the AIAConfigurationProperties.xml file from the MDS repository as described in "Downloading Files from the MDS Repository" and open it in an XML editor.
Search for the following text:
<Property name="EH.JNDIURL">t3://
After the existing list of SOA server details, add a comma and the host and port of the new node. In the following example, newnode.example.com:7003 has been added:
<Property name="EH.JNDIURL">t3://node1.example.com:7001,node2.example.com:7002,newnode.example.com:7003</Property>
Save and close the file.
Upload the changed file to the MDS repository as described in "Uploading Changed Files to the MDS Repository".
Open the Install_home/comms_home/config/AIAInstallProperties.xml file.
Search for the following element:
<properties>
<fp>
<server>
<jndiurl>
After the existing list of SOA server details, add a comma and the host and port of the new node. In the following example, newnode.example.com:7003 has been added:
<jndiurl>t3://node1.example.com:7001,node2.example.com:7002,newnode.example.com:7003</jndiurl>
Save and close the file.
Start the new Node.
Ignore any errors in the server log shows errors related to Foundation Pack.
Navigate to the following directory:
Install_home/comms_home/bin
Run the following command:
source commsenv.sh
Navigate to the following directory:
MW_home/soa/aiafp/Install/AID
Run the following command:
ant -f AIAInstallDriver.xml -DDeploymentPlan=MW_home/soa/aiafp/Install/config/FPAddNodeToClusterDP.xml -DPropertiesFile=domain_home/soa/aia/bin/AIAInstallProperties.xml
This section is for developers who customize installed composites. This is not a required post-installation task, but the you perform the procedure while customizing Oracle AIA composite services.
As part of your pre-built integrations implementation you may need to customize installed composites. For example, you may need to call different BRM opcodes than those specified in ready-to-use composites.
Customizations you make within customizable scopes in JDeveloper can be retained when upgrading Oracle AIA. The upgrade process overwrites any customizations you make outside of customizable scopes.
After upgrading, you can merge your customizations with the newly upgraded composites as described in "Migrating Custom Data".
To make upgrade-safe customizations to a deployed composite:
Open JDeveloper.
The Select Role dialog box appears.
Select Default Role and click OK.
From the Application menu, select New.
From the Application Template list, select SOA Application.
In the Application Name field, enter a name for the customized application.
Click Next.
In the Project Name field, enter the name of the BRM provider ABCS that you want to customize. For example, QueryInvoiceListBRMCommsProvABCSImpl.
On the Project Technologies tab, ensure that SOA appears in the Selected list.
Click Next.
From the Composite Template list, select Empty Composite.
Select the Customizable option.
Click Finish.
The project appears in the Projects section.
Expand the Application Resources section, then expand the Descriptors folder, and then the ADF META-INF folder.
Double-click the adf-config.xml element.
Click the MDS Configuration tab.
Next to Customization Configuration: Match Path = "/", click the plus sign.
The Edit Customization Class dialog box appears.
In the Match Class or Package Name field, enter the beginning of the name of the customization class that you want to use.
A list of matching customization classes appears.
Select the customization class that you want to use and click OK.
Select the newly-added class and click the Configure Design Time Customization Layer Values link.
The CustomizationLayerValues.xml file opens.
Add layer values for this customization layer. For example:
<cust-layer name="industry"> <cust-layer-value value="communications" display-name="Communications"/></cust-layer>
Click the Save All icon.
In the Projects section, select the top-level element. For example, QueryInvoiceListBRMCommsProvABCSImpl.
From the File menu, select Import.
Select SOA Archive Into SOA Project and click OK.
Click Browse.
Browse to the deploy directory under the directory where the BRM provider ABCS is copied from the Oracle AIA server. For example:
C:\DeployedFromServer\QueryInvoiceListBRMCommsProvABCSImpl\deploy
Select the JAR file associated with the provider ABCS and click Open.
Select the Import for Customization option and click Finish.
Click the Save All icon.
From the Tools menu, select Preferences.
In the navigation tree, select Roles.
Under Roles, select Customization Developer.
JDeveloper reopens in the new role.
In the Customization Context section, select the customization context that matches the layer values for the customization class you added earlier.
In the Project section, expand the top-level element.
Double-click the BPEL file for your composite.
The composite opens in Design mode.
Locate and expand the customizable scope where you want to make a customization.
Perform the customizations you require inside the customizable scope.
For example, to invoke a custom opcode, do the following:
Open the AIAConfigurationProperties.xml file, located in the Comms_home/source/soainfra/apps/config directory.
Under the entry for the service that you have customized, add a new property for invoking the custom opcode and set it to true. For example:
<Property name="Routing.BRMARServices.RouteToCustOp">true</Property>
In JDeveloper, in the BPEL file for the composite that you are customizing, create a partner link to represent the custom opcode.
In the switch that invokes the default BRM opcode or CAVS, add a new case with an expression linking it to the property for invoking the custom opcode.
For example, if you stored the property from AIAConfigurationProperties.xml in a variable in the composite's BPEL file, the expression might be as follows:
bpws:getVariableData('BRMARRouteToCustOp')
Within the new case, add a transform activity to transform the incoming message to the input field list (flist) of the custom opcode.
After the transform activity, add an invoke activity to invoke the partner link representing the custom opcode.
After the invoke activity, add a transform activity to transform the output flist of the custom opcode into the expected EBM that would be generated by the default opcode.
If the custom opcode output flist includes any attributes that are not present in the default opcode, extend the default EBM to include the attributes, and customize the PostXformEBMtoABM extension point with a transform or an assign activity to map the attribute values.
Click the Save All icon.
Redeploy the custom composite using JDeveloper or a deployment plan.
For more information about customizing and developing Oracle AIA composites, see the following documents:
For information about customizing BPEL processes, including customization classes, layer values, transform and invoke activities, scopes, switches, and partner links, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
For information about designing and constructing Oracle AIA artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Core Extension.
For information about deploying applications using JDeveloper, see Oracle Fusion Middleware User's Guide for Oracle JDeveloper.
When you modify a file stored in the MDS repository, you must upload the new version to the MDS repository for the modifications to take effect.
Additionally, before you modify the AIAConfigurationProperties.xml file, you must download the latest version from the MDS repository.
To download a file from the MDS repository:
Navigate to the following directory:
Install_home/comms_home/bin
Run the following command:
source commsenv.sh
Navigate to the following directory:
domain_home/soa/aia/MDSUtils
Open the DownloadMetaDataFileDP.xml file.
In the DownloadMetadataFile element, specify the following:
downloadLocation: The directory on your system where you want to temporarily store the file.
fileToDownload: The the path in the MDS repository to the file you want to download.
wlserver: The name of the WebLogic server where Oracle AIA is deployed.
For example:
<DownloadMetadataFile downloadLocation="/private/myhome" fileToDownload ="/soa/configuration/default/AIAConfigurationProperties.xml" wlserver="fp" />
Save and close the file.
Run the following command:
ant -f MW_home/soa/aiafp/Install/AID/UpdateMetaData.xml -DdeploymentPlan=domain_home/soa/aia/MDSUtils/DownloadMetadataFileDP.xml -DPropertiesFile=domain_home/soa/aia/bin/AIAInstallProperties.xml
The file is downloaded to the local directory.
To upload changed files to the MDS repository:
Navigate to the following directory:
Install_home/comms_home/bin
Run the following command:
source commsenv.sh
Navigate to the following directory:
domain_home/soa/aia/MDSUtils
Do one of the following:
To upload a file from a local directory, open the UpdateMetaDataFileDP.xml file and, in the UpdateMetaDataFile element, specify the following:
wlserver: The name of the WebLogic server where Oracle AIA is deployed.
mdslocation: The location in MDS where the file should be uploaded.
fileset dir: The directory on your system where the changed file is stored.
include name: The name of the file to include, relative to the value of fileset dir. To upload all files in a directory, finish the file path with /**.
To upload a file from an MDS-related path, open the UpdateMetaDataDP.xml file and, in the UpdateMetaData element, specify the following:
wlserver: The name of the WebLogic server where Oracle AIA is deployed.
fileset dir: The MDS-related directory where the changed file is stored.
include name: The name of the file to include, relative to the value of fileset dir. To upload all files in a directory, finish the file path with /**.
To upload an archive file, open the UploadMarDP.xml file and, in the UploadMAR element, specify the following:
marlocation: The directory where the archive file is stored.
wlserver: The name of the WebLogic server where Oracle AIA is deployed.
For example, to include the AIAConfigurationProperties.xml file stored in a local directory:
<UpdateMetadata wlserver="fp" mdslocation="soa/configuration/default/"> <fileset dir="/private/myhome"> <include name="AIAConfigurationProperties.xml" /> </fileset> </UpdateMetadata>
Or to upload all files in the /private/myhome directory:
<UpdateMetadata wlserver="fp"> <fileset dir="/private/myhome"> <include name="/**" /> </fileset> </UpdateMetadata>
Save and close the file.
Run the following command:
ant -f MW_home/soa/aiafp/Install/AID/UpdateMetaData.xml -DdeploymentPlan=domain_home/soa/aia/MDSUtils/deployment_plan.xml -DPropertiesFile=domain_home/soa/aia/bin/AIAInstallProperties.xml
where deployment_plan is UpdateMetaDataFileDP, UpdateMetaDataDP, or UpdateMarDP, depending on the location and type of file you are uploading.
The changed files are uploaded to the MDS repository.
If you did not select the Enable XREF split utility option while configuring Oracle AIA, you can split your cross reference tables after installation.
To maintain performance levels when looking up values in large cross reference tables, Oracle recommends splitting cross reference tables into multiple tables, with one table for each cross-reference object.
For details about how to split cross reference tables, see the information about the XREF Migration Utility on the following Oracle Technology Network web site:
http://www.oracle.com/technetwork/middleware/foundation-pack/learnmore/aiaxref-524690.html