G Web Services Gateway messages

CWWSG1001E: Invalid Root AppServer Directory.
Explanation: The user has entered an invalid string on the command line to represent the location of the AppServer root directory.
User Response: Check for typing errors, then re-issue the command with the root directory of the AppServer.

CWWSG1002E: Invalid Cell Name.
Explanation: The user has entered an invalid string on the command line to represent the cell name.
User Response: Check for typing errors then re-issue the command with the correct cell name.

CWWSG1003E: Invalid Server Name.
Explanation: The user has entered an invalid string on the command line to represent the server name.
User Response: Check for typing errors then re-issue the command with the server you wish to use.

CWWSG1004E: Invalid argument {0}.
Explanation: The user has entered an unrecognized argument on the command line.
User Response: Check for typing errors the re-issue the command without the unrecognized argument.

CWWSG1005E: There must be one bus name for each file.
Explanation: The user has entered a backup file name on the command line without a bus name.
User Response: Re-issue the command with a valid bus name for each backup file.

CWWSG1006E: Missing Argument {0}.
Explanation: The user has omitted the installation directory, cell name or server name from the command line argument list.
User Response: Re-issue the command using all the required fields.

CWWSG1007E: Invalid file {0}.
Explanation: The backup file that was given on the command line is not valid, contains errors or omitted data.
User Response: Try recreating the backup file.

CWWSG1008E: Could not find WSDL {0}.
Explanation: The WSDL file for one of the services could not be found via HTTP.
User Response: Turn on the server holding this WSDL and re-issue the command.

CWWSG1009E: No service elements defined.
Explanation: WSDL file is invalid as it contains no services.
User Response: Correct the WSDL file or obtain a valid version then re-issue the command.

CWWSG1010E: Multiple services with same name: {0}.
Explanation: WSDL file is invalid as it contains multiple services with the same name.
User Response: Correct the WSDL file or obtain a valid version then re-issue the command.

CWWSG1011E: No port elements defined for service: {0}.
Explanation: WSDL file is invalid as the service contains no ports.
User Response: Correct the WSDL file or obtain a valid version then re-issue the command.

CWWSG1012E: Service {0} not found in WSDL {1}.
Explanation: WSDL File may be valid in itself but not for the required service. The specified service name was missing from this WSDL.
User Response: Correct the WSDL file or obtain a valid version then re-issue the command.

CWWSG1013E: The External End Point Address field is invalid.
Explanation: The ExternalEndPointAddress field in the backup file should be of the format http://:/.....
User Response: Correct the WSDL file or obtain a valid version then re-issue the command.

CWWSG1014E: The SOAPHeader field is invalid.
Explanation: The SOAPHeader field in the backup file should be of the format namespaceURI:localPart.
User Response: Correct the WSDL file or obtain a valid version then re-issue the command.

CWWSG1015E: There must be one node name for each file.
Explanation: The user has entered a backup file name on the command line without a node name.
User Response: Re-issue the command with a valid node name for each backup file.

CWWSG1016E: Invalid argument value {1} for argument {0}.
Explanation: The user has entered an invalid string on the command line.
User Response: Check for typing errors then re-issue the command with the corrected argument.

CWWSG1017E: Migration Error.
Explanation: An unhandled error has occurred during the migration process.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWWSG2001E: File {0} threw an IOException.
Explanation: The file probably doesn't exist. The error is likely to have been caused by a typing error on the command line.
User Response: Check for typing errors in the Gateway backup file stated on the command line and re-issue the command with corrections.

CWWSG2002E: A user-defined channel {0} has been identified in the file {1}.
Explanation: Only standard channels can be migrated using this utility, but an unrecognised channel has been found in the file.
User Response: Remove the channel definition from the file and re-issue the command.

CWWSG2003E: No UDDIPassword has been found for UDDIReference {0}.
Explanation: UDDIReferences with a publishURL specified must also have a username specified. If no authentication is needed, the username should be UNAUTHENTICATED.
User Response: Correct the UDDIReference and re-issue the command.

CWWSG2004W: More than one TargetServiceLocation found for Proxy Service {0}.
Explanation: A proxy service should not have more than one target service in the Gateway backup file. Only one of those found will be used.
User Response:

