We're updating the issue view to help you get more done. 

WebSphere deployer should take into account the server name

Description

The WebSphere deployer currently ignores the server name:

1 2 3 [INFO] [talledLocalContainer] WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode. [INFO] [talledLocalContainer] ADMA5016I: Installation of cargo-deployable-px started. [INFO] [talledLocalContainer] ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=cargoNodeCell,node=cargoNode,server=server1 for module px.war+WEB-INF/web.xml.

Note that my profile was created with server name set to cargoServer. I'm not sure why, but it looks like server name is not given, and therefore defaults to server1.

Status

Assignee

Savas Ali Tokmen

Reporter

Savas Ali Tokmen

Components

Fix versions

Priority

Major