Deploying Oracle Service Bus Adapters with DataRaker
This section describes steps to deploy Oracle Service Bus (OSB) with Dataraker functionality.
Note: Replace <adapter> in the commands below with the respective adapter name i.e (LG, D4, MV90, D6, D7, D8, DG).
1. Run the following commands:
UNIX
cd $SPLEBASE/osbapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy- osb_<adapter>.xml -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Ddeploy.dataraker=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
Note: Use the following command if this is an upgrade from a previous version:
cd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy- osb_<adapter>.xml
update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Ddeploy.dataraker=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
This will not override any OSB custom changes.
Windows
cd %SPLEBASE%\osbapp
 
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_<adapter>.xml -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Ddeploy.dataraker=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
Note: Use the following command if this is an upgrade from a previous version:
cd %SPLEBASE%/osbapp
%SPLEBASE%/product/apache-ant/bin/ant -buildfile deploy- osb_<adapter>.xml
update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Ddeploy.dataraker=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
This will not override any OSB custom changes
2. For SSL deployment of OSB adapters with DataRaker functionality, please refer Deploying OSB adapters on SSL with argument.
Below is an example command for Linux with Custom trust store:
cd $SPLEBASE/osbapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy- osb_<adapter>.xml -Dadmin.user=<ADMIN_USER>
-Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER>
-Douaf.password=<JMS_PASSWORD> - Dosb.keystore.passphrase=<passphrase_of_truststore_for_osb_deployment> - Ddeploy.dataraker=true
 
3. For Dataraker messages to pass through SSL, open SB console of OSB.
4. Select the DataRakerBusinessService under each of the adapter specific CM project
5. Create an OSB session by clicking on the “Create” button on top-left of the screen
6. Navigate to Transport Detail in the Business Service Definition.
7. Select Enable SSL under Advanced Options.
8. Click Save in the Business Service definition tab.
9. Click Activate.
10. Configure a queue on the SOA server for DataRaker functionality.
11. Create the following JMS queues:
Queue Name: DataRakerQueue
JNDI Name: DataRakerQueue
Sub-deployment: SOASubDeployment
Targets: SOAJMSServer