WAS v8.5 >

Script the application serving environment (wsadmin)

Use the wsadmin scripting tool and commands to administer production environments and realistic test environments. Perform post-installation and customization tasks, deploy applications onto application servers, and administer applications and their server environments.

Use the Administering applications and their environments section to use the dmgr console to manage your configuration settings.

Subtopics

• How do I use wsadmin commands to administer applications and their environments?
  The wsadmin tool is a command-line interface that provides the ability to automate common tasks using Jacl or Jython scripts. The AdminTask, AdminApp, AdminControl, AdminConfig, and Help objects provide many commands and options that allow us to write and customize scripts to administer the applications, environment, web services, resources, and security configurations.
• Use wsadmin scripting
  The WebSphere administrative (wsadmin) scripting program is a powerful, non-graphical command interpreter environment enabling you to run administrative operations in a scripting language.
• Scripting concepts
  Scripting provides a non-graphical alternative to the dmgr console. Using wsadmin, we can run scripts to manage the product. The wsadmin tool supports two scripting languages: Jacl and Jython. Five objects are available with scripts: AdminControl, AdminConfig, AdminApp, AdminTask, and Help. Scripts use these objects to communicate with MBeans that run in product processes. MBeans are Java objects that represent JMX resources. JMX is a technology that provides a simple and standard way to manage Java objects.
• Get started with wsadmin scripting
  Scripting is a non-graphical alternative used to manage WAS.
• Use the wsadmin scripting objects
  The wsadmin tool utilizes a set of management objects which allow us to run commands and command parameters to configure the environment. Use the AdminConfig, AdminControl, AdminApp, AdminTask, and Help objects to perform administrative tasks.
• Use the wsadmin scripting AdminApp object for scripted administration
  Use the AdminApp object to manage applications.
• Use the wsadmin scripting AdminControl object for scripted administration
  The AdminControl scripting object is used for operational control. It communicates with MBeans that represent live objects running a WebSphere server process.
• Use the wsadmin scripting AdminConfig object for scripted administration
  Use the AdminConfig object to manage the configuration information stored in the repository.
• Use the wsadmin scripting AdminTask object for scripted administration
  Use AdminTask to access a set of administrative commands that provide an alternative way to access the configuration commands and the running object management commands.
• Start the wsadmin scripting client using wsadmin.sh
  We can use wsadmin to configure and administer application servers, application deployment, and server runtime operations.
• Use the script library to automate the application serving environment using wsadmin.sh
  The script library provides Jython script procedures to assist in automating the environment. Use the sample scripts to manage applications, resources, servers, nodes, and clusters. We can also use the script procedures as examples to learn the Jython syntax.
• Administer applications using wsadmin.sh
  We can use administrative scripts and wsadmin to install, uninstall, and manage applications.
• Manage deployed applications using wsadmin.sh
  Use these topics to learn more about managing deployed applications with wsadmin and scripting.
• Configure applications using scripting
  Using wsadmin, we can run scripts to configure applications.
• Configure servers with scripting
  We can use wsadmin to configure application servers in the environment. An application server configuration provides settings that control how an application server provides services for running applications and their components.
• Set up intermediary services using scripting
  Use wsadmin and the Jython scripting language to configure intermediary services, such as web servers, and proxy servers.
• Manage servers and nodes with scripting
  Use wsadmin to administer your administrative architecture and runtime settings.
• Use properties files to manage system configuration
  Use wsadmin and properties files to administer your administrative architecture and runtime settings.
• Directory conventions
  References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. This article describes the conventions in use for WAS.
• Use the Administration Thin Client
  With the Administration Thin Client, we can run wsadmin or a standalone administrative Java program with only a couple of JAR files. This reduces the amount of time that it takes for wsadmin to start and improved performance. This information should be used to set up JMX client programs.
• Troubleshooting with scripting
  Use these topics to learn more about troubleshooting with scripting.
• Scripting and command line reference material using wsadmin.sh
  Use this topic to locate wsadmin tool commands for the AdminTask, AdminControl, AdminConfig, and AdminApp scripting objects. This topic also provides a pointer to command line commands and options.
• Scripting for data access resources
  This page provides a starting point for finding information about data access. Various enterprise information systems (EIS) use different methods for storing data. These backend data stores might be relational databases, procedural transaction programs, or object-oriented databases.
• Scripting for Mail, URLs, and other Java EE resources
  This page provides a starting point for finding information about resources used by applications deployed on a Java EE-compliant application server. They include:
• Scripting for Messaging resources
  The use of asynchronous messaging resources for enterprise applications with WAS.
• Scripting for naming and directory
  This page provides a starting point for finding information about naming support. Naming includes both server-side and client-side components. The server-side component is a Common Object Request Broker Architecture (CORBA) naming service (CosNaming). The client-side component is a JNDI service provider. JNDI is a core component in the Java EE programming model.
• Scripting for security
  
• Scripting for Service integration
  This page provides a starting point for finding information about service integration.
• Scripting web applications
  Web applications are comprised of one or more related files managed as a unit, including HTML files; Servlets can support dynamic web page content, provide database access, serve multiple clients at one time, and filter data; and Java ServerPages (JSP) files enable the separation of the HTML code from the business logic in web pages. IBM extensions to the JSP specification make it easy for HTML authors to add the power of Java technology to web pages, without being experts in Java programming.
• Scripting for web services
  This page provides a starting point for finding information about web services.

Related concepts:

How do I?...
Overview
What is new
Web resources

+

Search Tips   |   Advanced Search