Persist Adapter Customizations

Customizations made to files in a server pod last only for the lifetime of that pod. The changes are not persisted when the pod goes down or restarts.

For example, update DbAdapter.rar with the following configuration to create a new connection instance. Create the corresponding CoffeeShop data source in the WebLogic Remote Console with the JNDI name jdbc/CoffeeShopDS.

File location: /u01/oracle/soa/soa/connectors/DbAdapter.rar

<connection-instance>
            <jndi-name>eis/DB/CoffeeShop</jndi-name>
            <connection-properties>
            <properties>
            <property>
            <name>XADataSourceName</name>
            <value>jdbc/CoffeeShopDS</value>
            </property>
            <property>
            <name>DataSourceName</name>
            <value></value>
            </property>
            <property>
            <name>PlatformClassName</name>
            <value>org.eclipse.persistence.platform.database.Oracle10Platform</value>
            </property>
            </properties>
            </connection-properties>
            </connection-instance>
        

To persist customizations to adapter files under the SOA Oracle home in the server pod, use one of the following methods.

Method 1: Customize the adapter file using the WebLogic Remote Console

By default, Plan.xml is stored in ${ORACLE_HOME}/soa/soa, which is outside the persistent volume (PV).

  1. Sign in to the WebLogic Remote Console and update Outbound Connection Pools and Plan.xml. See Specify Deployment Properties.
  2. Set the location for Plan.xml to a path on the domain's PV, such as {DOMAIN_HOME}/soainfra/servers.

The Plan.xml file is persisted at this location for each managed server.

Method 2: Customize the adapter file on the worker node

  1. Copy ABC.rar from the server pod to a path on the PV:

    kubectl cp <namespace>/<SOA Managed Server pod name>:<full path of .rar file>  <destination path inside PV>

    For example:

    kubectl cp soans/soainfra-soa-server1:/u01/oracle/soa/soa/connectors/ABC.rar ${DockerVolume}/domains/soainfra/servers/ABC.rar
                        

    Alternatively, use kubectl exec to access the managed server pod and copy the file between these locations.

  2. Extract ABC.rar.
  3. Update the connection details in weblogic-ra.xml under META_INF.
  4. In the WebLogic Remote Console, under Deployments, select ABC.rar, then Update. Set the new location of ABC.rar to ${DOMAIN_HOME}/user_projects/domains/soainfra/servers/ABC.rar and click Update.
  5. Verify that plan.xml or the updated .rar file is persisted on the PV.