This topic applies only to the IBM Business Process Manager Advanced configuration.

validateSCAImportExportInformation command

This command validates import and export information associated with an SCA module. It takes an EAR file as input and validates that all expected exports exist on the bus.

Use the validateSCAImportExportInformation command to validate the following:

All selector export bindings point to valid exports on the bus
All SCA imports point to valid exports on the bus

If the expected exports are not available, the command returns a warning.

Note: The product uses a Jython version that does not support Microsoft Windows 2003, Windows Vista, or Windows 7 operating systems.

Prerequisites

Run the command in connected mode. You must connect as a cell administrator that is assigned the CellAdmin role, or a deployment environment administrator that is assigned the DEAdmin role.

Location

Start the wsadmin scripting client from the install_root/profiles/deployment_manager_profile/bin directory.

Syntax


>>-$AdminTask-- -validateSCAImportExportInformation-- - -earFilePath-- -earFile-><

Required parameters

-earFilePath earFile: This parameter identifies the fully qualified EAR file name you have installed or are planning to install. Specify the full path to the EAR file (for example, install_root/profiles/profile_name/installedApps/cellName/applicationName.ear for an application that has already been installed, or pathToApplication/applicationName.ear for an uninstalled application).

Command output

If all imports and exports are validated, the command returns the following message:

LFCOR1003I: SCA export information validated successfully. No errors were found

If validation fails, the command returns one or more of the following warning messages:

LFCOR1001W: No matching export was found for selector target with module name moduleName and export name exportName in selector component selectorComponentName.

LFCOR1002W: No matching export was found for SCA import importName with module name moduleName and export name exportName.

Fix missing bindings in one of the following ways:

If the targeted module is not installed, install it now.
If the unknown binding is for a selector component, install the EAR and then use the administrative console or commands to update the targets.
If the unknown binding is an SCA import binding, install the EAR and then use the administrative console or commands to update the binding manually.

Example

The following example illustrates how to validate the SCA import and export information associated with the previously installed billingProcess.EAR application.

$AdminTask validateSCAImportExportInformation {-earFilePath C:\WPS62\profiles\Profile03\installedApps\server01Node01Cell\billingProcess.ear}

Batch mode example usage:

Using Jacl:

$AdminTask validateSCAImportExportInformation {-earFilePath C:\WPS62\profiles\Profile03\installedApps\server01node01Cell\billingProcess.ear}

Using Jython:

AdminTask.validateSCAImportExportInformation('[-earFilePath C:\WPS62\profiles\Profile03\installedApps\server01node01Cell\billingProcess.ear]')