CWWSG2005W: More than one ChannelForService found for Proxy Service {0}.
Explanation: A proxy service should not have more than one channel in the Gateway backup file. Only one of those found will be used.
User Response:

CWWSG2501E: The routing could not be set for destination {0}.
Explanation: The destination could not have it's forward or reverse routing path set. Make sure the destination was created successfully.
User Response: If problem recurrs, contact your IBM representative.

CWWSG2502E: Destination {0} could not be created.
Explanation: The destination could not be created successfully.
User Response: If problem recurrs, contact your IBM representative.

CWWSG3001E: Could not find correlation destination {0}.
Explanation: The destination defined for correlation support could not be found.
User Response: Ensure that the destination has been defined correctly.

CWWSG3002E: Boolean property called {0} could not be found.
Explanation: The specified boolean property could not be found.
User Response: Ensure that the boolean property has been defined correctly.

CWWSG3003E: String property called {0} could not be found.
Explanation: The specified string property could not be found.
User Response: Ensure that the string property has been defined correctly.

CWWSG3004E: Could not send correlation information to destination.
Explanation: An error occurred while sending information to the correlation destination.
User Response: Ensure that correlation destination has been defined and enabled correctly.

CWWSG3005E: The Filter workarea could not be accessed.
Explanation: The workarea used by filters could not be accessed.
User Response: Ensure that the deployed filters access the workarea correctly.

CWWSG3006E: The message received was not recognized.
Explanation: The message received was not in a recognized form.
User Response: Enable tracing and inspect the form and content of the message received.

CWWSG3007E: The message received could not be converted into a suitable form.
Explanation: The message received was not recognized as one could that be converted by an installed data mediator.
User Response: Ensure that an appropriate data mediator for the message format has been installed.

CWWSG3008E: The request could not be logged.
Explanation: Information about the request received could not be logged.
User Response: Ensure that the log file is writable and that there is sufficient storage space to record the logging information.

CWWSG3009E: The filter list was not recognized, contents {0}.
Explanation: The list of filters provided in the property was not recognized.
User Response: Ensure that the list of filters is provided in a comma-separated (CSV) form, using the correct encoding.

CWWSG3010E: The filter {0} was not found.
Explanation: The filter {0} could not be found within the system or could not be instantiated.
User Response: Ensure that the filter {0} has been correctly deployed and activated.

CWWSG3011E: A routing query failed.
Explanation: A filter could not query the routing information for the current message.
User Response: Enabling tracing for the Gateway runtime, to determine where the problem occurred.

CWWSG3012E: A routing modification failed.
Explanation: A filter could not modify the routing information for the current message.
User Response: Enabling tracing for the Gateway runtime, to determine where the problem occurred.

CWWSG3013E: A response could not be sent.
Explanation: A filter indicated that a response should be sent, but this could not be done.
User Response: Enabling tracing for the Gateway runtime, to determine where the problem occurred.

CWWSG3014E: A filter threw a fatal exception.
Explanation: A filter threw a fatal exception, which could not be handled by the Gateway.
User Response: Enable tracing for the Gateway runtime and the filter, to determine the cause of the exception.

CWWSG3015E: The response could not be logged.
Explanation: Information about the response received could not be logged.
User Response: Ensure that the log file is writable and that there is sufficient storage space to record the logging information.

CWWSG3016E: Could not find correlation information for response.
Explanation: An error occurred while retrieving information from the correlation destination.
User Response: Ensure that correlation destination has been defined and enabled correctly.

CWWSG3017E: Could not locate referenced object {0}.
Explanation: An error occurred while performing a lookup.
User Response: Ensure that object has been defined correctly.

CWWSG3018E: The namespace {0} does not appear to be valid.
Explanation: An error occurred while working with the specified namespace.
User Response: Use trace information to determine what task was being performed when the error occured, and check that the namespace is correct and makes sense at that point.

CWWSG3019E: The service {0} does not appear to be valid.
Explanation: An error occurred while working with the specified service.
User Response: Use trace information to determine what task was being performed when the error occured, and check that the service is correct and makes sense at that point.

