1. Get the following JAR files:
   • From Siebel containers, get siebel.jar and SiebelJI_enu.jar.
   • From the WebLogic container, get wlthint3client.jar.
2. Log in to Siebel eCommunication Web UI as SADMIN user and update the JAVA64 profile parameters to include the three JAR files:

   Note:

   Ensure that the path /sfs/aiacn/jms is a persistent store so that the files are retained after the pod restarts.

   /sfs/aiacn/jms:/sfs/aiacn/jms/Siebel.jar:/sfs/aiacn/jms/SiebelJI_enu.jar:/sfs/aiacn/jms/wlthint3client.jar:.

3. Relocate the JAR files:
   1. Connect to the Siebel SES pod.
   2. Create a folder with the same name as what is listed in step 2 (/sfs/aiacn/jms), where /sfs is a shared persistent folder, and then copy the 3 JAR files into the folder.
4. In the same folder, create the jndi.properties file and copy the following text into it:

   Note:

   Ensure that the AIACN t3 channel URL and user name and password are set with the correct values.

   java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
   java.naming.provider.url=t3://soa_cluster_service_name.soa_namespace.svc.cluster.local:soa_service_cluster_port
   java.naming.security.principal=soa_console_username
   java.naming.security.credentials=soa_console_password

5. Copy the three JAR files into the Apache TOMCAT /siebel/mde/applicationcontainer/lib folder.
6. Restart Apache TOMCAT server inside Siebel SES pod.
7. Configure Siebel Web Service in Siebel DB.
   1. Create the "update_siebel_ws.sql" SQL script with the following content:

      UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISubmitOrderPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISubmitOrder_o2cPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SALESORDERJMSQUEUE@jms/aia/COMMS_SUBMITORDER_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISubmitQuote_o2cPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_SPECIALRATINGJMSQ@jms/aia/COMMS_SPECIALRATINGLIST_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWISpecialRatingListPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='jms://jms/aia/AIA_CMUREQADJIOJMSQUEUE@jms/aia/COMMS_ADJUSTMENT_CONSUMER', PORT_TRANSPORT='JMS' WHERE NAME='SWICreateAdjustmentPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/AccountBalanceSiebelCommsReqABCS/AccountBalanceSiebelCommsReqABCS_ep' WHERE NAME='_soap_AccountBalanceSiebelCommsReqABCS_AccountBalanceSiebelCommsReqABCS';
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/AdjustmentSiebelCommsReqABCS/AdjustmentSiebelCommsReqABCS_ep' WHERE NAME='AdjustmentSiebelCommsReqABCSPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/InvoiceSiebelCommsReqABCS/InvoiceSiebelCommsReqABCS_ep' WHERE NAME='_soap_InvoiceSiebelCommsReqABCS_InvoiceSiebelCommsReqABCS';
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/PaymentSiebelCommsReqABCS/PaymentSiebelCommsReqABCS_ep' WHERE NAME='PaymentSiebelCommsReqABCSPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/UnbilledUsageSiebelCommsReqABCS/UnbilledUsageSiebelCommsReqABCS_ep' WHERE NAME='_soap_UnbilledUsageSiebelCommsReqABCS_UnbilledUsageSiebelCommsReqABCS';
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/SyncCustomerSiebelEventAggregator/Client' WHERE NAME='SyncCustomerSiebelEventAggregatorPort'; 
      UPDATE S_WS_PORT SET PORT_ADDRESS='http://aiacn_hostname:port/soa-infra2/services/default/UpdateCreditAlertSiebelCommsReqABCSImpl/UpdateCreditAlertSiebelCommsReqABCSImpl' WHERE NAME='UpdateCreditAlertSiebelCommsReqABCSImplServicePort';
      SET ESCAPE ON; 
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIOrderUpsert';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWI Product Attribute Import';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWI Product Class Import';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIProductImport';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIPromotionImport';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/eai/enu/start.swe?SWEExtSource=SecureWebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='SWIUpsertQuote';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSCancelOrderPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSCustomServicesPort';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSOrderUpsert';
      UPDATE S_WS_PORT SET PORT_ADDRESS='https://Siebel_hostname:Siebel_port/siebel/app/eai/enu?SWEExtSource=WebService\&SWEExtCmd=Execute\&WSSOAP=1' WHERE NAME='COMMSSubmitBillingOrder';
      commit;
      quit;

   2. Connect to Siebel DB and run the SQL script with DB user name and the corresponding password.
