+

Search Tips   |   Advanced Search

Get started with wsadmin scripting

The wsadmin tool supports Jacl and Jython.

wsadmin objects communicate with MBeans running in appserver processes. MBeans use Java objects that represent JMX resources. Five objects are available:


File system access permissions

Some wsadmin scripts, including the AdminApp install, AdminApp update, and some AdminTask commands, require that the user ID under which the server is running must have read permission to the files created by the user running wsadmin scripting. For example, if the application server is running under user1, but we are running wsadmin scripting under user2, we might encounter exceptions involving a temporary directory. When user2 runs wsadmin scripting to deploy an application, a temporary directory for the EAR file is created. However, when the application server attempts to read and unzip the EAR file as user1, the process fails. IBM recommends to not set the umask value of the user running wsadmin scripting to 022 or 023 to work around this issue. This approach makes all of the files created by the user readable by other users. To resolve this issue, consider the following approaches based on our administrative policies:


Subtopics

  1. Start the wsadmin scripting client
  2. Jython
  3. Jacl (deprecated)
  4. Use wsadmin scripting
  5. wsadmin scripting tool
  6. wsadmin objects
  7. Reference material
  8. WAS configuration model
  9. JMX resources
  10. Restricting remote access using scripting
  11. Administrative properties
  12. IBM Jacl to Jython Conversion Assistant
  13. WAS Administration Using Jython