Running wsadmin remotely in a Java 2 Platform, Standard Edition environment

The thin admin client adds JAR files that support administrative client functions that we can use with IBM Developer Kits For the Java ™ Platform.

Thin admin clients do not support the installation of SAR files or the editing of applications that use an external JACC provider such as TAM.

For tracing and logging information for the thin admin client, see the Enable trace on client and stand-alone applications article.

Obtain the thin admin client JAR file and other required files that are required when security is on from the WebSphere Application Server ND installation. Refer to the Use the Administration Thin Client article for details about the files that we need to perform this task.
Generate the wsadmin.sh or the wsadmin.bat file from the server machine. This file does not ship with the application client.
There is an example of wsadmin.bat step 4.
Copy the Java directory from the server installation to the thin client environment.

Start wsadmin in a non-OSGi environment. Examples of the wsadmin.bat file and the wsadmin.sh file follow:

Example: wsadmin.sh

@REM wsadmin launcher 
@echo off 
@REM Usage: wsadmin arguments setlocal 
@REM was home should point to whatever directory you decide for your thin client environment 

set WAS_HOME=c:\MyThinClient 
set USER_INSTALL_ROOT=%WAS_HOME% 

@REM Java home should point to where you installed java for your thinclient 
set JAVA_HOME="%WAS_HOME%\java" 
set WAS_LOGGING=-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Djava.util.logging.configureByServer=true
set THIN_CLIENT=-Dcom.ibm.websphere.thinclient=true

if exist "%JAVA_HOME%\bin\java.exe" (
    set JAVA_EXE="%JAVA_HOME%\bin\java" ) 
 else ( 
    set JAVA_EXE="%JAVA_HOME%\jre\bin\java" )  

@REM CONSOLE_ENCODING controls the output encoding used for stdout/stderr 
@REM console - encoding is correct for a console window 
@REM file - encoding is the default file encoding for the system 
@REM other - the specified encoding is used.  e.g. Cp1252, Cp850, SJIS 
@REM SET CONSOLE_ENCODING=-Dws.output.encoding=console  
@REM For debugging the utility itself 
@REM set WAS_DEBUG=-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=7777  

set CLIENTSOAP=-Dcom.ibm.SOAP.ConfigURL=file:"%USER_INSTALL_ROOT%"\properties\soap.client.props 
set CLIENTSAS=-Dcom.ibm.CORBA.ConfigURL=file:"%USER_INSTALL_ROOT%"\properties\sas.client.props 
set CLIENTSSL=-Dcom.ibm.SSL.ConfigURL=file:"%USER_INSTALL_ROOT%"\properties\ssl.client.props 
set CLIENTIPC=-Dcom.ibm.IPC.ConfigURL=file:"%USER_INSTALL_ROOT%"\properties\ipc.client.props  
set JAASSOAP=-Djava.security.auth.login.config=%USER_INSTALL_ROOT%\properties\wsjaas_client.conf


@REM the following are wsadmin property 
@REM you need to change the value to enabled to turn on trace 
set wsadminTraceString=-Dcom.ibm.ws.scripting.traceString=com.ibm.*=all=disabled 
set wsadminTraceFile=-Dcom.ibm.ws.scripting.traceFile="%USER_INSTALL_ROOT%"\logs\wsadmin.traceout 
set wsadminValOut=-Dcom.ibm.ws.scripting.validationOutput="%USER_INSTALL_ROOT%"\logs\wsadmin.valout 

@REM this will be the server host that you will connecting to 
set wsadminHost=-Dcom.ibm.ws.scripting.host=myhost.austin.ibm.com  

@REM you need to make sure the port number is the server SOAP port number you want to connect to, in this example the server SOAP port is 8887 
set wsadminConnType=-Dcom.ibm.ws.scripting.connectionType=SOAP 
set wsadminPort=-Dcom.ibm.ws.scripting.port=8887  

@REM you need to make sure the port number is the server RMI port number you want to connect to, in this example the server RMI Port is 2815 
@REM set wsadminConnType=-Dcom.ibm.ws.scripting.connectionType=RMI 
@REM set wsadminPort=-Dcom.ibm.ws.scripting.port=2815  

@REM you need to make sure the port number is the server JSR160RMI port number you want to connect to, in this example the server JSR160RMI Port is 2815 
@REM set wsadminConnType=-Dcom.ibm.ws.scripting.connectionType=JSR160RMI 
@REM set wsadminPort=-Dcom.ibm.ws.scripting.port=2815  

@REM you need to make sure the port number is the server IPC port number you want to connect to, in this example the server IPC Port is 9632 and the host for IPC should be localhost 
@REM set wsadminHost=-Dcom.ibm.ws.scripting.ipchost=localhost 
@REM set wsadminConnType=-Dcom.ibm.ws.scripting.connectionType=IPC 
@REM set wsadminPort=-Dcom.ibm.ws.scripting.port=9632  

@REM specify what language you want to use with wsadmin 
set wsadminLang=-Dcom.ibm.ws.scripting.defaultLang=jacl 
@REM set wsadminLang=-Dcom.ibm.ws.scripting.defaultLang=jython  

set SHELL=com.ibm.ws.scripting.WasxShell  

:prop set WSADMIN_PROPERTIES_PROP= 
if not defined WSADMIN_PROPERTIES goto workspace 
set WSADMIN_PROPERTIES_PROP="-Dcom.ibm.ws.scripting.wsadminprops=%WSADMIN_PROPERTIES%"  

:workspace set WORKSPACE_PROPERTIES= 
if not defined CONFIG_CONSISTENCY_CHECK goto loop 
set WORKSPACE_PROPERTIES="-Dconfig_consistency_check=%CONFIG_CONSISTENCY_CHECK%"  

:loop 
if '%1'=='-javaoption' goto javaoption 
if '%1'=='' goto runcmd 
goto nonjavaoption  

:javaoption 
shift 
set javaoption=%javaoption% %1 
goto again  

:nonjavaoption 
set nonjavaoption=%nonjavaoption% %1  

:again 
shift 
goto loop   

:runcmd  

set C_PATH="%WAS_HOME%\properties;%WAS_HOME%\com.ibm.ws.admin.client_7.0.0.jar;%WAS_HOME%\com.ibm.ws.security.crypto.jar" 

set PERFJAVAOPTION=-Xms256m -Xmx256m -Xj9 -Xquickstart  

if "%JAASSOAP%"=="" set JAASSOAP=-Djaassoap=off  

"%JAVA_EXE%" %PERFJAVAOPTION% %WAS_LOGGING% %javaoption% %CONSOLE_ENCODING% %WAS_DEBUG% "%THIN_CLIENT%" "%JAASSOAP%" "%CLIENTSOAP%" "%CLIENTSAS%" "%CLIENTIPC%" "%CLIENTSSL%" %WSADMIN_PROPERTIES_PROP% %WORKSPACE_PROPERTIES% "-Duser.install.root=%USER_INSTALL_ROOT%" "-Dwas.install.root=%WAS_HOME%" %wsadminTraceFile% %wsadminTraceString% %wsadminValOut% %wsadminHost% %wsadminConnType% %wsadminPort% %wsadminLang% -classpath %C_PATH% com.ibm.ws.scripting.WasxShell %*  

set RC=%ERRORLEVEL%  

goto END  

:END  

@endlocal 
set MYERRORLEVEL=%ERRORLEVEL% if defined PROFILE_CONFIG_ACTION exit %MYERRORLEVEL% else exit /b %MYERRORLEVEL%

Use scripting (wsadmin)
Enable trace on client and stand-alone applications
Start wsadmin