8. Configure the Siebel repository in Siebel DB:
   1. Create the "update_siebel_repository.sql" SQL script with the following contents:

      UPDATE S_SYS_PREF SET VAL='TRUE' WHERE SYS_PREF_CD='Enable AIA Comms';
      UPDATE S_SYS_PREF SET VAL='TRUE' WHERE SYS_PREF_CD='Enable AIA MDM';
      UPDATE S_SYS_PREF SET VAL='TRUE' WHERE SYS_PREF_CD='Enable AIA Testing';
      UPDATE S_SYS_PREF SET VAL='FALSE' WHERE SYS_PREF_CD='Enable AIA Utility';
      UPDATE S_SYS_PREF SET VAL='No' WHERE SYS_PREF_CD='Enable Promotion Group';
      UPDATE S_SYS_PREF SET VAL='/siebel/mde/siebsrvr/temp/OrderBackup/' WHERE SYS_PREF_CD='AIA Order Backup Path';
      UPDATE S_SYS_PREF SET VAL='Yes' WHERE SYS_PREF_CD='Enable Promotion Group';
      UPDATE S_SYS_PREF SET VAL='Y' WHERE SYS_PREF_CD='Promotion Group Compatibility';
      commit;
      quit;

   2. Connect to Siebel DB and run the SQL script with DB user name and the corresponding password.
9. Configure EAI File Transfer Folder:
   1. Connect to the SES pod of the Siebel cloud native instance.
   2. Run the following two Siebel commands respectively and set "EAIFileTransportFolders" with the created "OrderBackup" sub-folder's full path as follows:

      [aiacn_pod-0:/siebel/mde]#srvrmgr /g cgw-aiacn-0.ses-aiacn.siebel-cn.svc.cluster.local:2320 /e aiacn /u username /p password /c "change ent param EAIFileTransportFolders=/siebel/mde/siebsrvr/temp/OrderBackup"

      srvrmgr> change ent param EAIFileTransportFolders=/siebel/mde/siebsrvr/temp/OrderBackup

      srvrmgr> change ent param EAIFileTransportFolders=/siebel/mde/siebsrvr/temp/OrderBackup for server aiacn_pod-0

   3. Restart the SES service using the kubectl command:

      kubectl -n siebel_namespace, delete pod Siebel_Enterprise_Server_pod_name-0

   4. After the pod is recreated and verified that it is running, do steps 5 and 6.
10. (Optional) Import products into Siebel cloud native by using the Siebel eCommunication application. Refer to Siebel CRM documentation for instructions.
11. Import Siebel cloud native SSL/TLS security certificates and configure AIA cloud native with the certificates. See "Installing SSL Certificates".
    1. Validate that keystore custom identity and custom trust are created successfully. To do this, log in to the Enterprise Manager Console for AIA and navigate to the Keystore section.
    2. Validate that Siebel trust certificate is available in the custom trust keystore in the Keystore section.
    3. Log in to the Weblogic Console of AIA cloud native. For each managed server, in the Keystore section, ensure the following:
       • kss://system/custom_identity_keystorename is displayed for Custom Identity Store.
       • kss://system/custom_trust_keystorename is displayed for Custom Trust Store.
    4. Validate /u01/oracle/user_projects/domains/soainfra/bin/setDomainEnv.sh with custom trust:
       1. Connect to any managed server pod.
       2. Open the /u01/oracle/user_projects/domains/soainfra/bin/setDomainEnv.sh using the vi tool.
       3. Validate that -Djavax.net.ssl.trustStore=kss://system/custom_trust_keystorename -Djavax.net.ssl.trustStoreType=kss -Djavax.net.ssl.keyStorePassword=password" is configured in EXTRA_JAVA_PROPERTIES.
