Understanding bootstrap configuration items for the Application Configuration Client

This item defines the Java™ edition of the application. The application can be either a standard or enterprise Java application. Possible values are:

• "j2se" - standard Java application
• "j2ee" - enterprise Java application

If not set, this item defaults to "j2ee".

Default:

application.java.edition=j2ee

This item lists the service URLs of the JMX remote connector server through which the Application Configuration Client accepts incoming connections from remote agents.

The content of the URL determines the type and configuration of the connector server. Only standard edition applications (J2SE) require the use of a JMX Remote Connector Server. Enterprise edition applications (J2EE) are made available for management through the Management EJB (MEJB). Therefore, this setting can be omitted for J2EE applications.

Examples:

service:jmx:rmi://localhost/jndi/rmi://localhost:9999
service:jmx:soap://host:8080
service:jmx:soap+ssl://host:8443

Default:

remote.connector.url=service:jmx:rmi://localhost/jndi/rmi://localhost:9999

This item specifies the name of the application deployment. The meaning of this name depends on the edition of the application.

• In J2EE, this item configures the name of the application as known by the application server
• In J2SE, this item configures the install directory of the application

Examples:

deployment.name=CUSTOMER-01
deployment.name=/usr/DWL/BatchController

Default:

deployment.name=deployment1

Specifies the name of the application runtime instance. The meaning of this name depends on the edition of the application.

• In J2EE, this item configures the name of the cluster node on which the instance runs
• In J2SE, this item configures the convention-based name to reflect the purpose of running the instance

An instance name is not typically required and can be left empty.

Examples:

instance.name=SERVER-01
instance.name=Monthly

Default:

instance.name=