Use WLST commands to update XSLT customizations in an existing SOA composite application.

To import XSLT customizations into an existing SOA composite application:

1. Start WLST:

   sh FMW_HOME/oracle_common/common/bin/wlst.sh

2. Use the sca_exportUpdates command to export the customizations to a .jar file.

   For example:

   sca_exportUpdates('http://soa_server_host:soa_server_port', 'all',
   '/tmp/test/sca_SupplierMaintenance_updates.jar', 'SupplierMaintenance',
   '1.0', user='weblogic', password='weblogic1')

   Note:

   If there are no previous customizations, this command will not create a .jar file. In this case, simply create a dummy .jar file using zip. For example, /tmp/test/sca_SupplierMaintenance_updates.jar.
3. Connect to the SOA server.

   connect('weblogic','weblogic1','t3://soa_server_host:soa_server_port')

4. Use the exportMetadata command to export the existing XSLT (.xsl) file.

   exportMetadata(application='soa-infra',server='soa_server1',toLocation='/tmp/test/',docs='/deployed-composites/default/SupplierMaintenance_rev1.0/Transformations/Transformation_InitializeBusinessRule.xsl')

5. Edit the .xsl with required updates.
6. Add the updates to the .jar file.

   For example:

   zip -r sca_SupplierMaintenance_updates.jar Transformations/*

   Now the .jar file includes the updated .xsl file under the same directory structure.

7. Use the sca_importUpdates command to import the update back into the SOA composite application to save the customization.

   For example:

    sca_importUpdates('http://soa_server_host:soa_server_port', '/tmp/test/sca_SupplierMaintenance_updates.jar', 'SupplierMaintenance', '1.0', user='weblogic', password='weblogic1')

8. Use the sca_exportUpdates command to export the updates again and confirm the changes are in place.

   For example:

    sca_exportUpdates('http://soa_server_host:soa_server_port', 'all', '/tmp/test/sca_SupplierMaintenance_updates.jar', 'SupplierMaintenance', '1.0', user='weblogic', password='weblogic1')