12. Configure Siebel credentials in the Enterprise Console of AIA cloud native.
    1. Navigate to the Credentials section and edit participatingapplications.siebel.server.eai.password to specify the username and password.
    2. Repeat step a. for participatingapplications.siebel.server.db.password if you want to change the Siebel DB credentials.
    3. Restart the AIA cloud native services by using the domain-lifecycle scripts.
13. Configure AIA cloud native MetaData with Siebel Business Unit ID, and PRICELIST.
    1. Log in to Siebel and get Siebel Business Unit Id by navigating to Organizations. Navigate to About Record, copy Row #, and update the AIAConfigurationProperties.xml file with it.
    2. If not already available, create a pricelist.
    3. Search for the pricelist you created.
    4. Update AIAConfigurationProperties.xml and PRICELIST.dvm for Default Pricelist.
    5. Repeat steps from b. to d. for Business Pricelist and Consumer Pricelist.
    6. Search for the Pricelist and get Row # if available. Navigate to All Price Lists, select the row that contains NA Pricelist, and copy the Row # from About Record.
    7. Update AIAConfigurationProperties.xml and PRICELIST.dvm for Default Pricelist.
    8. Repeat steps from f. and g. for Business Pricelist and Consumer Pricelist.
    9. Log in to Enterprise Manager console for AIA and update Siebel end points, Price List IDs, and Business Unit IDs:
       1. Get the latest AIAConfigurationProperties.xml and PRICElIST.dvm files.
       2. In Enterprise Manager console for AIA, navigate to the MDS Configuration section and export the zip file.
       3. Go to soa/configuration/default folder of your zip and copy the AIAConfigurationProperties.xml.
       4. Go to apps/AIAMetaData/dvm and copy PRICELIST.dvm.
       5. In the AIAConfigurationProperties.xml file, replace the Siebel URL and then save and close the file.
       6. Update MDS with the updated AIAConfigurationProperties.xml file and restart AIA cloud native using domain-lifecycle scripts.
    10. In the PRICElIST.dvm file, do the following:
        1. Update the value of <cell> element, which is immediately after DEFAULT Pricelist, with the copied Row # of NA Pricelist.
        2. Change the value of <cell> element, which is immediately after Consumer Pricelist, with the copied Row # of Consumer Pricelist.
        3. Change the value of <cell> element, which is immediately after Business Pricelist, with the copied Row # of Business Pricelist.
        4. Save and close the file.
        5. Open AIAConfigurationProperties.xml and search for XML tags property by the name Siebel.SEBL_01.PriceList.ID.
        6. Update all the values of Siebel.SEBL_01.PriceList.ID with the copied NA Pricelist Row #.
        7. Save and close the file.
    11. Update the Business Unit ID:
        1. In the AIAConfigurationProperties.xml file, search for XML tags property by the name Siebel.SEBL_01.BusinessUnit.
        2. Update all the values of Siebel.SEBL_01.BusinessUnit with the copied Default Organization Row #.
        3. Save and close the file.
    12. Update MDS with the updated PRICELIST.dvm and AIAConfigurationProperties.xml files.
        1. Copy the PRICELIST.dvm and AIAConfigurationProperties.xml files to a shared folder of AIA cloud native.
        2. Create a file with the name UpdateMetaDataDP.xml and add the following content:

           <?xml version="1.0" standalone="yes"?>
           <DeploymentPlan component="Metadata" version="3.0">
                   <Configurations>              
                           <UpdateMetadataFile wlserver="fp" mdslocation="soa/configuration/default/">
                                           <fileset dir="absolute_path_to_share_folder_where_the_files_are_copied"
                                           <include name="AIAConfigurationProperties.xml" />
                                   </fileset>
                           </UpdateMetadataFile>
                           <UpdateMetadataFile wlserver="fp" mdslocation="/apps/AIAMetaData/dvm">
                                   <fileset dir="absolute_path_to_share_folder_where_the_files_are_copied"
                                           <include name="PRICELIST.dvm" />
                                   </fileset>
                           </UpdateMetadataFile>
                   </Configurations>
           </DeploymentPlan>

        3. Connect to any SOA or AIA cloud native managed server pod and run following command:

           $ cd /u01/aiacn/comms_home/bin
           $ source ./commsenv.sh
           $ ant -f $MW_HOME/soa/aiafp/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=absolute_path_to_file_no_variables_please/UpdateMetaDataDP.xml -DPropertiesFile=$DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml

        4. Restart AIACN domain services by running the domain-lifecycle scripts.
