Improved administrative scripting features Jython script library The Jython script library provides a set of procedures to automate the most administration functions. For example, you can use the script library to easily configure servers, applications, mail settings, resources, nodes, business-level applications clusters, authorization groups, and more. You can run each script procedure individually, or combine several procedures to quickly develop new scripts automate the application serving environment o For more information, see Using the script library to Wildcard pattern usage for the Admin Task help and Use Java regular expression patterns and wildcard Admin Config list command patterns with the Admin Task. help(-commands')command to query for command names and with Admin Config. list, dmin Config types and Admin Config. list Templates functions to query for configuration object types For more information about using pattens with the Admin Task object, see Obtaining online help using For more information about using patterns with the Admin Config object, see Commands for the Admin Config object Complex parameter type support Use primitive and complex Java data types for the parameters of the admin Task commands For more information, see Data types for the Admin Task Admin Task command support for configuring certificate Use the wsadmin tool to manage certificate authority(CA) authority(CA)clients client configurations. Use the commands and parameters in the CAClientCommands group to create, modify, query, and remove connections to a third-party CA server. For more information see CAClientCommands command group for the Admin Task object Admin Task command support for configuring security While security authentication and authorization ensures that users must have access to view protected resources security auditing provides a mechanism to validate the integrity of a security computing environment. Security auditing collects and logs authentication, authorization, system management, security, and audit policy events in audit event records. You can analyze audit event records to determine possible security breaches, threats, attacks, and potential weaknesses in the security configuration of your environment. Enable security auditing in your environment For more information, see Configuring security auditing using scripting 24 Administering applications and their en
Improved administrative scripting features Jython script library The Jython script library provides a set of procedures to automate the most common application server administration functions. For example, you can use the script library to easily configure servers, applications, mail settings, resources, nodes, business-level applications, clusters, authorization groups, and more. You can run each script procedure individually, or combine several procedures to quickly develop new scripts. For more information, see Using the script library to automate the application serving environment. Wildcard pattern usage for the AdminTask help and AdminConfig list commands Use Java regular expression patterns and wildcard patterns with the AdminTask.help(’–commands’) command to query for command names and with AdminConfig.list, AdminConfig.types and AdminConfig.listTemplates functions to query for configuration object types. For more information about using patterns with the AdminTask object, see Obtaining online help using scripting For more information about using patterns with the AdminConfig object, see Commands for the AdminConfig object Complex parameter type support Use primitive and complex Java™ data types for the parameters of the AdminTask commands. For more information, see Data types for the AdminTask object AdminTask command support for configuring certificate authority (CA) clients Use the wsadmin tool to manage certificate authority (CA) client configurations. Use the commands and parameters in the CAClientCommands group to create, modify, query, and remove connections to a third-party CA server. For more information, see CAClientCommands command group for the AdminTask object AdminTask command support for configuring security auditing While security authentication and authorization ensures that users must have access to view protected resources, security auditing provides a mechanism to validate the integrity of a security computing environment. Security auditing collects and logs authentication, authorization, system management, security, and audit policy events in audit event records. You can analyze audit event records to determine possible security breaches, threats, attacks, and potential weaknesses in the security configuration of your environment. Enable security auditing in your environment. For more information, see Configuring security auditing using scripting 24 Administering applications and their environment
Admin Task command support for configuring multiple Create multiple security configurations and assign them to security domains different applications in WebSphere Application Server processes. By creating multiple security domains, you can configure different security attributes for both administrative and user applications within a cell environment. You can configure different applications to use different security configurations by assigning the servers or clusters or SIBuses that host these applications to the security domains Only users assigned to the administrator role can configure multiple security domains For more information, see Configuring multiple security domains using scripting Task command support for configuring A business-level application is an administration model ess-level applications that provides the entire definition of an application as it makes sense to the business. a business-level application is a WebSphere configuration artifact, similar to a server or cluster, that is stored in the product configuration For more information, see Setting up business-level applications using scripting Admin Task command support for managing configurations Manage your system configuration using properties files. ing properties files Use the commands in the Properties Configuration group to copy configuration properties from one environment to another, troubleshoot configuration issues, and to apply one set of configuration properties across multiple profiles, nodes, cells, servers, or applications For more information, see Properties Basedconfiguration command group for the Admin Task object Admin Task command support for configuring proxy Use the commands and parameters in the servers ProxyManagement group to configure proxy servers for For more information, see Proxy Management command group for the Admin Task object Introduction: Variables Variables come in many varieties. They are used to control settings and properties relating to the serve environment. The three main types of variables that you should understand are environment variables, Web Sphere variables, and custom properties Environment variables. Environment variables, also called native environment variables, are not spe to WebSphere Application Server and are defined by other elements, such as UNIX, Language Environment(LE), or third-party vendors, among others. Some of the UNIX-specific native variables are LIBPATH and STEPLIB. These variables tend to be operating system-specific Environment variables can also be specified as an application server environment entry. To specify an environment variable as an environment entry, in the administrative console, click Servers Server Types WebSphere application servers server_name. Then, under Server Infrastructure, click Java process management >Process definition >Environment entries WebSphere variables Web Sphere variables are name and value pairs that are used to provide settings for any of the string data type attributes contained in one of the XML formatted configuration files that reside in the product Chapter 1 Overview and new features: Administering
AdminTask command support for configuring multiple security domains Create multiple security configurations and assign them to different applications in WebSphere Application Server processes. By creating multiple security domains, you can configure different security attributes for both administrative and user applications within a cell environment. You can configure different applications to use different security configurations by assigning the servers or clusters or SIBuses that host these applications to the security domains. Only users assigned to the administrator role can configure multiple security domains. For more information, see Configuring multiple security domains using scripting AdminTask command support for configuring business-level applications A business-level application is an administration model that provides the entire definition of an application as it makes sense to the business. A business-level application is a WebSphere® configuration artifact, similar to a server or cluster, that is stored in the product configuration repository. For more information, see Setting up business-level applications using scripting AdminTask command support for managing configurations using properties files Manage your system configuration using properties files. Use the commands in the PropertiesBasedConfiguration group to copy configuration properties from one environment to another, troubleshoot configuration issues, and to apply one set of configuration properties across multiple profiles, nodes, cells, servers, or applications. For more information, see PropertiesBasedConfiguration command group for the AdminTask object AdminTask command support for configuring proxy servers Use the commands and parameters in the ProxyManagement group to configure proxy servers for Web modules. For more information, see ProxyManagement command group for the AdminTask object Introduction: 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 you should understand are environment variables, WebSphere variables, and custom properties. Environment variables. Environment variables, also called native environment variables, are not specific to WebSphere Application Server and are defined by other elements, such as UNIX, Language Environment® (LE), or third-party vendors, among others. Some of the UNIX-specific native variables are LIBPATH and STEPLIB. These variables tend to be operating system-specific. Environment variables can also be specified as an application server environment entry. To specify an environment variable as an environment entry, in the administrative console, click Servers > Server Types > WebSphere application serversserver_name. Then, under Server Infrastructure, click Java process management > Process definition > Environment entries. WebSphere variables WebSphere variables are name and value pairs that are used to provide settings for any of the string data type attributes contained in one of the XML formatted configuration files that reside in the product Chapter 1. Overview and new features: Administering 25
repository. After a variable is defined, the value specified for the variable replaces the variable name whenever the variable name is encountered during configuration processing WebSphere variables can be used to configure Web Sphere Application Server path names, such as JAVA_HOME, and APP_INSTALL_ROOT Certain cell-wide customization values To create or modify a Web Sphere variable, in the administrative console click Environment WebSphere variables A variable can apply to a node or a server. How the variable is set determines its scope. If the variable is set At the server level, it applies to the entire serve At the node level, it applies to all servers in the node, unless you set the same variable at the server level. In that case, for that server, the setting that is specified at the server level overrides the setting that is specified at the node level Custom properties Custom properties are property settings meant for a specific functional component. Any configuration element can have a custom property. Common configuration elements are cell, node, server, Web container, and transaction service. A limited number of supported custom properties are available and these properties can be set in the administrative console using the custom properties link that is associated with the functional component. For example, to set Web container custom properties, click Servers >Server Types WebSphere application servers server_ name, and then, in the Container settings section, click Web container> Custom properties Custom properties set from the Web container custom properties page apply to all transports that are associated with that Web container; custom properties set from one of the Web container transport chain or Http transport custom properties pages apply only to that specific Http transport chain or Http transport. If the same property is set on both the Web container page and either a transport chain or Http transport page the settings on the transport chain or Http transport page override the settings that are defined for the Web container for that specific transport. Note: You can only specify custom properties for an Http transport that is being used by an application server that is running on a Version 5. 1. x node in a mixed cell environment. Language versions offered by this product This product is offered in several languages, as enabled by the operating platform on which the product is installed The following language versions are available Brazilian Portuguese Chinese(Simplified) Chinese(Traditional) · Czech English Frenc German 26 Administering applications and their environment
repository. After a variable is defined, the value specified for the variable replaces the variable name whenever the variable name is encountered during configuration processing. WebSphere variables can be used to configure: v WebSphere Application Server path names, such as JAVA_HOME, and APP_INSTALL_ROOT v Certain cell-wide customization values To create or modify a WebSphere variable, in the administrative console click Environment > WebSphere variables. A variable can apply to a node or a server. How the variable is set determines its scope. If the variable is set: v At the server level, it applies to the entire server. v At the node level, it applies to all servers in the node, unless you set the same variable at the server level. In that case, for that server, the setting that is specified at the server level overrides the setting that is specified at the node level. Custom properties Custom properties are property settings meant for a specific functional component. Any configuration element can have a custom property. Common configuration elements are cell, node, server, Web container, and transaction service. A limited number of supported custom properties are available and these properties can be set in the administrative console using the custom properties link that is associated with the functional component. For example, to set Web container custom properties, click Servers > Server Types > WebSphere application servers > server_name, and then, in the Container settings section, click Web container > Custom properties Custom properties set from the Web container custom properties page apply to all transports that are associated with that Web container; custom properties set from one of the Web container transport chain or HTTP transport custom properties pages apply only to that specific HTTP transport chain or HTTP transport. If the same property is set on both the Web container page and either a transport chain or HTTP transport page, the settings on the transport chain or HTTP transport page override the settings that are defined for the Web container for that specific transport. Note: You can only specify custom properties for an HTTP transport that is being used by an application server that is running on a Version 5.1.x node in a mixed cell environment. Language versions offered by this product This product is offered in several languages, as enabled by the operating platform on which the product is installed. The following language versions are available: v Brazilian Portuguese v Chinese (Simplified) v Chinese (Traditional) v Czech v English v French v German 26 Administering applications and their environment
Hungarian Japanese Korean Polish Russian Spanish Chapter 1 Overview and new features: Administering
v Hungarian v Italian v Japanese v Korean v Polish v Russian v Spanish Chapter 1. Overview and new features: Administering 27
Administering applications and their er
28 Administering applications and their environment