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 administrative console to manage your configuration settings.
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 you to write and customize scripts to administer your applications, environment, web services, resources, and security configurations. Follow these shortcuts to get started quickly with popular tasks.
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 provides a non-graphical alternative to the administrative console. Using the wsadmin tool, you can run scripts to configure and 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 Java Management Extensions (JMX) resources. JMX is a technology that provides a simple and standard way to manage Java objects.
Scripting is a non-graphical alternative that you can use to configure and manage WebSphere Application Server.
The wsadmin tool utilizes a set of management objects which allow you to execute commands and command parameters to configure your environment. Use the AdminConfig, AdminControl, AdminApp, AdminTask, and Help objects to perform administrative tasks.
Use the AdminApp object to manage applications.
The AdminControl scripting object is used for operational control. It communicates with MBeans that represent live objects running a WebSphere server process.
Use the AdminConfig object to manage the configuration information that is stored in the repository.
Use the AdminTask object to access a set of administrative commands that provide an alternative way to access the configuration commands and the running object management commands.
You can use the wsadmin tool to configure and administer application servers, application deployment, and server runtime operations.
You can use the wsadmin tool to restrict remote administration so that administrators only manage nodes locally. This prevents the base node from opening remote ports for the administrator. Each administrative connection must occur from the local workstation.
The script library provides Jython script procedures to assist in automating your environment. Use the sample scripts to manage applications, resources, servers, nodes, and clusters. You can also use the script procedures as examples to learn the Jython syntax.
You can use administrative scripts and the wsadmin tool to install, uninstall, and manage applications.
Use these topics to learn more about managing deployed applications with the wsadmin tool and scripting.
Using the wsadmin tool, you can run scripts to configure applications.
You can use the wsadmin tool to configure application servers in your environment. An application server configuration provides settings that control how an application server provides services for running applications and their components.
Use the wsadmin tool and the Jython scripting language to configure intermediary services, such as Web servers, proxy servers, and DataPower® appliances.
Use the wsadmin tool to administer your administrative architecture and runtime settings.
Use the wsadmin tool and properties files to administer your administrative architecture and runtime settings.
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. This topic describes the conventions in use for WebSphere Application Server.
Use the flexible management environment to locally or remotely submit and manage administrative jobs. You can use the job manager to manage applications, modify configurations, and control the application server run time.
You can use scripting and the wsadmin tool to cluster application servers, generic servers, web servers, and proxy servers.
With the Administration Thin Client, you can run the wsadmin tool or a standalone administrative Java program with only a couple of Java archive (JAR) files. This reduces the amount of time that it takes for the wsadmin tool to start and improved performance. This information should be used to set up JMX client programs.
Use these topics to learn more about troubleshooting with scripting.
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.
You can use wsadmin scripts to remove the common batch container from your deployment target or redeploy the common batch container on your deployment target. You can use the JobSchedulerCommands command group to show or modify job scheduler attributes, and to create, modify, remove, or list job scheduler custom properties.
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.
This page provides a starting point for finding information about resources that are used by applications that are deployed on a Java Enterprise Edition (Java EE)-compliant application server. They include:
This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere Application Server.
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 Java™ Naming and Directory Interface (JNDI) service provider. JNDI is a core component in the Java Platform, Enterprise Edition (Java EE) programming model.
This page provides a starting point for finding information about service integration.
This page provides a starting point for finding information about web applications, which are comprised of one or more related files that you can manage 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.
This page provides a starting point for finding information about web services.