White Papers
Abstract
In a WebSphere Application Server BASE environment, you can configure more than one profile; they are all independent of each other, but can be managed by a single administration agent.
To deploy an application on a server of a registered node, you can connect to the WebSphere administration agent console, on its own admin port, select the profile's node and then go through the usual deploy console panels.
If you want to run the same deploy via wsadmin (AdminApp.install), here is how it works:
Content
When you register a standalone profile to the administration agent, the Admin Agent's serverindex.xml gets updated.
Subsystem ports are added, and one of them is the new SOAP port for the node of the profile we are registering
An example follows:
endPointName="SOAP_CONNECTOR_ADDRESS_LinuxRH841Node04">
<endPoint xmi:id="EndPoint_1761908108969" host="LinuxRH841Node04" port="8904"/>
</specialEndpoints>
at the same time, also the properties/wsadmin.properties file, of the profile we are registering, gets updated, to use that same SOAP subsystem port:
com.ibm.ws.scripting.port=8904
When you launch the wsadmin command, you need to specify the profile's name of the server where you are going to install your application, but actually, you get connected to the adminagent process:
wsadmin -lang jython -profileName <server's profile name> (like AppSrv01) and it will return:
WASX7209I: Connected to process "adminagent" on node <server's node_name> using SOAP connector; The type of process is: AdminAgent
there is nothing else to specify; just run the adminApp.install command as usual, and the application will be installed on the server. Note that the Admin Agent subsystem can manage more than one server on the same registered node, as is the case in an ND environment. Therefore the MapModuleToServer option must be set to tell the code which server it will be installed on, even if only one server is configured.
An example follows:
wsadmin>AdminApp.install ('/opt/IBM/WebSphereBASE90/AppServer/installableApps/PerfServletApp.ear', '[ -nopreCompileJSPs -distributeApp -nouseMetaDataFromBinary -nodeployejb -appname perfServletApp -createMBeansForResources -noreloadEnabled -nodeployws -validateinstall warn -noprocessEmbeddedConfig -filepermission .*\.dll=755#.*\.so=755#.*\.a=755#.*\.sl=755 -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -asyncRequestDispatchType DISABLED -nouseAutoLink -noenableClientModule -clientMode isolated -novalidateSchema -MapModulesToServers [[ perfservlet perfServletApp.war,WEB-INF/web.xml WebSphere:cell=LinuxRH841Node02Cell,node=LinuxRH841Node04,server=server1 ]]]' )
the output will be:
ADMA5016I: Installation of perfServletApp started.
ADMA5067I: Resource validation for application perfServletApp completed successfully.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
ADMA5005I: The application perfServletApp is configured in the WebSphere Application Server repository.
ADMA5005I: The application perfServletApp is configured in the WebSphere Application Server repository.
ADMA5081I: The bootstrap address for client module is configured in the WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5005I: The application perfServletApp is configured in the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in /opt/IBM/WebSphereBASE90/AppServer/profiles/AdminAgent01/wstemp/AppSrv01-BASE-979c27fa-5a97-473f-b57b-430b70addbd3/Script19a4fab0408/workspace/cells/LinuxRH841Node02Cell/applications/perfServletApp.ear/perfServletApp.ear
ADMA5005I: The application perfServletApp is configured in the WebSphere Application Server repository.
SECJ0400I: Successfully updated the application perfServletApp with the appContextIDForSecurity information.
ADMA5005I: The application perfServletApp is configured in the WebSphere Application Server repository.
ADMA5005I: The application perfServletApp is configured in the WebSphere Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application perfServletApp is complete.
ADMA5013I: Application perfServletApp installed successfully.
The wsadmin.traceout, containing the wsadmin messages log, is the server's one ( in this example under AppSrv01/logs).
The temporary directory (wstemp), used to upload the application's binaries during the install process, is that of AdminAgent.
Was this topic helpful?
Document Information
Modified date:
05 November 2025
UID
ibm17249846