WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Changing an import binding

You can use a command to change the SCA import bindings of mediation modules that have been deployed to WebSphere ESB.

Before you begin

You must use the wsadmin tool to run the following commands.

Why and when to perform this task

You might change an SCA import binding if you wanted a particular mediation module to invoke a different mediation 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. Use the wsadmin tool to complete the following steps.
Note: You can only modify Service Component Architecture (SCA) module import bindings if they are SCA bindings, but not if they are other types of bindings. An SCA binding connects one SCA module to another SCA module. Mediation modules are types of SCA module.

To modify the binding of a particular mediation module import, you need to know the names of the source and target mediation 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.

Steps for this task

  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
    Note: You also have the option of specifying the applicationName and targetApplicationName. Providing an applicationName and a targetApplicationName improves performance.

Result

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 topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\twesb_changingimportbindingviacommand.html

(C) Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)