14. Enable the eai_enu application configuration using the Siebel Management Console. Refer to the Siebel Management Console documentation for instructions.

1. Validate the BRM cloud native CM parameter by running the following command:

   Note:

   Ensure that the BRM CM service is configured with the dnsName of the cluster, so that the CM service can be connected using the dnsName in the cluster.

   kubectl -n brmcn_namespace get deployment/cm -o yaml

   A sample output is as follows:

   - name: CM_DNS_NAME
     value: dns:cm.brmcn-ps8

2. Deploy the BRM JCA Adapter by downloading Patch 35353279 from My Oracle Support and apply it.
   • In the extracted files, in the Oracle_BRMJCA_Adapter_RAR/META-INF directory, update the value for the ConnectionString parameter with the same value of CM_DNS_NAME of the CM service of BRM cloud native.
   • In the ra.xml and weblogic-ra.xml files, set the properties appropriately. For details, see "Deploying and Configuring JCA Resource Adapter on Oracle WebLogic Server" in the BRM JCA Resource Adapter guide. In addition to the parameters listed in the BRM JCA Resource Adapter guide, set the following parameters with appropriate values for a single cluster. The values shown are samples.
     • ConnectionString : "ip cm.brmcn-ps8 11960"
     • FailoverConnectionString : "root.0.0.0.1:password@cm.brmcn-ps8:11960"
     • UserName : "root.0.0.0.1"
     • Password : password
     • SslWalletLocation : "/u01/oracle/user_projects/domains/soainfra/servers/AdminServer/tmp/_WL_user/OracleBRMJCA15Adapter/wernpi/wallet"

       Note: In a multi-cluster scenario, set the values of ConnectionString and FailoverConnectionString as shown in the following samples:

     • ConnectionString : "ip 192.0.2.1 31773"
     • FailoverConnectionString : "root.0.0.0.1:password@192.0.2.1:31773,root.0.0.0.1:password@192.0.2.1:31773"
   • Download cwallet.sso file from the CM pod of the BRM cloud native instance and re-package ra.xml, weblogic-ra.xml and cwallet.sso into OracleBRMJCA15Adapter.rar.
   • Deploy OracleBRMJCA15Adapter.rar into AIA cloud native Weblogic cluster using the Weblogic Admin console and ensure that it is in the "Active" state.
3. (Optional) Validate the connection between AIA cloud native and BRM cloud native by deploying the BRM JCA Adapter test client (Web application) and sending a test request with the test client Web UI. For more details, see "Testing JCA Resource Adapter Configuration and BRM Connectivity" in the BRM JCA Resource Adapter guide.
4. Enable notification and Product Sync in BRM cloud native.
   1. Ensure that the fm_publish enable_publish parameter is set to 1 in the CM pin.conf.
   2. Ensure that eai-java-server in cm pod Infranet.properties file has the same payload as payloadconfig_crm_sync.xml. This payload contains the required events (ProductInfoChange and DiscountInfo change) for generating the XML for EAI. Ensure that the DB is 0.0.9.7, which points to EAI. The DB entries mapping can be found in dm-oracle pin.conf.
   3. Ensure that in the dm-aq config file, ALL queues are enabled.
   4. Ensure that notifications are enabled for the following:

      /event/notification/price/products/modify
      /event/notification/price/discounts/modify
      /event/notification/price/sponsorships/modify
      /event/customer/status
      /event/notification/amt/AccountInfoChange

   5. Restart the cm and dm-oracle, dm-aq and dm-ifw-sync pods of the BRM cloud native instance.