CWWSG3020E: The portname {0} does not appear to be valid.
Explanation: An error occurred while working with the specified portname.
User Response: Use trace information to determine what task was being performed when the error occured, and check that the portname is correct and makes sense at that point.

CWWSG3021E: The property {0} with value {1} does not appear to be valid.
Explanation: An error occurred while working with the specified property.
User Response: Use trace information to determine what task was being performed when the error occured, and check that the property and its value are correct and make sense at that point.

CWWSG3022E: The format of property {0} with value {1} does not appear to be valid.
Explanation: An error occurred while working with the specified property.
User Response: Check that the property value is correct and consistent with the required format.

CWWSG3023E: Could not locate the message property {0}.
Explanation: An expected property within the message could not be located.
User Response: Determine the contents of the message and its properties, and confirm that the expected property is present and in the correct form.

CWWSG3024E: Target service with location {0} was not found for gateway service {1}
Explanation: The given location could not be set as the target service because this location has not been defined as a target service for this gateway service.
User Response: Ensure that the correct target service location is specified.

CWWSG3025E: Target service identity cannot be specified as null
Explanation: A target service can only be selected using a non-null value for the identity.
User Response: Modify the calling code to ensure that the target service identity value is never null.

CWWSG3026E: Target service identity information {0} not matched for gateway service {1}
Explanation: A target service was requested by identity, but the identity information does not match any currently deployed target service.
User Response: Ensure that the identity information is correct, and that there is a target service deployed to the given gateway service with the right identity information.

CWWSG3027E: Target service with location {0} was not found for gateway service {1}
Explanation: The WSDL definition for the given location could not be returned because this location has not been defined as a target service for this gateway service.
User Response: Ensure that the correct target service location is specified.

CWWSG3028E: Error retrieving WSDL for target service named {0} in gateway service {1}
Explanation: The WSDL definition for this target service could not be retrieved.
User Response: Ensure that the gateway and target services are correctly defined.

CWWSG3029E: No default target service available for gateway service {0} on service integration bus {1}
Explanation: The default target service location cannot be obtained for the gateway service as no suitable target services are defined for it.
User Response: Ensure that one or more target services are defined for the gateway service.

CWWSG3030E: Could not determine default port name for target service {0} in gateway service {1} on service integration bus {2}
Explanation: There are no outbound ports defined for the outbound service associated with the given target or proxy service.
User Response: Make sure that there is at least one outbound port defined for the outbound service associated with the given target or proxy service.

CWWSG3031E: Target service with location {0} was not found for gateway service {1} on service integration bus {2}
Explanation: The given location could not be set as the target service because this location has not been defined as a target service for this gateway service.
User Response: Ensure that the correct target service location is specified.

CWWSG3032E: Port {0} does not exist for target service {1} in gateway service {2} on service integration bus {3}
Explanation: The requested port does not exist for the target service.
User Response: Ensure that a valid port is requested and defined as an outbound port in the outbound service associated with the given target or proxy service.

CWWSG3501W: Filter {0} threw a non-fatal exception.
Explanation: The filter {0} threw a non-fatal exception.
User Response: Enable tracing for filter {0} to determine the cause of the exception if this was unexpected.

CWWSG3502W: The message was not modified by any filter.
Explanation: No filter made a change to the message.
User Response: No action required. It is possible that one or more of the filters are not required.

CWWSG3503I: A request message has been received.
Explanation: A request message has been received.
User Response: No action required.

CWWSG3504I: A response message has been received.
Explanation: A response message has been received.
User Response: No action required.

CWWSG6001E: Unable to resolve outbound service {0}: {1} matches.
Explanation: The required outbound service could not be uniquely identified.
User Response: Ensure the outbound service exists and that the configuration is consistent.

CWWSG6002E: Either target destination or target service must be specified, but not both.
Explanation: An invalid gateway target service has been specified.
User Response: Ensure that the gateway target service specified is either a destination or an outbound service.

CWWSG6004E: No default WSDL location has been configured for gateway instance: {0}.
Explanation: The default WSDL location for the gateway instance is required but has not been configured.
User Response: Configure a default WSDL location for the gateway instance.

