Configuring servers with scripting

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.

About this task

After installing the product, you might need to configure additional options for your application server. With the wsadmin tool, you can use the commands for the AdminTask and AdminConfig objects to retrieve configuration IDs and invoke operations on the objects to configure the application server. Alternatively, you can use the script library to perform specific operations to configure your application servers. The scripting library provides a set of procedures to automate the most common application server administration functions. You can run each script procedure individually, or combine several procedures to quickly develop new scripts.

You might need to complete one or more of the following tasks to configure your application server:

Procedure

  • Create servers.
    Use the commands in the ServerManagement command group for the AdminTask object or the AdminServerManagement script library to create a new application server, web server, proxy server, or generic server.
  • Configure a unique HTTP session clone ID for each application server.
    If you require session affinity, use the commands in this topic to configure an HTTP session clone ID for each application server.
  • Configure database session persistence.
    You can use the AdminConfig object to configure database persistence.
  • Configure the Java virtual machine to run in debug mode.
    Use the commands in the ServerManagement command group for the AdminTask object or the configureJavaVirtualMachine script in the AdminServerManagement script library to modify your Java virtual machine (JVM) configuration.
  • Configure EJB containers.
    You can use the AdminConfig object or the configureEJBContainer script in the AdminServerManagement script library to configure Enterprise JavaBeans (EJB) containers in your configuration.
  • Configure the Performance Monitoring Infrastructure.
    You can use the wsadmin tool to configure the Performance Monitoring Infrastructure (PMI) in your environment. PMI enables the server to collect performance data from various product components. PMI provides information about average system resource usage statistics, with no correlation between the data across different components.
  • [AIX Solaris HP-UX Linux Windows]Limit the growth of Java virtual machine log files.
    You can use the AdminConfig object or the configureJavaProcessLogs script in the AdminServerManagement script library to configure the size of JVM log files. JVM logs record events or information from a running JVM.
  • Configure Object Request Broker (ORB) services.
    You can use the AdminConfig object or the configureORBService script in the AdminServerManagement script library to configure an ORB service in your environment. An ORB manages the interaction between clients and servers, using the Internet InterORB Protocol (IIOP). It enables clients to make requests and receive responses from servers in a network-distributed environment.
  • Configure processes.
    You can use the AdminConfig object or the configureProcessDefintion script in the AdminServerManagement script library to configure processes in your application server configuration. Enhance the operation of an application server by defining command-line information for starting or initializing the application server process. Process definition settings define runtime properties such as the program to run, arguments to run the program, and the working directory.
  • Configure the runtime transaction service.
    Use the AdminControl object or the configureTransactionService script in the AdminServerManagement script library to configure transaction properties for servers. The transaction service is a server runtime component that coordinates updates to multiple resource managers to ensure atomic updates of data. Transactions are started and ended by applications or the container in which the applications are deployed.
  • Set port numbers to the serverindex.xml file.
    You can use the AdminConfig object, AdminTask object, or the scripts in the AdminServerManagement script library to modify the port numbers specified in the serverindex.xml file. The end points of the serverindex.xml file are part of different objects in the configuration.
  • Disable components.
    You can use the AdminConfig object or the configureStateManageable script in the AdminServerManagement script library to disable components by invoking operations. This topic describes how to disable the nameServer component of the product. You can modify the examples in this topic to disable other components.
  • Disable the trace service.
    Refer to the topic on disabling trace service for more information.
  • Configure servlet caching.
    You can configure servlet caching with scripting and the wsadmin tool. The dynamic cache service works within an application server JVM, intercepting calls to cacheable objects. For example, it intercepts calls through a servlet service method or a command execute method, and either stores the output of the object to the cache or serves the content of the object from the dynamic cache.
  • Modify variables. Refer to the topic on modifying variables for more information.
  • Increase the Java virtual machine heap size. Refer to the topic for more information.