Environment configuration

Navigate to help topics within this section.

• Administrative console scope settings
  Use this page to specify the level at which a resource is visible on the administrative console page. By changing the value for Scope, you see only the resources that are defined at that scope. The contents of the collection table might change. A resource can be visible in the administrative console collection table at the cell, node, or server scope. For multiple-server products, a resource also can be visible at the cluster scope.
• Application routing order settings
  Use this page to specify whether the Default SIP Application Router (DAR) must rely on the basic application startup order or advanced application routing rules (DAR configuration).
• Application startup order settings
  Use this page to define the order in which Session Initiation Protocol (SIP) requests are routed to applications.
• Bootstrap address collection
  Use this page to manage bootstrap addresses for a foreign cell binding. Multiple bootstrap addresses can enhance the failover support provided by clusters.
• Bootstrap address settings
  Use this page to specify one or more bootstrap addresses for a foreign cell binding. Multiple bootstrap addresses can enhance the failover support provided by clusters.
• CORBA object binding settings
  Use this page to configure a new name binding of a CORBA object binding, or to view or edit an existing CORBA object binding.
• Class loader collection
  Use this page to manage class-loader instances on an application server. A class loader determines whether an application class loader or a parent class loader finds and loads Java class files for an application.
• Class loader settings
  Use this page to configure a class loader for applications that reside on an application server.
• Default application router rule collection
  Use this page to view or modify default application router (DAR) routing rules or import a new DAR configuration file. The DAR is a Session Initiation Protocol (SIP) application router that you can use to select the order in which SIP applications are triggered.
• Default application router rule settings
  Use this page to edit the details of an application router rule.
• EJB binding settings
  Use this page to configure a new enterprise bean (EJB) binding, or to view or edit an existing EJB binding.
• Foreign cell binding collection
  Use this page to manage foreign cell bindings.
• Foreign cell binding settings
  Use this page to configure a foreign cell binding.
• Host alias collection
  Use this page to manage host name aliases defined for a virtual host. An alias is the DNS host name and port number that a client uses to form the URL request for a web application resource.
• Host alias settings
  Use this page to view and configure a host alias.
• Indirect lookup binding settings
  Use this page to configure a new indirect lookup name binding, or to view or edit an existing indirect lookup binding.
• MIME type collection
  Use this page to view and configure multi-purpose internet mail extensions (MIME) object types and their file name extensions.
• MIME type settings
  Use this page to configure a multi-purpose internet mail extensions (MIME) object type.
• Name space binding collection
  Use this page to configure a name binding of an EJB, a CORBA CosNaming NamingContext, a CORBA leaf node object, an object that you can look up using Java Naming and Directory Interface (JNDI), or a constant string value.
• Node installation properties
  Use this page to view read-only installation properties for this node. These properties provide information about the capabilities of the node that are collected during product installation time, such as the operating system name, architecture and version, or WebSphere Application Server product levels that are installed on the node.
• Other context properties settings
  Use this page to specify properties to be passed to the javax.naming.InitialContext constructor for an indirect Java Naming and Directory Interface (JNDI) lookup name binding. Completion of this page is optional. The properties are in addition to the basic properties specified for an indirect namespace binding.
• SIP application router collection
  Use this page to create and delete SIP application routers. The Session Initiation Protocol (SIP) application router allows you to select the order in which SIP applications are run at an initial SIP request.
• SIP application router settings
  Use this page to configure SIP application router container settings. The Session Initiation Protocol (SIP) application router allows you to select the order in which SIP applications are triggered. You can use the default application router (DAR) or specify a custom application router adhering to the SIP Servlet specification.
• Shared library collection
  Use this page to define a list of shared library files that deployed applications can use.
• Shared library settings
  Use this page to make a library file available to deployed applications.
• Specify binding type settings
  Use this page to select the type of namespace binding that you want.
• String binding settings
  Use this page to view or configure a string binding.
• Update the global web server plug-in configuration setting
  Use this page to create or update a global plug-in configuration file. The configuration settings this file contains are based on the topology of the cell that contains the applications servers that use this web server plug-in. The web server plug-in configuration file settings determine whether an application server or the web server handles user requests.
• Virtual host collection
  Use this page to create and manage configurations that each let a single host machine resemble multiple host machines. Such configurations are known as virtual hosts.
• Virtual host settings
  Use this page to configure a virtual host instance.
• WebSphere variables collection
  Use this page to view and change the defined product variables with their values. You can also use this page to create a new variable, or delete an existing variable. These variables are name and value pairs that are used to provide the settings for the string data type configuration attributes that are contained in one of the XML formatted configuration files that reside in the product repository.
• WebSphere variables settings
  Use this page to define the name and value of a WebSphere variable. A WebSphere variable is a name and value pair that is used to provide the setting for one of the string data type attributes contained in one of the XML formatted configuration files that reside in the product repository.
• z/OS location service daemon settings
  In a cell, one location service daemon definition exists for each sysplex node group. A location service daemon process runs on each system that has a node in a sysplex node group in that cell. When a client makes a remote call to an enterprise bean, a location service daemon determines which server or servers are eligible to process the request, and routes the request to the selected server. An example of a system is the z/OS operating system on a logical partition (LPAR).