Script Adapter

How the Script Adapter Works

The Script adapter gives users a way to incorporate scripts into Sterling B2B Integrator business processes without having to write a new adapter to handle the business need.

The Script adapter executes scripts written in languages supported by the Bean Scripting Framework. The Script adapter provides tight coupling between BSF user scripts and Sterling B2B Integrator by allowing scripts to access java objects that are normally only available to Sterling B2B Integrator adapters, thus providing a solution to complex business problems.

Example

Your company uses a Python script to generate midday inventory reports from a legacy tracking system residing on a mainframe. Sterling B2B Integrator runs under UNIX, receiving and processing incoming orders and producing midday order reports. Rather than using two systems to produce the midday status reports, you use the Script adapter to import inventory data into the order reporting business process, allowing for easier tracking of orders against existing inventory.

Business Process Example

The following example uses the Script adapter:

<process name = "BSF"> 
  <operation name="Script Adapter">
   <participant name="ScriptAdapter"/>
   <output message="ScriptAdapterInputMessage">
     <assign to="scriptFileName">/somepath/test.py</assign>
     <assign to="." from="*"></assign>
   </output>
    <input message="inmsg">
     <assign to="." from="*"></assign>
   </input>
  </operation> 
</process>

Script Adapter Restrictions

The only scripts this adapter can execute have to be supported by the Bean Scripting Framework. If and when new script languages develop script engines that work with the Bean Scripting Framework, no code changes need to occur in the adapter code, as new script languages can be registered and used at any time.

Third-Party Adapters

For some adapters used with third-party software, you must install specific .jar files or drivers before you can use the adapter with Sterling B2B Integrator. These third-party .jar files are available from the applicable third-party software vendors. Often, you can download the files from the vendor's Web site. If an adapter requires any third-party files, the specific information about the files is included in the documentation for that adapter.

Implementing the Script Adapter

Configuring the Script Adapter

To configure the Script adapter, you must specify settings for the following fields in the GPM:

Objects Exposed for Use By a Script (Object Name – Class Exposed)

Testing the Script Adapter Configuration

After you have a script written that you want to test, create an instance of the Script adapter and create a business process that runs that instance.

Python Script Example

The following example (Test.py) illustrates a script written in Python:

# This script expects an input file with the workflow context 
# This script expects a bp called zze (FS Extract) to exist 
siDoc = siWfc.getPrimaryDocument(); 
name = siDoc.getBodyName(); 
body = siDoc.getBody(); 
siLog.logError(name); 
stuff = siRmi.readFile("/home/test.txt"); 
id1 = siWfd.getIDForName("zze"); 
siIwf.setWorkFlowDefId(id1); 
siIwf.setDocumentName("junk.txt"); 
siIwf.setDocumentBody(body); 
siWfk = siIwf.start(); 
id2 = siWfk.getWorkFlowId(); 
siLog.logError(str(id2)); 
siWfc.addBootStrapWorkFlows(str(id2)); 
siDoc = siWfc.createDocument(); 
siDoc.setBody("this is a test"); 
siDoc.setBodyName("test.txt"); 
siWfc.putPrimaryDocument(siDoc); 
siWfc.setWFContent("TestVal", "Hello"); 
siWfc.setWFStatusRpt("Status_Report", "hello"); 
siWfc.setAdvancedStatus("worked"); 
siWfc.setBasicStatus(siWfc.SUCCESS);