Console pages to configure application installations

From the application installation wizard and application settings page, you can configure your application with the administrative console.

Preparing for application installation settings
Use this page to specify an application or module to install.
Preparing for application installation binding settings
Use this page to select whether to view all installation options and to change the existing bindings for you application or module during installation. You can choose to generate default bindings for any incomplete bindings in the application or module or to assign specific bindings during installation.
Select installation options settings
Use this page to specify options for the installation of a Java™ Platform, Enterprise Edition (Java EE) application onto a WebSphere® Application Server deployment target. Default values for the options are used if you do not specify a value. After application installation, you can specify values for many of these options from an enterprise application settings page.
Manage modules settings
Use this page to specify deployment targets where you want to install the modules that are contained in your application. Modules can be installed on the same deployment target or dispersed among several deployment targets.
Client module settings
Use this page to configure a deployed client module.
Client module property settings
Use this page to configure the deployment mode of a deployed client module.
Provide options to compile JavaServer Pages settings
Use this page to specify options to be used by the JavaServer Pages (JSP) compiler.
EJB JNDI names for beans
Use this page to view and modify the Java Naming and Directory Interface (JNDI) names of non-message-driven enterprise beans in your application or module.
Bind EJB business settings
Use this administrative console page to specify Java Naming and Directory (JNDI) name bindings for each enterprise bean with a business interface in an EJB module. Each enterprise bean with a business interface in an EJB module must be bound to a JNDI name. For any business interface that does not provide a JNDI name, or if its bean does not provide a JNDI name, a default binding name is provided. If its bean provides a JNDI name, the default JNDI name for the business interface is provided on its bean JNDI name by appending the package-qualified class name of the interface.
Map default data sources for modules containing 1.x entity beans
Use this page to set the default data source mapping for EJB modules that contain 1.x container-managed persistence (CMP) beans. Unless you configure individual data sources for your 1.x CMP beans, this default mapping applies to all beans within the module.
RAR module settings
Use this page to view and manage a resource adapter (RAR) module that corresponds to a connector module in a deployed application (EAR).
EJB references
Use this page to view and modify the Enterprise JavaBeans (EJB) references to the enterprise beans. References are logical names used to locate external resources for enterprise applications. References are defined in the application's deployment descriptor file. At deployment, the references are bound to the physical location (global Java Naming and Directory Interface (JNDI) name) of the resource in the target operational environment.
Resource references
Use this page to designate how the resource references of application modules map to the actual resources that are configured for the application.
Virtual hosts settings
Use this page to specify virtual hosts for web modules contained in your application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.
Security role to user or group mapping
Use this page to specify the users and groups that are mapped to the security roles that are used with the enterprise application.
JASPI authentication enablement for applications
Use this page to enable or disable Java Authentication SPI (JASPI) authentication for an application or web module, and to specify the name of a JASPI authentication provider to be used for authenticating messages for the application or web module.
User RunAs collection
Use this page to map a specified user identity and password to a RunAs role. This panel enables you to specify application-specific privileges for individual users to run specific tasks using another user identity.
Ensure all unprotected 1.x methods have the correct level of protection
Use this page to verify that the unprotected Enterprise JavaBeans (EJB) Version 1.x methods have the correct level of protection before you map users to roles.
Bind listeners for message-driven beans settings
Use this page to specify bindings for message-driven beans in your application or module.
Map data sources for all 2.x CMP beans
Use this page to set the default data source mapping for EJB modules that contain 2.x container-managed persistence (CMP) beans. Unless you configure individual data sources for your 2.x CMP beans, this default mapping applies to all beans within the module.
Map data sources for all 2.x CMP beans settings
Use this page to map container-managed persistence (CMP) 2.x beans of an application to data sources that are available to the application.
Ensure all unprotected 2.x methods have the correct level of protection
Use this page to verify that the unprotected Enterprise JavaBeans (EJB) Version 2.x methods have the correct level of protection before you map users to roles.
Provide options to perform the EJB Deploy settings (deprecated)
Use this page to specify options for the enterprise bean (EJB) deployment tool. The tool generates code needed to run enterprise bean files. You can specify extra class paths, Remote Method Invocation compiler (RMIC) options, database types, and database schema names to be used while running the EJB deployment tool.
Shared library reference and mapping settings
Use the Shared library references and Shared library mapping pages to associate defined shared libraries with an application or web module. A shared library is an external Java archive (JAR) file that is used by one or more applications. Using shared libraries enables multiple applications deployed on a server to use a single library, rather than use multiple copies of the same library. After you associate shared libraries with an application or module, the application or module class loader loads classes represented by the shared libraries and makes those classes available to the application or module.
Shared library relationship and mapping settings
Use the Shared library relationship and Shared library relationship mapping pages to specify relationship identifiers and composition unit names for shared libraries that modules in your enterprise application reference. When installing your enterprise application, the product creates a composition unit for each shared library relationship in the business-level application that you specified on the Select installation options page of the application installation wizard.
JSP and JSF option settings
Use this page to configure the class reloading of web modules such as JavaServer Pages (JSP) files and to select a JSF implementation to use with this application.
Context root for web modules settings
Use this page to specify the context root for web modules during or after installation of an application onto a WebSphere Application Server deployment target.
Initial parameters for servlets settings
Use this page to specify initial parameters that are passed to the init method of web module servlet filters. You can specify initial parameter values for servlets in web modules during or after installation of an application onto a WebSphere Application Server deployment target. The <param-value> values specified in <init-param> statements in the web.xml file of web modules are used by default.
Environment entries for client modules settings
Use this page to configure the environment entries of application client modules that are deployed as Java archive (JAR) files.
Environment entries for EJB modules settings
Use this page to configure the environment entries of Enterprise JavaBeans (EJB) modules such as entity, session, or message driven beans.
Environment entries for web modules settings
Use this page to configure the environment entries of web modules such as servlets and JavaServer Pages (JSP) files.
Environment entries for application settings
Use this page to configure the environment entries of applications that are deployed as enterprise archive (EAR) files.
Resource environment references
Use this page to designate how the resource environment references of application modules map to remote resources, which are represented in the product as resource environment entries.
Message destination reference settings
If your application uses message-driven beans, use this page to specify the Java Naming and Directory Interface (JNDI) name of the J2C administered object to bind the message destination reference to the message-driven beans. You must map each message destination reference that is defined in your application to an administered object.
Select current backend ID settings
Use this page to select a backend identifier for container-managed persistence (CMP) beans that contain mappings for multiple backend databases.
Provide JNDI names for JCA objects settings
Use this page to configure Java Naming and Directory Interface (JNDI) name values for J2C objects (J2CConnectionFactory, J2CActivationSpec, and J2CAdminObject) in your application or modules. If your application contains an embedded resource archive (RAR) file, specify the name and JNDI name of each JCA connection factory, administered object, and activation specification.
Correct use of the system identity
Use this page to manage the system identity properties for the Enterprise JavaBeans (EJB) method in your application.
Metadata for module settings
Use this page to instruct a Java Platform, Enterprise Edition (Java EE) enterprise bean (EJB) deployment descriptor, web module deployment descriptor, or JCA resource adapter archive (RAR) module to ignore annotations that specify deployment information.
Provide options to perform the web services deployment settings
Use this page to specify options for web services deployment.
Display module build ID settings
Use this page to view the build identifier of a module in a Java Platform, Enterprise Edition (Java EE) enterprise archive (EAR file). The build identifier for a module is shown if the MANIFEST.MF file of a module or application specifies a build identifier.
Preparing for application installation settings
Use this page to specify an application or module to install.
Preparing for application installation binding settings
Use this page to select whether to view all installation options and to change the existing bindings for you application or module during installation. You can choose to generate default bindings for any incomplete bindings in the application or module or to assign specific bindings during installation.
Select installation options settings
Use this page to specify options for the installation of a Java Platform, Enterprise Edition (Java EE) application onto a WebSphere Application Server deployment target. Default values for the options are used if you do not specify a value. After application installation, you can specify values for many of these options from an enterprise application settings page.
Manage modules settings
Use this page to specify deployment targets where you want to install the modules that are contained in your application. Modules can be installed on the same deployment target or dispersed among several deployment targets.
Client module settings
Use this page to configure a deployed client module.
Client module property settings
Use this page to configure the deployment mode of a deployed client module.
Provide options to compile JavaServer Pages settings
Use this page to specify options to be used by the JavaServer Pages (JSP) compiler.
EJB JNDI names for beans
Use this page to view and modify the Java Naming and Directory Interface (JNDI) names of non-message-driven enterprise beans in your application or module.
Bind EJB business settings
Use this administrative console page to specify Java Naming and Directory (JNDI) name bindings for each enterprise bean with a business interface in an EJB module. Each enterprise bean with a business interface in an EJB module must be bound to a JNDI name. For any business interface that does not provide a JNDI name, or if its bean does not provide a JNDI name, a default binding name is provided. If its bean provides a JNDI name, the default JNDI name for the business interface is provided on its bean JNDI name by appending the package-qualified class name of the interface.
Map default data sources for modules containing 1.x entity beans
Use this page to set the default data source mapping for EJB modules that contain 1.x container-managed persistence (CMP) beans. Unless you configure individual data sources for your 1.x CMP beans, this default mapping applies to all beans within the module.
RAR module settings
Use this page to view and manage a resource adapter (RAR) module that corresponds to a connector module in a deployed application (EAR).
EJB references
Use this page to view and modify the Enterprise JavaBeans (EJB) references to the enterprise beans. References are logical names used to locate external resources for enterprise applications. References are defined in the application's deployment descriptor file. At deployment, the references are bound to the physical location (global Java Naming and Directory Interface (JNDI) name) of the resource in the target operational environment.
Resource references
Use this page to designate how the resource references of application modules map to the actual resources that are configured for the application.
Virtual hosts settings
Use this page to specify virtual hosts for web modules contained in your application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.
Security role to user or group mapping
Use this page to specify the users and groups that are mapped to the security roles that are used with the enterprise application.
JASPI authentication enablement for applications
Use this page to enable or disable Java Authentication SPI (JASPI) authentication for an application or web module, and to specify the name of a JASPI authentication provider to be used for authenticating messages for the application or web module.
User RunAs collection
Use this page to map a specified user identity and password to a RunAs role. This panel enables you to specify application-specific privileges for individual users to run specific tasks using another user identity.
Ensure all unprotected 1.x methods have the correct level of protection
Use this page to verify that the unprotected Enterprise JavaBeans (EJB) Version 1.x methods have the correct level of protection before you map users to roles.
Bind listeners for message-driven beans settings
Use this page to specify bindings for message-driven beans in your application or module.
Map data sources for all 2.x CMP beans
Use this page to set the default data source mapping for EJB modules that contain 2.x container-managed persistence (CMP) beans. Unless you configure individual data sources for your 2.x CMP beans, this default mapping applies to all beans within the module.
Map data sources for all 2.x CMP beans settings
Use this page to map container-managed persistence (CMP) 2.x beans of an application to data sources that are available to the application.
Ensure all unprotected 2.x methods have the correct level of protection
Use this page to verify that the unprotected Enterprise JavaBeans (EJB) Version 2.x methods have the correct level of protection before you map users to roles.
Provide options to perform the EJB Deploy settings (deprecated)
Use this page to specify options for the enterprise bean (EJB) deployment tool. The tool generates code needed to run enterprise bean files. You can specify extra class paths, Remote Method Invocation compiler (RMIC) options, database types, and database schema names to be used while running the EJB deployment tool.
Shared library reference and mapping settings
Use the Shared library references and Shared library mapping pages to associate defined shared libraries with an application or web module. A shared library is an external Java archive (JAR) file that is used by one or more applications. Using shared libraries enables multiple applications deployed on a server to use a single library, rather than use multiple copies of the same library. After you associate shared libraries with an application or module, the application or module class loader loads classes represented by the shared libraries and makes those classes available to the application or module.
Shared library relationship and mapping settings
Use the Shared library relationship and Shared library relationship mapping pages to specify relationship identifiers and composition unit names for shared libraries that modules in your enterprise application reference. When installing your enterprise application, the product creates a composition unit for each shared library relationship in the business-level application that you specified on the Select installation options page of the application installation wizard.
JSP and JSF option settings
Use this page to configure the class reloading of web modules such as JavaServer Pages (JSP) files and to select a JSF implementation to use with this application.
Context root for web modules settings
Use this page to specify the context root for web modules during or after installation of an application onto a WebSphere Application Server deployment target.
Initial parameters for servlets settings
Use this page to specify initial parameters that are passed to the init method of web module servlet filters. You can specify initial parameter values for servlets in web modules during or after installation of an application onto a WebSphere Application Server deployment target. The <param-value> values specified in <init-param> statements in the web.xml file of web modules are used by default.
Environment entries for client modules settings
Use this page to configure the environment entries of application client modules that are deployed as Java archive (JAR) files.
Environment entries for EJB modules settings
Use this page to configure the environment entries of Enterprise JavaBeans (EJB) modules such as entity, session, or message driven beans.
Environment entries for web modules settings
Use this page to configure the environment entries of web modules such as servlets and JavaServer Pages (JSP) files.
Environment entries for application settings
Use this page to configure the environment entries of applications that are deployed as enterprise archive (EAR) files.
Resource environment references
Use this page to designate how the resource environment references of application modules map to remote resources, which are represented in the product as resource environment entries.
Message destination reference settings
If your application uses message-driven beans, use this page to specify the Java Naming and Directory Interface (JNDI) name of the J2C administered object to bind the message destination reference to the message-driven beans. You must map each message destination reference that is defined in your application to an administered object.
Select current backend ID settings
Use this page to select a backend identifier for container-managed persistence (CMP) beans that contain mappings for multiple backend databases.
Provide JNDI names for JCA objects settings
Use this page to configure Java Naming and Directory Interface (JNDI) name values for J2C objects (J2CConnectionFactory, J2CActivationSpec, and J2CAdminObject) in your application or modules. If your application contains an embedded resource archive (RAR) file, specify the name and JNDI name of each JCA connection factory, administered object, and activation specification.
Correct use of the system identity
Use this page to manage the system identity properties for the Enterprise JavaBeans (EJB) method in your application.
Metadata for module settings
Use this page to instruct a Java Platform, Enterprise Edition (Java EE) enterprise bean (EJB) deployment descriptor, web module deployment descriptor, or JCA resource adapter archive (RAR) module to ignore annotations that specify deployment information.
Provide options to perform the web services deployment settings
Use this page to specify options for web services deployment.
Display module build ID settings
Use this page to view the build identifier of a module in a Java Platform, Enterprise Edition (Java EE) enterprise archive (EAR file). The build identifier for a module is shown if the MANIFEST.MF file of a module or application specifies a build identifier.