Application scoped resources Use this page to view brief descriptions of the resources
that are bundled with your application. You can view individual resource
settings by clicking the resource name.
Available resources Use this page to select configured resources that you want
to bind to the resource references of the enterprise beans or web
modules in your application.
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 top of its bean JNDI name by appending the package-qualified
class name of the interface.
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.
Correct use of the system identity Use this page to manage the system identity properties
for the Enterprise JavaBeans (EJB)
method in your application.
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 identifer.
Download SQLJ profile group Use this panel to download the group file for the Structured
Query Language in Java (SQLJ)
profiles that are bound together as a single package on the DB2 database server. You can use
the file when performing future customization or binding work on the
application. Click the link that is provided to download the profile
group to your local file system. The group file has a filename extension
of .grp and a HTTP Content-Type of text/plain.. Your web browser
settings might cause the browser to display the file contents rather
than prompting you for a download destination. If this happens, you
can manually copy and paste the contents into your own .grp file.
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.
EJB module settings Use this page to configure and manage a specific deployed
EJB module.
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.
EJB timer service settings Use this page to configure and manage the Enterprise JavaBeans (EJB) timer service
for a specific EJB container.
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.
Extended data source properties Use this page to set the extended data source properties
for a DB2 database. You can use these properties to
allow an application to extend the custom properties for a data source
or override any non-core properties that already exist for that data
source.
Global deployment settings Use this page to manage settings that apply to all applications
or to a subset of application types.
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.
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.
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.
Library reference collection Use this page to view and manage library references that
define how to use global libraries. For example, you can use this
page to associate shared library files with a deployed application.
Library reference settings Use this page to define library references, which specify
how to use global libraries.
Look up users Use this page to select and to map users, groups and special
subjects for security roles.
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.
Map data sources for all 1.x CMP beans Use this page to designate how the container-managed persistence
(CMP) 1.x beans of an application map to data sources that are available
to the application.
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 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.
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.
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.
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.
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.
Provide options to perform the EJB Deploy settings 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.
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).
Remote dispatcher property settings Use this page to configure the sending of include requests
between the application and remote resources.
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.
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.
Review results Use this panel to review the results from the customization
and binding process for the Structured Query Language in Java (SQLJ) profiles or pureQuery bind files.
Use SQLJ or IBM Optim PureQuery Runtime to develop data access
applications that connect to DB2 databases.
SQLJ is a set of programming extensions that enable a programmer to
use the Java programming language
to embed statements that provide SQL (Structured Query Language) database
requests. IBM Optim PureQuery Runtime provides an alternate
set of APIs that can be used instead of JDBC to access the DB2 database.
SQLJ profiles and pureQuery bind files settings Use this page to do customization and binding for the Structured
Query Language in Java (SQLJ) profiles for DB2 that
are included in this application. You can also use this page to do
binding for pureQuery bind files in the application. You can view
SQLJ profiles for other database types, but you cannot change these
profiles. PureQuery bind files are only valid for DB2. Use
SQLJ or pureQuery to develop data access applications that connect
to DB2 databases. SQLJ is a set of programming extensions
that enable a programmer to use the Java programming
language to embed statements that provide SQL database requests. PureQuery
provides an alternate set of APIs that can be used instead of JDBC
to access the DB2 database.
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.
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.
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.
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.
Startup behavior settings Use this page to configure when an application starts compared
to other applications and to the server, and to configure whether
MBeans for resources are created when an application starts.
Stateful session beans failover settings (EJB modules) Each Enterprise JavaBeans (EJB)
container provides a method for stateful session beans to fail over
to other servers. Use this method to specify whether failover occurs
for the stateful session beans in this module. You can also override
the stateful session bean replication settings of the parent object
for this module.
Stateful
session beans failover settings (applications) Each Enterprise JavaBeans (EJB)
container provides a method for stateful session beans to fail over
to other servers. Use this method to specify whether failover occurs
for the stateful session beans in this application. You can also override
the stateful session bean failover settings on a particular module.
Task settings Use this page to modify task settings.
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.
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.
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).