WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Changing an SCA import binding using commands

You can use a command to change the SCA import bindings of service modules deployed to WebSphere® ESB.

Before you begin

Use the wsadmin tool to run the following commands.

About this task

An SCA binding connects one Service Component Architecture (SCA) module to another SCA module. Mediation modules are types of SCA module

You might change an SCA import binding if you wanted a particular service module to call a different service module. If you change an import binding you must ensure that the import and export match, that is, that the operations provided are equivalent. This might involve reviewing the WSDL.

To modify the binding of a particular service module import, you need to know the names of the source and target service modules, and the specific import and export.

The listSCAModules command lists all SCA modules that have been deployed to WebSphere ESB. The listSCAImports command lists all imports for a particular SCA module and the listSCAExports command lists all exports for a particular SCA module.

Procedure
  1. List the deployed SCA modules. $AdminTask listSCAModules
  2. List the imports for a particular SCA module. $AdminTask listSCAImports {-moduleName moduleName}
    Note: In addition to specifying the moduleName, you have the option of specifying the applicationName. Providing an applicationName improves performance.
  3. Modify an SCA module import binding, of type SCA. $AdminTask modifySCAImportSCABinding -moduleName moduleName -import importName -targetModule targetModuleName -targetExport targetExportName

    You also have the option of specifying the applicationName and targetApplicationName.

    Note: Providing an applicationName and a targetApplicationName improves performance.

Results

Changes the SCA import binding for a particular SCA module import.

WebSphere ESB issues a warning for each import interface that is not satisfied by an export interface. WebSphere ESB compares the WSDL port type names of import and export, if they are not the same then a warning is issued. However, if the port type names do match, then WebSphere ESB assumes that the operations provided are equivalent and no warning is issued.

Example

$AdminTask modifySCAImportSCABinding {-moduleName myModule -applicationName myApplication -import myImport -targetModule myTargetModule -targetApplicationName myTargetApplication -targetExport myTargetExport}

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/tasks/twesb_changingimportbindingviacommand.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).