1. Create a t3 channel in the AIA cloud native instance:
   • For a single cluster scenario, where in AIA cloud native, Siebel CRM cloud native, BRM cloud native, and OSM cloud native are deployed in the same cluster, create a t3 channel in the WebLogic Admin Console for AIA cloud native.
     1. Log in to AIA cloud native Weblogic Console.
     2. Navigate to the Servers section in the Domain Structure pane and then select a managed server (for example, select soa_server1).
     3. Navigate to the Channels tab in Protocols and create a new channel (for example, T3Channel).
     4. Specify the following:
        • Listen Address as soainfra-cluster-soa-cluster.namespace.svc.cluster.local.
        • External Listen Port.
     5. Ensure that ‘Tunneling Enabled’ is selected.
     6. Repeat steps b. to e. for managed server soa_server2.
   • For multiple clusters, where in AIA cloud native and OSM cloud native are deployed in different clusters, do the following:
     1. Connect to the AIA cloud native cluster and create an ingressroute that includes route rules for all common names and the respective ports.

        apiVersion: traefik.containo.us/v1alpha1
        kind: IngressRoute
        metadata:
          name: aia-ingress
          namespace: namespace
        spec:
          entryPoints:
          - web
          routes:
          - kind: Rule
            match: Host(`soa.domain_name.namespace.aia.org`)
            services:
            - name: soa_cluster_service_name
              port: soa_ms_port
              sticky:
                cookie:
                  httpOnly: true
          - kind: Rule
            match: Host(`t3.domain_name.namespace.aia.org`)
            services:
            - name: soa_cluster_service_name  
              port: soa_cluster_service_port
              sticky:
                cookie:
                  httpOnly: true
          - kind: Rule
            match: Host(`admin.domain_name.namespace.aia.org`)
            services:
            - name: soa_admin_server_service_name
              port: soa_admin_server_port
              sticky:
                cookie:
                  httpOnly: true

     2. Apply the yaml file to create the ingressroute:

        kubectl apply -f aia-ingress.yaml

     3. Edit the AIA cloud native domain configuration to specify the following settings for integrating with the OSM cloud native instance:

        Note:

        If the previous node is cordoned, deleted, or repaved, update the values for hostAliases and change the IP addresses to new IP addresses of a working node.

        spec:
        .........
        .........
          serverPod:
        .........
        .........
            hostAliases:
            - hostnames:
              - t3.instance.project.osm.org
              - instance.project.osm.org
              - admin.instance.project.osm.org
              ip: osm_node_IP_address
            - hostnames:
              - soa.soainfra.soa_namespace.aia.org
              - t3.domain_name.namespace.aia.org
              - admin.domain_name.namespace.aia.org
              ip: soa_node_IP_address

     4. Edit the OSM cloud native domain configuration to specify the same settings as described in step 1.b for integrating with the AIA cloud native instance.

        Note:

        Ensure that the AIA cloud native and OSM cloud native instance pods restart automatically after steps b and c. If they do not, run the corresponding scripts to restart the AIA and OSM instances.
     5. Create a t3 channel in the WebLogic Admin Console for AIA cloud native, ensuring that the External Listen Address is set as the hostname defined earlier. In addition, ensure that the HTTP Enabled for This Protocol option is selected.
2. Deploy the O2A cartridge into the OSM cloud native instance. For instructions, see OSM Cloud Native Deployment Guide for Oracle Application Integration Architecture Cartridges and "Deploying the Sample Cartridge" in OSM Cloud Native Deployment Guide.
3. Set the AIA cloud native SAF t3 value, created earlier, in the OSM project specification file as follows:
   • For single cluster, specify the following:

     safConnectionConfig:
       - name: O2A_SAFImportedDestinations
         t3Url: t3://soa_cluster_servicename.namespace.svc.cluster.local:soa_cluster_serviceport
         secretName: osm_project_instance__saf_credentials_aia_secret_name

     Note:

     osm_project_instance__saf_credentials_aia_secret_name is the secret you created while setting up and deploying OSM.
   • For multiple clusters, specify the following:

     safConnectionConfig:
       - name: O2A_SAFImportedDestinations
         t3Url: http://t3_hostname_in_ingressroute:t3_port_created
         secretName: osm_project_instance__saf_credentials_aia_secret_name