CWWSG6006E: No ports defined for service {0} in proxy service WSDL {1}.
Explanation: No ports are defined in the WSDL for the proxy service.
User Response: Ensure that the WSDL for the proxy service defines at least one port.

CWWSG6007E: A gateway service named {0} already exists within gateway instance {1}.
Explanation: A gateway service with the specified name already exists.
User Response: Ensure the name of the gateway service is unique within the gateway instance.

CWWSG6008E: A proxy service named {0} already exists within gateway instance {1}.
Explanation: A proxy service with the specified name already exists.
User Response: Ensure the name of the proxy service is unique within the gateway instance.

CWWSG6009E: A target service named {0} already exists for gateway service {1}.
Explanation: A gateway target service with the specified name already exists.
User Response: Ensure that the name of the target service is unique within a gateway service.

CWWSG6010E: Cannot remove the last target service for gateway service {0}.
Explanation: A gateway service must have at least one target service.
User Response: Add an additional target service before attempting to remove the last remaining target for a gateway service.

CWWSG6011E: Invalid parameter combination: {0}.
Explanation: The specified parameters are not a valid combination.
User Response: Consult the user documentation for valid parameter combinations.

CWWSG6012W: Inbound service {0} referenced by gateway service {1} was not found.
Explanation: An inbound service referenced in a gateway service's configuration does not exist.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWWSG6013W: Inbound service {0} referenced by proxy service {1} was not found.
Explanation: An inbound service referenced in a proxy service's configuration does not exist.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWWSG6014W: Outbound service {0} referenced by proxy service {1} was not found.
Explanation: An outbound service referenced in a proxy service's configuration does not exist.
User Response: If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.

CWWSG7000E: Cannot instantiate a JROM data mediator: exception {0}.
Explanation: Unable to access JROM Factory or JROM TypeMap Java classes.
User Response: Check Java classpath and installation configuration.

CWWSG7001E: Cannot create a root data object {0} from JROM tree: Parent property {1}:{2}.
Explanation: Unable to create the root SDO data object in the generated datagraph.
User Response: Check that JROM tree embedded in message has a single root and no orphans.

CWWSG7002E: Cannot create a datagraph from JROM tree.
Explanation: Unable to create the root SDO data object from the supplied JROM tree
User Response: Check that JROM tree embedded in message has a single root and no orphans.

CWWSG7003E: Cannot create a JROM tree from supplied datagraph.
Explanation: Unable to access JROM Factory or JROM TypeMap Java classes.
User Response: Check integrity of the supplied datagraph and model.

CWWSG7004E: SDO Property not found : {0}.
Explanation: The property was not located in the datagraph.
User Response: Check consistancy between JROM tree and repository model.

CWWSG7005E: Cannot create a JROM tree from supplied datagraph.
Explanation: Unable to access JROM Factory or JROM TypeMap Java classes.
User Response: Check integrity of the supplied datagraph and model.

CWWSG7006E: Invalid format string : {0}.
Explanation: Unable to parse the given format string as it does not conform to designated rules.
User Response: Correct the internal format string used.

CWWSG7007E: Method invocation failure : exception {0}.
Explanation: Failed to invoke a Java method using the Introspection API.
User Response: Ensure method is referenced correctly and is defined.

CWWSG7008E: Type mapping failure : exception {0}.
Explanation: Failed to locate a Java method using the Introspection API.
User Response: Ensure method is referenced correctly and is defined.

CWWSG7009E: DataObject and JROMValue types differ, with no conversion defined: {0}.
Explanation: Unable to find conversion method for Type.
User Response: Check integrity of the supplied datagraph and model.

CWWSG7010E: Property is not a leaf or is unset: {0}.
Explanation: Unable to access JROM Factory or JROM TypeMap Java classes.
User Response: Check integrity of the supplied datagraph and model.

CWWSG7011E: Property is not single-valued: {0}.
Explanation: Expected a single valued property but found many-valued.
User Response: Check integrity of the supplied datagraph and model.

CWWSG7012E: Property is not a JROM Simple Type: {0}.
Explanation: Expected a simple type property but found complex.
User Response: Check integrity of the supplied datagraph and model.