![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Using TIBCO ActiveMatrix BusinessWorksThis section includes procedures and prerequisites that have to be carried out to integrate the adapter with TIBCO ActiveMatrix BusinessWorks.Configuring a TIBCO ActiveMatrix BusinessWorks ExampleTo configure a TIBCO ActiveMatrix BusinessWorks example:
1. Start TIBCO Designer and select New Empty Project.
2. In the Save Project dialog, click the Browse button to select the location of the project and click OK. A project is created.
3. Drag and drop the KenanAdapterConfiguration icon from the palettes panel into the design panel. An adapter instance is created and the default instance name is KenanAdapterConfiguration. You can change the instance name.
4. Click the Global Variables tab in the project panel and provide values for the following global variables:
− adkenanLogin (The username used to connect to the Security Server)
− adkenanPassword (The password used to connect to the Security Server)
− adkenanSecurityRealm (The Security Realm variable for the Security Server)
5. Drag and drop the Request-Response Service icon from the palette panel into the design panel.
6. Save the project by selecting Project > Save.Task B Import the XSD files
2. Create a folder named XSD under the project root folder where you will store all imported XSD files.
3.
4. Import the following XSD files in the order specified: request.xsd, AccountLocate.xsd, ExternalIdAcctMap.xsd, CreditCard.xsd, and Account.xsd. The order is useful because Account.xsd includes the schema location of the other XSD files. These XSD files are a part of the Kenan/BP installation.
5. To import an XSD file, select Project > Import Resources from File, Folder, URL. Select the file (.xsd,.xslt,.wsdl) from the drop-down list and browse to location of the XSD file.
1. Create a new TIBCO ActiveMatrix BusinessWorks process by dragging and dropping the Process Definition icon from the palette panel to the design panel.
b. Click the Input Editor tab.
c.
d. In the Schema field (which shows a default of <No Namespace>), browse and select the AccountGet element in Account.xsd as shown in Figure 8.
e. Click OK in the Select a Resource dialog box.
f. Click Apply in the Mapper task dialog box.
g. Select the Input tab to provide the field values to execute this request.
h. Expand the AccountGet node in the Activity Input panel and specify a value for the AccountInternal Id and specify int in the e-dtype field as shown in Figure 9.
i. Click Apply.Figure 8 Select a ResourceFigure 9 Map Data
c. In the Configuration tab, select text in the Output Style drop-down list. Check the Validate Input and Format with Default Namespace Prefix checkboxes. Select UTF-8 for encoding.
d. In the Input Editor tab, select the Request element from Account.xsd. The procedure is exactly the one used in the Mapper task. (Refer to step c and step d in step 2).
f. Expand the Request node in the Activity Input panel. Specify values for the fields under the Header group.
g. Drag and drop the AccountGet node from the Process Data panel (this is the output of the mapper task) into the node named any element or exception.
h. In the dialog box that follows, titled Mapping Wizard, select (any element). Click Next and then click Finish.
a. Drag and drop the Invoke an Adapter Request-Response Service icon from the palette panel to the design panel.
d. Map the Render XML output (a string called XMLstring) to the incoming Request-Response Schemas (a string named InXMLMsg) as shown in Figure 10.
e. Click Apply.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |