Getting started with scripting Provides an introduction to WebSphere Application Server scripting and information about using the wsadmin tool. Topics include information about the scripting languages and the scripting objects, and instructions for starting the wsadmin tool Using the Jython script library 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 Deploying applications Provides instructions for deploying and uninstalling applications. For example stand-alone Java archive files and Web archive files, the administrative console, remote enterprise archive(EAR) files, file transfer applications, and so on Managing deployed applications Includes tasks that you perform after the application is deployed For example, starting and stopping applications, checking status, modifying listener address ports, querying application state, configuring a shared library, and so on Configuring servers Provides instructions for configuring servers, such as creating a server, modifying and restarting the server, configuring the Java virtual machine, disabling a component, disabling a service, and so on Configuring connections to Web servers Includes topics such as regenerating the plug-in, creating new virtual host templates, modifying virtual hosts, and so on Managing servers Includes tasks that you use to manage servers. For example, stopping nodes starting and stopping servers, querying a server state, starting a listener port, and so on Configuring security Includes security tasks such as enabling and disabling security. Configuring data access Includes topics such as configuring a Java Data Base Connectivity (JDBC) ovider, defining a data source, configuring connection pools, and so on Configuring messaging Includes topics about messaging, such as Java Message Service(JMS connection, JMS provider, WebSphere queue connection factory, MQ topics, and so on Configuring mail, URLS, and resource environment entries Includes topics such as mail providers, mai sessions, protocols, resource environment providers, referenceables, URL providers, URLS, and so on Troubleshooting Provides information about how to troubleshoot using scripting. For example, tracing thread dumps, profiles, and so on Obtaining product information Includes tasks such as querying the product identification Scripting reference material Includes all of the reference material related to scripting. Topics include the syntax for the wsadmin tool and for the administrative command framework, explanations and examples for all of the scripting object commands, the scripting properties, and so on Introduction Administrative commande Command line tools are simple programs that you run from an operating system command-line prompt to perform specific tasks, as opposed to general purpose administration. Using the tools, you can start and stop application servers, check server status, add or remove nodes, and complete similar tasks and syntax of all the commands that are available with the product. a subset of these commands s es See Reference Administrator> Commands in the information center navigation area for the name particular to system administration purposes Introduction: Administrative programs The Java Management Extensions (JMX) specification allows you to write Java programs to administer WebSphere Application Server. The product supports a Java programming interface for developing administrative programs. All of the administrative tools supplied with the product are written according to the APl, which is based on the industry standard Java Management Extensions(JMX) specification. You can write a Java program that performs any of the administrative features of the Web Sphere Application Server administrative tools. You can also extend the basic WebSphere Application Server administrative system to include your own managed resources Chapter 1 Overview and new features: Administering 19
v Getting started with scripting Provides an introduction to WebSphere Application Server scripting and information about using the wsadmin tool. Topics include information about the scripting languages and the scripting objects, and instructions for starting the wsadmin tool. v Using the Jython script library 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. v Deploying applications Provides instructions for deploying and uninstalling applications. For example, stand-alone Java archive files and Web archive files, the administrative console, remote enterprise archive (EAR) files, file transfer applications, and so on. v Managing deployed applications Includes tasks that you perform after the application is deployed. For example, starting and stopping applications, checking status, modifying listener address ports, querying application state, configuring a shared library, and so on. v Configuring servers Provides instructions for configuring servers, such as creating a server, modifying and restarting the server, configuring the Java virtual machine, disabling a component, disabling a service, and so on. v Configuring connections to Web servers Includes topics such as regenerating the plug-in, creating new virtual host templates, modifying virtual hosts, and so on. v Managing servers Includes tasks that you use to manage servers. For example, stopping nodes, starting and stopping servers, querying a server state, starting a listener port, and so on. v Configuring security Includes security tasks such as enabling and disabling security. v Configuring data access Includes topics such as configuring a Java DataBase Connectivity (JDBC) provider, defining a data source, configuring connection pools, and so on. v Configuring messaging Includes topics about messaging, such as Java Message Service (JMS) connection, JMS provider, WebSphere queue connection factory, MQ topics, and so on. v Configuring mail, URLs, and resource environment entries Includes topics such as mail providers, mail sessions, protocols, resource environment providers, referenceables, URL providers, URLs, and so on. v Troubleshooting Provides information about how to troubleshoot using scripting. For example, tracing, thread dumps, profiles, and so on. v Obtaining product information Includes tasks such as querying the product identification. v Scripting reference material Includes all of the reference material related to scripting. Topics include the syntax for the wsadmin tool and for the administrative command framework, explanations and examples for all of the scripting object commands, the scripting properties, and so on. Introduction: Administrative commands Command line tools are simple programs that you run from an operating system command-line prompt to perform specific tasks, as opposed to general purpose administration. Using the tools, you can start and stop application servers, check server status, add or remove nodes, and complete similar tasks. See Reference > Administrator > Commands in the information center navigation area for the names and syntax of all the commands that are available with the product. A subset of these commands is particular to system administration purposes. Introduction: Administrative programs The Java Management Extensions (JMX) specification allows you to write Java programs to administer WebSphere Application Server. The product supports a Java programming interface for developing administrative programs. All of the administrative tools supplied with the product are written according to the API, which is based on the industry standard Java Management Extensions (JMX) specification. You can write a Java program that performs any of the administrative features of the WebSphere Application Server administrative tools. You can also extend the basic WebSphere Application Server administrative system to include your own managed resources. Chapter 1. Overview and new features: Administering 19
Introduction: Administrative configuration data leb Sphere Application Server configuration data is kept in files. All administrative actions that you perform involve changes to these files The WebSphere Application Server product includes an implementation of the Java Management Extension (JMX) specification. All operations on managed resources in the product go through JMX functions. This setup means a more standard framework underlying your administrative operations as well as the ability to tap into the systems management infrastructure programmatically Introduction: Application servers Application servers provide the core functionality of the Web Sphere Application Server product family Application servers extend the ability of a Web server to handle Web application requests, and much more. An application server enables a server to generate a dynamic, customized response to a client Introduction: Application servers An application server is a Java Virtual Machine(JVM) that runs user applications. The applicatio on server collaborates with the Web server to return a dynamic, customized response to a client request. The client request can consist of servlets, Java Server Pages(JSP) files, and enterprise beans, and their supporting For example, a user at a Web browser visits a company Web site 1. The user requests access to data in a database 2. The user request flows to the Web server. 3. The Web server determines that the request involves an application containing resources not handled directly by the Web server (such as servlets). It forwards the request to one of its application servers on which the application is running 4. The invoked application then processes the user request. For example An application servlet prepares the user request for processing by an enterprise bean that performs the database access The application produces a dynamic Web page containing the results of the user query 5. The application server collaborates with the Web server to return the results to the user at the Web hen you install the product, a default application server, named server1, is automatically created. You can use the administrative console to manage this server. You can use the administrative console or command-line tools to create additional application servers that can either be separately configured processes or nearly identical clones. You must either use command-line tools to manage these additional servers, set up an administrative console for each server, or configure an administrative agent to provide a single interface to all of your servers, including the original base server. An administrative agent makes it easier to more fully administer these unfederated application servers Note: If you create additional application servers, only use one server to modify and save configurations There is no coordination of configuration setting between the different servers and if you modify and save configurations on multiple servers, your data might become corrupted Note: You can improve system performance if you configure some of your application servers, such that each of their components are dynamically started as they are needed, instead of letting all of these components automatically start when the server starts. Selecting this option can improve server startup time, and reduce the memory footprint. Starting components as they are needed is most effective if all of the applications that are deployed on the application server are of the same type 20 Administering applications and their environment
Introduction: Administrative configuration data WebSphere Application Server configuration data is kept in files. All administrative actions that you perform involve changes to these files. The WebSphere Application Server product includes an implementation of the Java Management Extension (JMX) specification. All operations on managed resources in the product go through JMX functions. This setup means a more standard framework underlying your administrative operations as well as the ability to tap into the systems management infrastructure programmatically. Introduction: Application servers Application servers provide the core functionality of the WebSphere Application Server product family. Application servers extend the ability of a Web server to handle Web application requests, and much more. An application server enables a server to generate a dynamic, customized response to a client request. Introduction: Application servers An application server is a Java Virtual Machine (JVM) that runs user applications. The application server collaborates with the Web server to return a dynamic, customized response to a client request. The client request can consist of servlets, JavaServer Pages (JSP) files, and enterprise beans, and their supporting classes. For example, a user at a Web browser visits a company Web site: 1. The user requests access to data in a database. 2. The user request flows to the Web server. 3. The Web server determines that the request involves an application containing resources not handled directly by the Web server (such as servlets). It forwards the request to one of its application servers on which the application is running. 4. The invoked application then processes the user request. For example: v An application servlet prepares the user request for processing by an enterprise bean that performs the database access. v The application produces a dynamic Web page containing the results of the user query. 5. The application server collaborates with the Web server to return the results to the user at the Web browser. When you install the product, a default application server, named server1, is automatically created. You can use the administrative console to manage this server. You can use the administrative console or command-line tools to create additional application servers that can either be separately configured processes or nearly identical clones. You must either use command-line tools to manage these additional servers, set up an administrative console for each server, or configure an administrative agent to provide a single interface to all of your servers, including the original base server. An administrative agent makes it easier to more fully administer these unfederated application servers. Note: If you create additional application servers, only use one server to modify and save configurations. There is no coordination of configuration setting between the different servers and if you modify and save configurations on multiple servers, your data might become corrupted. Note: You can improve system performance if you configure some of your application servers, such that each of their components are dynamically started as they are needed, instead of letting all of these components automatically start when the server starts. Selecting this option can improve server startup time, and reduce the memory footprint. Starting components as they are needed is most effective if all of the applications that are deployed on the application server are of the same type. 20 Administering applications and their environment
For example, using this option works better if all of your applications are Web applications that use ervlets, and Java Server Pages(JSP). This option works less effectively if your applications use servlets, JSPs and Enterprise JavaBeans(EJB) You can also perform the following tasks to enhance the operation of an application server: Configure transport chains to provide network protocol support for wo operations within an application server environment Add an interface to an application server to define a hook point that runs when the server starts and shuts down Define command-line information that passes to a server when it starts or initializes Tune the application server. Enhance the performance of the application server JVM Configure an Object Request Broker(oRB)for RMI/IOP communication. Asynchronous messaging The product supports asynchronous messaging based on the Java Message Service (JMS)of a JMS provider that conforms to the JMS specification Version 1.1 The JMs functions of the default message service that is provided with the product are served by one or more messaging engines(in a service integration bus)that runs within application servers Generic Servers a generic server is a server that is managed in the Web Sphere administrative domain, although it is not a server that is supplied by the product. The generic server can be any server or process that is necessary to support the product environment. Chapter 1 Overview and new features: Administering 21
For example, using this option works better if all of your applications are Web applications that use servlets, and JavaServer Pages (JSP). This option works less effectively if your applications use servlets, JSPs and Enterprise JavaBeans (EJB). You can also perform the following tasks to enhance the operation of an application server: v Configure transport chains to provide network protocol support for I/O operations within an application server environment. v Add an interface to an application server to define a hook point that runs when the server starts and shuts down. v Define command-line information that passes to a server when it starts or initializes. v Tune the application server. v Enhance the performance of the application server JVM. v Configure an Object Request Broker (ORB) for RMI/IIOP communication. Asynchronous messaging The product supports asynchronous messaging based on the Java Message Service (JMS) of a JMS provider that conforms to the JMS specification Version 1.1. The JMS functions of the default message service that is provided with the product are served by one or more messaging engines (in a service integration bus) that runs within application servers. Generic Servers A generic server is a server that is managed in the WebSphere administrative domain, although it is not a server that is supplied by the product. The generic server can be any server or process that is necessary to support the product environment. Chapter 1. Overview and new features: Administering 21
Related tasks Creating generic servers a generic server is a server that is managed in the z/OS Application Server administrative domain even though the server is not a server that is supplied by Web Sphere Application Server. The WebSphere Application Server generic servers function enables you to define a generic server as an application server instance within the Web Sphere Application Server administration, and associate it with a non-Web Sphere WebSphere Application server or process Programming to use JMS and messaging directly Use these tasks to implement Web Sphere J2EE applications that use JMS programming interfaces Administering application servers An application server configuration provides settings that control how an application server provides services for running applications and their components Configuring transport chains A transport chain consists of one or more types of channels, each of which supports a different type of vo protocol such as Tcp or Http.nEtworkportscanbesharedamongallofthechannelswithinachain The channel framework function automatically distributes a request arriving on that port to the correct vo protocol channel for processing Creating custom services You can create one or more custom services for an application server. Each custom services defines a class that is loaded and initialized whenever the server starts and shuts down each of these classes must implement the com. ibm websphere runtime. Custom Service interface. After you create a custom service use the administrative console to configure that custom service for your application servers Configuring the JVM As part of configuring an application server, you might define settings that enhance the way your operating system uses of the Java virtual machine (JVM) Tuning application servers The product contains interrelated components that must be harmoniously tuned to support the custom needs of your end-to-end e-business application Managing Object Request Brokers InterORB Protocol(IOP). There are several ways to manage an ORB. For example, you can use oR et An Object Request Broker (ORB)manages the interaction between clients and servers using the interne custom property settings, or system property settings to configure an ORB, or you can provide objects during ORB initialization Introduction Web servers from Web applications. A Web server uses a Web server plug-ins to establish and maintain persisten An application server works with a Web server to handle requests for dynamic content, such as servlet Http and Https connections with an application server The Supported Hardware and Software Web page provides the most current information about supported Web servers Communicating with Web servers describes how to set up your Web server and Web server plug-in environment and how to create a web server definition the web server definition associates a web erver with an application server. After you create a Web server definition, you can use the administrative console to perform the following functions for that Web server Check the status of the web server enerate a plug-in configuration file for that Web server. You can not propagate a plug-in configuration file for a non-lbm Http Server You must manually install an updated plug-in configuration file on that Web server. Administering applications and their er
Related tasks Creating generic servers A generic server is a server that is managed in the z/OS® Application Server administrative domain even though the server is not a server that is supplied by WebSphere Application Server. The WebSphere Application Server generic servers function enables you to define a generic server as an application server instance within the WebSphere Application Server administration, and associate it with a non-WebSphere WebSphere Application server or process. Programming to use JMS and messaging directly Use these tasks to implement WebSphere J2EE applications that use JMS programming interfaces directly. Administering application servers An application server configuration provides settings that control how an application server provides services for running applications and their components. Configuring transport chains A transport chain consists of one or more types of channels, each of which supports a different type of I/O protocol, such as TCP or HTTP. Network ports can be shared among all of the channels within a chain. The channel framework function automatically distributes a request arriving on that port to the correct I/O protocol channel for processing. Creating custom services You can create one or more custom services for an application server. Each custom services defines a class that is loaded and initialized whenever the server starts and shuts down. Each of these classes must implement the com.ibm.websphere.runtime.CustomService interface. After you create a custom service, use the administrative console to configure that custom service for your application servers. Configuring the JVM As part of configuring an application server, you might define settings that enhance the way your operating system uses of the Java virtual machine (JVM). Tuning application servers The product contains interrelated components that must be harmoniously tuned to support the custom needs of your end-to-end e-business application. Managing Object Request Brokers An Object Request Broker (ORB) manages the interaction between clients and servers using the Internet InterORB Protocol (IIOP). There are several ways to manage an ORB. For example, you can use ORB custom property settings, or system property settings to configure an ORB, or you can provide objects during ORB initialization. Introduction: Web servers An application server works with a Web server to handle requests for dynamic content, such as servlets, from Web applications. A Web server uses a Web server plug-ins to establish and maintain persistent HTTP and HTTPS connections with an application server. The Supported Hardware and Software Web page provides the most current information about supported Web servers. Communicating with Web servers describes how to set up your Web server and Web server plug-in environment and how to create a Web server definition. The Web server definition associates a Web server with an application server. After you create a Web server definition, you can use the administrative console to perform the following functions for that Web server: v Check the status of the Web server v Generate a plug-in configuration file for that Web server. You can not propagate a plug-in configuration file for a non-IBM HTTP Server. You must manually install an updated plug-in configuration file on that Web server. 22 Administering applications and their environment
After you set up your Web server and Web server plug-in, whenever you deploy a Web application, you must specify a Web server as the deployment target that serves as a router for requests to the Web application. The configuration settings in the plug-in configuration file(plugin-cfg. xml) for each Web server are based on the applications that are routed through that Web server. If the Web server plug-in configuration service is enabled, a Web server plug-ins configuration file is automatically regenerated whenever a new application is associated with that Web server. Note: Before starting the Web server, make sure you are authorized to run any Application Response Measurement (ARM) agent associated with that Web server Refer to your Web server documentation for information on how to administer that Web server. For tips on tuning your Web server plug-in, see Web server plug-in tuning tips Introduction Environment Your Web Sphere Application Server product environment includes Web server plug-ins, Web Sphere Application Server variables, and other data objects. Configure values for settings in these categories using the Environment section of the administrative console Web servers In the WebSphere Application Server product, an application server works with a Web server to handle requests for Web applications. The application Server and Web server communicate using a WebSphere Http plug-in for the Web server For more information, refer to"Introduction: Web servers"on page 22. Variables Variables come in many varieties. They are used to control settings and properties relating to the server environment. The three main types of variables that are important for you to understand are environment variables, WebSphere variables, and custom properties For more information, refer to"Introduction: Variables"on page 25 Related concepts Introduction: Web servers"on page 22 An application server works with a Web server to handle requests for dynamic content, such as servlets from Web applications. A Web server uses a Web server plug-ins to establish and maintain persistent Http and Https connections with an application server Introduction: Variables"on page 25 Variables come in many varieties. They are used to control settings and properties relating to the server environment. The three main types of variables that you should understand are environment variables Web Sphere variables, and custom properties What is new for scripted administration(wsadmin) This topic highlights what is new or changed, for users who are going to customize, administer, monitor, and tune production server environments using the wsadmin tool Deprecated, stabilized, and removed features describes features that are being replaced or removed in this or future releases Chapter 1 Overview and new features: Administering
After you set up your Web server and Web server plug-in, whenever you deploy a Web application, you must specify a Web server as the deployment target that serves as a router for requests to the Web application. The configuration settings in the plug-in configuration file (plugin-cfg.xml) for each Web server are based on the applications that are routed through that Web server. If the Web server plug-in configuration service is enabled, a Web server plug-in’s configuration file is automatically regenerated whenever a new application is associated with that Web server. Note: Before starting the Web server, make sure you are authorized to run any Application Response Measurement (ARM) agent associated with that Web server. Refer to your Web server documentation for information on how to administer that Web server. For tips on tuning your Web server plug-in, see Web server plug-in tuning tips. Introduction: Environment Your WebSphere Application Server product environment includes Web server plug-ins, WebSphere Application Server variables, and other data objects. Configure values for settings in these categories using the Environment section of the administrative console. Web servers In the WebSphere Application Server product, an application server works with a Web server to handle requests for Web applications. The application Server and Web server communicate using a WebSphere HTTP plug-in for the Web server. For more information, refer to “Introduction: Web servers” on page 22. Variables Variables come in many varieties. They are used to control settings and properties relating to the server environment. The three main types of variables that are important for you to understand are environment variables, WebSphere variables, and custom properties. For more information, refer to “Introduction: Variables” on page 25. Related concepts “Introduction: Web servers” on page 22 An application server works with a Web server to handle requests for dynamic content, such as servlets, from Web applications. A Web server uses a Web server plug-ins to establish and maintain persistent HTTP and HTTPS connections with an application server. “Introduction: Variables” on page 25 Variables come in many varieties. They are used to control settings and properties relating to the server environment. The three main types of variables that you should understand are environment variables, WebSphere variables, and custom properties. What is new for scripted administration (wsadmin) This topic highlights what is new or changed, for users who are going to customize, administer, monitor, and tune production server environments using the wsadmin tool. Deprecated, stabilized, and removed features describes features that are being replaced or removed in this or future releases. Chapter 1. Overview and new features: Administering 23