Deprecated feature: Importing custom XSL files and extension functions into the WESB mediation module
The custom XSL files and extension functions are imported into the WESB mediation module. The custom XSL files are utilized by XSL Transformation primitives in mediation flows to transform WebSphere Commerce OAGIS BOD messages to and from External OMS Simulator messages. The custom XSL files use the extension functions to extract parameters from XPath expressions in WebSphere Commerce OAGIS BOD messages.
Procedure
-
Download the custom XSL files:
These custom XSL files are utilized by XSL Transformation primitives in mediation flows to transform WebSphere Commerce OAGIS BOD messages to and from External OMS Simulator messages.
- Extract the custom XSL files into a temporary directory, for example, C:\TEMP\ExtOMSSimMediationModuleTutorial\CustomXSLFiles.
- In WebSphere Integration Developer, select .
- Select .
- Click Browse and locate the temporary directory selected in step 2.
- Select all the files and select ExtOMSSimMediationModule/xslt/custom as the target directory. Create the directories if they do not already exist.
- Click Finish.
- Select .
- Select .
-
Click Browse and locate the WebSphere Commerce EAR directory:
- WC_eardir
- WCDE_installdir/workspace/WC
- Select Foundation-Core.jar and Foundation-Server.jar and select ExtOMSSimMediationModuleas the target directory.
- Click Finish.
-
Download the custom XSL extension functions JAR file to a temporary directory, for example,
C:\TEMP\ExtOMSSimMediationModuleTutorial:
These custom XSL files use the extension functions to extract parameters from XPath expressions in WebSphere Commerce OAGIS BOD messages.
- In WebSphere Integration Developer, select .
- Select .
- Click Browse and locate the temporary directory selected in step 13.
- Select MediationUtil.jar.
- Click Finish.