4. Run the corresponding scripts to deploy the O2A cartridge with the AIA cloud native configuration:

   [opc@cn-deployment o2a_cartridge]$ ./shutdown_osm.sh ; ./deploy_o2a_par.sh ; ./start_osm.sh

5. Log in to the Weblogic Admin Console for OSM cloud native and verify that the SAF setting is configured with the expected t3 Url value.
6. Log in to the OSM Task Web client and verify that the O2A cartridge is deployed.
7. In WebLogic Admin Console for OSM cloud native, copy the t3 URL dispalyed for T3ClustChannel for single cluster or the value of T3Channel (HTTP) for multi-cluster channel.
8. In the WebLogic Admin console for AIA cloud native, navigate to the JMS Modules page, for the OSM and SOM AIAJMSModules, set the URL test fields with the copied t3 URLs.
9. Restart the AIA cloud native domain services by using the domain-lifecycle scripts.
10. In WebLogic Admin Console, navigate to the Store and Forward Agents page. In the Remote Endpoints tab for OSM_SAFAgent, ensure that for each Remote Endpoint, the t3 URL is displayed for single-cluster environment.
11. Log in to Oracle Enterprise Manager Fusion Middleware Control for AIA cloud native, add the singleton property. See the AIA Installation Guide for instructions.
12. Configure the AIA queues to support JMS Priority. See the AIA Installation Guide for instructions.
13. Add the No Authentication security policy to the Product class service. See the AIA Installation Guide for instructions. Ensure that you select "QueryProductClassAndAttributesSCECommsReqABCSImpl" in the Service and References region.
14. Ensure that the JAVA_OPTIONS parameter -Dweblogic.rjvm.allowUnknownHost=true is added into AIA cloud native domain setting.
15. In Oracle Enterprise Manager Fusion Middleware Control, for SOA Infrastructure, set the Callback Server URL and Server URL common properties with the SOA infrastructure URL.

• Main Deployment Plan
• Supplementary Deployment Plan
• Custom Deployment Plan

1. Main Deployment Plan
2. (Optional) Supplementary Deployment Plan
3. (Optional) Custom Deployment Plan

source $COMMS_AIA_HOME/comms_home/bin/commsenv.sh
ant -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml \
-DPropertiesFile=$VOLUME_DIR/domains/$DOMAIN_NAME/soa/aia/bin/AIAInstallProperties.xml \
-DDeploymentPlan=$COMMS_HOME/pips/PIP_name/DeploymentPlans/PIP_nameDP.xml  \
-DSupplementaryDeploymentPlan=$COMMS_HOME/pips/PIP_name/DeploymentPlans/PIP_nameSupplementaryDP.xml  \
-DDeploymentPolicyFile=$COMMS_HOME/pips/PIP_name/DeploymentPlans/PIP_nameConditionalPolicy.xml

source $COMMS_AIA_HOME/comms_home/bin/commsenv.sh
ant -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml \
-DPropertiesFile=$VOLUME_DIR/domains/$DOMAIN_NAME/soa/aia/bin/AIAInstallProperties.xml Uninstall \
-DDeploymentPlan=$COMMS_HOME/pips/PIP_name/DeploymentPlans/PIP_nameUndeployDP.xml

1. Copy the supplementary deployment plan and name it as PIP_NameUndeploySupplementaryDP.xml or PIP_NameUndeployCustomSupplementaryDP.xml, depending on the supplementary deployment plan name.
2. In the new deployment plan, change the action attributes of all the tasks from "deploy" to "undeploy" or from "create" to "delete".