WebSphere

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Scope

Specifies the scope in which the mail provider supports installed mail applications.For example, 'Cell=Cell01,Node=Node01,Server=server1' or 'Cell=Cell01,ServerCluster=testCluster'

Mail Provider Name

Specifies the name to be given to the new mail provider .

Mail Provider Description

Specifies the mail provider description.

Isolate this mail provider?

Specifies that this mail provider will be loaded in its own class loader. This allows the application server to load different versions or implementations of the same mail provider in the same Java Virtual Machine. Give each version or implementation of the mail provider a unique class path in following (Mail provider classpath) field that is appropriate for that version or implementation.

Mail Provider Classpath

Specifies the class path to a Java archive (JAR) file that contains the implementation classes for this mail provider.

Custom Property Name

Specifies the name of custom property to create.

Custom Property Value

Specifies the value to associate with this custom property of the resource.

Protocol Provider Name

Specifies the name to be given to the new protocol provider .

Protocol Provider Class Name

Specifies the implementation class of this protocol provider.

Protocol Provider Type

Specifies the type of protocol provider. Valid options are STORE(for incoming protocol provider) or TRANSPORT(for outgoing protocol provider).

Mail Session Name

Specifies the administrative name of the JavaMail session object.

Mail Session JNDI Name

Specifies the Java Naming and Directory Interface (JNDI) name for the resource, including any naming subcontexts.

Category

Optional string to use while classifying or grouping the resources.

Enable Debug Mode?

Select to print the interaction between mail application and mail server as well as the properties of this mail session to System.Out.log file.

Mail Session Description

Specifies optional description for mail session.

Incoming Mail Server

Specifies the host name server that is accessed when receiving mail.

Incoming Mail Server Port

Specifies the port of the server that is accessed when receiving mail.

Incoming Mail Server Credentials

Specifies the credential for the mail account when the incoming mail server requires authentication.

Outgoing Mail Server

Specifies the host name of server that is accessed when sending mail.

Outgoing Mail Server Port

Specifies the port of the server that is accessed when sending mail.

Outgoing Mail Server Credential

Specifies the user of the mail account when the outgoing mail server requires authentication.

Enable Strict Internet Address Parsing?

Specifies whether the recipient addresses must be parsed in strict compliance with RFC 822.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Scope

Specifies the scope in which the mail session supports installed mail applications.For example, 'Cell=Cell01,Node=Node01,Server=server1' or 'Cell=Cell01,ServerCluster=testCluster'

Mail Session Name

Specifies the administrative name of the JavaMail session object.

Mail Session Description

Specifies optional description for mail session.

Mail Session JNDI Name

Specifies the Java Naming and Directory Interface (JNDI) name for the resource, including any naming subcontexts.

Category

Optional string to use while classifying or grouping the resources.

Enable Debug Mode?

Select to print the interaction between mail application and mail server as well as the properties of this mail session to System.Out.log file.

Outgoing Mail Server

Specifies the host name of server that is accessed when sending mail.

Outgoing Mail Server Port

Specifies the port of the server that is accessed when sending mail.

Outgoing Mail Server Protocol

Specifies the protocol to use when sending mail.

Outgoing Mail Server Credential

Specifies the user of the mail account when the outgoing mail server requires authentication.

Return E-mail Address

Represents the Internet email address that, by default, displays in the received message in the From or the Reply-To address. The recipient’s reply will come to this address.

Incoming Mail Server

Specifies the host name server that is accessed when receiving mail.

Incoming Mail Server Port

Specifies the port of the server that is accessed when receiving mail.

Incoming Mail Server Protocol

Specifies the protocol to use when receiving mail.

Incoming Mail Server Credentials

Specifies the credential for the mail account when the incoming mail server requires authentication.

Enable Strict Internet Address Parsing?

Specifies whether the recipient addresses must be parsed in strict compliance with RFC 822.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Name of the application of which to publish the WSDL file. i.e: 'webapp'.

Location to publish WSDL file

Filename and absolute path on the filesystem where published WSDL files should get stored.For example, 'C:/webservices/sampleWSDL.zip'

Commands

Commands to be entered to wsadmin. Use one command per line.

Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'.

SOAP address prefixes

Give SOAP address prefix in format "{{module {{binding partial-url}}}}" to customize the WSDL SOAP address for each module. For example, '{ {AddressBookJ2WB.war {{http http://localhost:9080}}} {StockQuote.jar {{http https://localhost:9443}}} }'.

Additional Commands

Additional commands to be entered for wsadmin.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Node Name

Name of the node where application server is to be created.

Server Name

Name of application server to be created.

Generate Unique Ports?

By default ports generated during server creation will be created uniquely. If not checked ports in template will be used as is for server creation.

Source Type

Type of source which should be used for server creation. Select Template or Application Server. In case of template, application server template will be used for server creation, in case of Application Server, template will be created from existing application server and new server will be created from this template then. After successful creation template will be deleted.

Source Template Name

This parameter is applicable only when the source is a Template. Name of server template to be the source for a new server.

Source Template Location

The configuration Id that represents the location of a template. This parameter is applicable only when the source is a Template.

Source Server Name

Name of application server to be the source for a new server in format nodename:servername.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Node Name

Name of the node where application server to be deleted.

Server Name

Name of application server to be deleted.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Node Name

Name of the node where application server is located.

Application Server Name

Name of the application server the template will be based out of.

Template Name

Application server template name to be created.

Template Location

Specifies a configuration Id that represents the location to place the template.

Template Description

Description of application server template.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Template Name

Application server template name to be deleted.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

Name of the new cluster.

Prefer Local?

Specifies whether enterprise bean requests are routed to the node on which the client resides whenever such a routing is possible.

Create First Cluster Member?

If not checked, empty cluster will be created

First Cluster Member Creation Policy

Controls how 1st cluster member is to be created Existing - use existing server as template Convert - convert existing server to 1st cluster member Template - use app server template to create 1st cluster member

Source Template Name

Name of server template to be the source for first cluster member.

Source Server Name

Name of application server to be the source for a new server in format nodename:servername.

First Cluster Member Node

Node name where first cluster member will be created.

First Cluster Member Name

Name of the server that will be created as a first cluster member.

First Cluster Member Weight

Weight of first cluster member.

Generate Unique Ports for First Cluster Member?

By default ports generated during for first cluster member creation will be created uniquely. If not checked ports in template will be used as is for server creation.

Server Resources Promotion Policy

Specifies how resources such as data sources are initially created in the cluster. Create settings at the cluster scope if the settings can be used across the entire cluster. Otherwise, create settings at the cluster member (server) level. Creating settings at the cluster scope reduces the amount of configuration that you maintain. Default is Cluster.

Add Cluster Members?

If checked, additional cluster members will be added right after cluster creation.

Gen Unique Ports for Cluster Members?

By default ports generated during cluster members creation will be created uniquely. If not checked ports in template will be used as is for server creation.

Weight of Each Cluster Member

Weight of each cluster member from list.

Cluster Members List

List of cluster members to be created in format NodeName:server1, NodeName2:server2.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

The name of the cluster to delete.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Node Name

Name of application server node.

Application Server Name

Name of the application server to be exported.

Archive

Specifies the fully qualified path of the exported configuration archive.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Node Name

Name of the Node in which the Application Server is to be Imported.

Application Server Name

Name of the Application Server to be created based on the server in the Imported Archive.

Archive

Specifies the fully qualified path of the configuration archive.

Node Name in Archive

Specifies the node name of the server defined in the configuration archive. Not required if there is only one Node in the Archive to be imported. If there are multiple nodes in the Archive, mention the node name of the Server to be imported.

Server Name in Archive

Specifies the name of the server defined in the configuration archive. Not required if there is only one Server in the Archive to be imported. If there are multiple servers in the Archive, mention the name of the Server to be imported.

Core Group

Specifies the core group name to which the server should belong.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

Name of the cluster of which members to list down.

Output Property Path

Property where cluster members list is to be stored.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

Name of cluster from which to remove/delete the members.

List of Cluster Members

List of cluster members in the form Node01:server1, Node02:server2 to remove/delete from cluster. Important note: server will be not only removed from cluster, but also deleted.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Cell Name

Name of cell to which EJB container belongs to.

Node Name

Name of node to which EJB container belongs to.

Server Name

Name of application server to which EJB container belongs to.

Passivation Directory

Specifies the directory into which the container saves the persistent state of passivated stateful session beans. This directory must already exist. It is not automatically created.Default is ${USER_INSTALL_ROOT}/temp.

Cache Size

Number of buckets in the active instance list within the EJB container.Input value range - greater than 0. The container selects the next largest prime number equal to or greater than the specified value.Default is 2053

Cleanup Interval

Interval (in milliseconds)at which the container attempts to remove unused items from the cache.Default is 3000. Allowed range is 0 to 2147483647

Inactive Pool Cleanup Interval

Specifies the interval at which the container examines the pools of available bean instances to determine if some instances can be deleted to reduce memory usage.

Enable stateful session bean fail over using memory-to-memory replication?

Specifies that failover is enabled for all stateful session beans installed in this EJB container.Replication domains must already exist to failover feature to work.

Replication domain

Specifies the replication domain in which HTTP sessions are replicated.

Replication Mode

The mode specifies whether data is only sent (client), only received (server), or both. Select client if sessions need to be replicated. Select server if sessions need to be stored. Select both client and server if sessions need to be replicated and stored. The default is both.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

Name of the new cluster.

First Cluster Member Name

Server Name of first cluster member.

First Cluster Member Node

Node Name of first cluster member.

First Cluster Member Weight

Weight of first cluster member.

Generate Unique Ports for First Cluster Member?

By default the port generated for first cluster member will be created uniquely. If this option is not checked, ports in template will be used as is.

Server Resources Promotion Policy

Specifies how resources such as data sources are initially created in the cluster. Create settings at the cluster scope if the settings can be used across the entire cluster. Otherwise, create settings at the cluster member (server) level. Creating settings at the cluster scope reduces the amount of configuration that you maintain. Default is Cluster.

First Cluster Member Creation Policy

Controls how first cluster member is created. The values mean the following. Existing - Use existing server Template - Use app server template to create first cluster member

Source Template Name

Name of server template to be the source for first cluster member.

Source Server Name

Name of application server to be the source for a new server in format nodename:servername.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

A name of the cluster where servers is to be created.

Gen Unique Ports?

Generate unique ports number if checked.

Cluster Member Weight

Weight of each cluster member

List of Cluster Members

List of cluster members.

Sync Nodes?

The syncNode command forces a configuration synchronization to occur between the node and the deployment manager for the cell in which the node is configured.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Server List

List of Servers to be started. Provide them in this format : NodeName:ServerName. For example, Node1:Server1, Node2:Server2, Node3:Server3, or Node4:* to start all servers within Node4.

Wait time

Not Required. Time to wait until all servers are started. If not specified wait time will be treated as 0.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Server List

List of Servers to be stopped. Provide them in this format : NodeName:ServerName. For example, Node1:Server1, Node2:Server2, Node3:Server3, or Node4:* to stop all servers within Node4.

Wait time

Not Required. Time to wait until all servers are stopped. If not specified wait time will be treated as 0.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

Name of the cluster to be started.

Timeout

Specifies the waiting time before cluster start times out and returns an error.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Cluster Name

Name of the cluster to be stopped.

Timeout

Specifies the waiting time before cluster stop times out and returns an error.

Perform Ripple Start?

If checked, all servers within cluster will be stopped one-by-one and then started.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

StartManager Location

Absolute Physical path in Filesystem to location of startManager script i.e., /path/to/startManager.sh or startManager.bat

Deployment Manager Profile

Profile name of the DeploymentManager which needs to be started. If this is not provided StartManager will start the DeploymentManager which has the default profile.

Log File Location

Absolute Physical path in Filesystem to location of startManager.sh logs i.e., /path/to/startServer.log

Timeout

Specifies the waiting time before deployment manager start times out and returns an error.

Additional Parameters

This parameter can be used to either override defaults or pass Custom Properties. For example: -quiet, -nowait, -help.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

StopManager Location

Absolute Physical path in Filesystem to location of stopManager script i.e., /path/to/stopManager.sh or stopManager.bat

Deployment Manager Profile

Profile name of the DeploymentManager which needs to be stopped. If this is not provided StopManager will stop the DeploymentManager which has the default profile.

Log File Location

Absolute Physical path in Filesystem to location of stopManager.sh logs i.e., /path/to/stopServer.log

Timeout

Specifies the waiting time before deployment manager stop times out and returns an error.

Additional Parameters

This parameter can be used to either override defaults or pass Custom Properties. For example: -quiet, -nowait, -help.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

StartNode Location

Absolute Physical path in Filesystem to location of startNode script i.e., /path/to/startNode.sh or startNode.bat

Node Profile

Profile name of the Node which needs to be started. If this is not provided StartNode will start the Node which has the default profile.

Log File Location

Absolute Physical path in Filesystem to location of startNode.sh logs i.e., /path/to/startServer.log

Timeout

Specifies the waiting time before node start times out and returns an error.

Start all Application Servers?

Start all application servers within node after nodeagent is started.

Node Name to start Servers

Name of the node where application servers needs to be started.

Additional Parameters

This parameter can be used to either override defaults or pass Custom Properties. For example: -quiet, -nowait, -help.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

StopNode Location

Absolute Physical path in Filesystem to location of stopNode script i.e., /path/to/stopNode.sh or stopNode.bat

Node Profile

Profile name of the Node which needs to be stopped. If this is not provided StopNode will stop the Node which has the default profile.

Log File Location

Absolute Physical path in Filesystem to location of stopNode.sh logs i.e., /path/to/stopServer.log

Timeout

Specifies the waiting time before node stop times out and returns an error.

Node Stop Policy

Policy that will be used for node stopping. It could be one of: Just Stop node agent, stop Spplication Servers, Save Node State.

Additional Parameters

This parameter can be used to either override defaults or pass Custom Properties. For example: -quiet, -nowait, -help.

StartServer Absolute Path

Absolute path of the start server script, including filename and extension. i.e: 'startServer.bat' or '/path/to/startServer.sh' or 'C:\Program Files\IBM\WebSphere\AppServer\bin\startServer.bat'.

Instance name

The name of the instance of the server to be started. i.e: 'server01'.

Additional Commands

Additional commands to be entered for the startup of the server.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Script Location

Absolute path of the stop server script, including filename and extension. i.e: 'C:/Program Files/IBM/WebSphere/AppServer/bin/stopServer.bat', 'stopServer.bat', '/path/to/stopServer.sh'

Instance Name

Server instance name of the server to be stopped. i.e: 'server01'.

Additional Commands

Additional commands to be entered for stop the server.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Commands

Commands to be entered to wsadmin. Use one command per line.

Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'.

Script File Absolute Path

Path of a Jython script that will be run using wsadmin. i.e: '/path/to/scriptFile.jython' or 'c:/dir/scriptFile.jython'.

Script File Source

Indicates either if a script file route or an embedded script file will be provided.

Script File

Content of the script file to run if Embedded File is chosen in the Script File Source.

Additional Commands

Additional commands to be entered for wsadmin.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. /path/to/wsadmin.sh or wsadmin.bat.

Application Name

Name of the web application to configure.

Enable SSL Tracking

Specifies that session tracking uses Secure Sockets Layer (SSL) information as a session ID. Enabling SSL tracking takes precedence over cookie-based session tracking and URL rewriting.

Enable Cookies

Specifies whether to enable cookies.

Enable URL Rewriting

Specifies whether the session management facility uses rewritten URLs to carry the session IDs. If URL rewriting is enabled, the session management facility recognizes session IDs that arrive in the URL if the encodeURL method is called in the servlet.

Enable Protocol Switching

This option is only applicable when Enable URL rewriting is selected. This option specifies that the session ID is added to a URL when the URL requires a switch from HTTP to HTTPS or from HTTPS to HTTP. If rewriting is enabled, the session ID is required to go between HTTP and HTTPS.

Max in-memory session count

Specifies the maximum number of sessions to maintain in memory.

Allow Overflow

Specifies whether the number of sessions in memory can exceed the value specified by the Max in-memory session count property. This option is valid only in non-distributed sessions mode..

Enable Serialized Session

If selected, concurrent session access in a given server is not permitted.

Maximum Wait Time

Specifies the maximum amount of time in seconds a servlet request waits on an HTTP session before continuing execution. The default is 5 seconds. Under normal conditions, a servlet request waiting for access to an HTTP session gets notified by the request that currently owns the given HTTP session when the request finishes.

Access Session On Timeout

Specifies whether the servlet is started normally or aborted in the event of a timeout. If you specify true, the servlet is started normally. If you specify false, the servlet execution aborts and error logs are generated.

Invalid Timeout

Specifies how long(in minutes) a session can go unused before it is no longer valid.

Session Persistence Mode

Specifies whether to enable session persistence mode.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Library Name

Shared Library Name.

Application Name

Name of application to which shared library will be mapped.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Load Order

The class-loader delegation mode, also known as the class loader order, determines whether a class loader delegates the loading of classes to the parent class loader.

ClassLoader Isolation Policy

Application class loaders load EJB modules, dependency JAR files, embedded resource adapters, and application-scoped shared libraries. Depending on the application class-loader policy, an application class loader can be shared by multiple applications (Single) or unique for each application (Multiple). The application class-loader policy controls the isolation of applications that are running in the system. When set to Single, applications are not isolated. When set to Multiple, applications are isolated from each other.

Application Name

Name of the existing web application, which ClassLoader should be modified.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Name of the application to start. i.e: 'webapp'.

Cluster Name

Name of the cluster on which application is deployed. Not required in WebSphere Base Edition.

Server Name

Name of the server on which application is deployed. Specify server in the form Node=server. For e.g. Node01=Server1. Not required in WebSphere Base Edition.

Commands

Commands to be entered to wsadmin. Use one command per line.

Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'.

Additional Commands

Additional commands to be entered for wsadmin.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Name of the application to stop. i.e: 'webapp'.

Cluster Name

Name of the cluster on which application is deployed. Not required in WebSphere Base Edition.

Server Name

Name of the server on which application is deployed. Specify server in the form Node=server. For e.g. Node01=Server1. Not required in WebSphere Base Edition.

Commands

Commands to be entered to wsadmin. Use one command per line.

Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'.

Additional Commands

Additional commands to be entered for wsadmin.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

JDBC Provider Name

Name of the JDBC Provider.

JDBC Provider Description

A description for the JDBC Provider.

Cell Scope

Parent object where the JDBC Provider will be created. This determines the visibility scope of the JDBC Provider. When the Cell Scope is provided, if the node and server scopes are not provided, then the scope will be the 'cell'; if the node is provided and the server not, then the scope will be the 'node'; if the server is provided and the node not, then the scope will be the 'server'. At least the Cell, the Node or the Server scope must be provided. i.e: 'wsaspluginNode01Cell'.

Cluster Scope

When the Cluster Scope is provided, then the scope will be the cluster. i.e: 'cluster1'.

Node Scope

When the Node Scope is provided, if the cell and server scopes are not provided, then the scope will be the 'node'; if the cell is provided and the server not, then the scope will be the 'node'; if the server is provided and the cell not, then the scope will be the 'server'. i.e: 'wsaspluginNode01'.

Server Scope

When the Server Scope is provided, then the scope will be the Node and the server always, even if the Node and the Cell Scopes are not provided. i.e: 'server1'.

Implementation Class Name

Java class name of the JDBC provider implementation.

Driver Class Path

A path for the resource provider classes.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

JDBC Provider Name

A unique name that identifies the JDBC Provider to delete in the WebSphere domain.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

JDBC Provider

Name of an existing JDBC Provider.

Datasource Name

A unique name that identifies this Datasource in the WebSphere domain.

Datasource Description

A description for the datasource.

JNDI Name

The JNDI path to where this Datasource is bound.

Statement Cache Size

Specifies the number of statements that can be cached per connection. The application server caches a statement after you close that statement.

Authentication Alias Name

Provide the authentication data alias.

Datasource Helper Class Name

Provide the datasource helper class name.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Datasource Name

A unique name that identifies the datasource to delete in the WebSphere domain.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Scope

Specifies a scope of cell, node, server, or cluster for the JMS provider. E.g. Cell=Cell01,Node=Node01,Server=server1

JMS Provider Name

Specifies the name to assign to the new JMS provider.

Initial Context Factory

Specifies the Java class name of the initial context factory for the JMS provider.

JMS provider URL

Specifies the JMS provider URL for external JNDI lookups.

Classpath

Specifies a list of paths or Java archive (JAR) file names which together form the location for the resource provider classes. Use a semicolon (;) to separate class paths.

Description

Specifies a description of the JMS Provider.

Isolated Class Loader

If set to true, specifies that the resource provider is loaded in its own class loader.

Native Path

Specifies an optional path to any native libraries, such as *.dll and *.so. Native path entries are separated by a semicolon (;).

Provider Type

Specifies the JMS provider type that this JMS provider uses.

Property Set

Specifies resource properties in the following format: [[['name','nameValue1'],['type','typeValue1'],['value','valueValue1']]…​ [['name','nameValuen'],['type','typeValuen'],['value','valueValuen']]]

Supports ASF

If set to true, specifies that the JMS provider supports Application Server Facilities (ASF), which provides concurrency and transactional support for applications.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

JMS Provider Scope

Scope of the WebSphere messaging provider to be deleted.

JMS Provider Administartive Name

The administrative name of JMS Provider to be deleted.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Messaging System Type

The name of the messaging provider. Pass in either WMQ or SIB.

Queue Scope

Scope of the messaging provider at which the JMS Queue is to be created.

Queue Administrative Name

The administrative name assigned to this WebSphere MQ messaging provider queue.

Queue Name

Name of the Queue.

JNDI Name

The name used to bind this object into WebSphere Application Server JNDI.

Queue Manager Name

Queue manager that hosts the queue.

Queue Administrative Description

An administrative description assigned to queue.

Additional Options

This parameter can be used to either override defaults or pass Custom Properties. For example: -ccsid 1208 -readAhead YES

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Messaging System Type

The name of the messaging provider. Pass in either WMQ or SIB.

Queue Scope

Scope of the messaging provider at which the JMS Queue is to be deleted.

Queue Administrative Name

The administrative name assigned to this WebSphere MQ messaging provider queue.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Messaging System Type

The name of the messaging provider. Pass in either WMQ or SIB.

Topic Scope

Scope of the messaging provider at which the JMS Topic is to be created.

Topic Administrative Name

The administrative name assigned to this WebSphere MQ messaging provider Topic.

Topic Name

Name of the Topic.

JNDI Name

The name used to bind this object into WebSphere Application Server JNDI.

Topic Administrative Description

An administrative description assigned to Topic.

Additional Options

This parameter can be used to either override defaults or pass Custom Properties. For example: -readAhead YES -ccsid 1208

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Messaging System Type

The name of the messaging provider. Pass in either WMQ or SIB.

Topic Scope

Scope of the messaging provider at which the JMS Topic is to be deleted.

Topic Administrative Name

The administrative name assigned to this WebSphere MQ messaging provider topic.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Scope of the Activation Spec

Scope of the WebSphere Default messaging provider at which the Activation Spec is to be created.

Activation Spec Administrative Name

The administrative name assigned to this Activation Spec.

JNDI Name

The name and location used to bind this object into WebSphere Application Server JNDI.

Destination JNDI Name

The JNDI name of the destination JMS queue or topic used by the message-driven bean.

Activation Spec Administrative Description

An Administrative description assigned to Activation Spec.

Destination Type

An option to determine whether the message_driven bean uses a JMS queue or a JMS topic.

Message Selector

The JMS message selector used to determine which messages the message-driven bean receives. The value is a string that is used to select a subset of the available messages. The syntax is based on a subset of the SQL 92 conditional expression syntax, as described in the JMS specification. Refer to the information center for more information. The selector string can refer to fields in the JMS message header and fields in the message properties. Message selectors cannot reference message body values. A null value (an empty string) indicates that there is no message selector for the message consumer.

Additional Options

Used to either override defaults or pass Custom Properties.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Scope of the Activation Spec

Scope of the WebSphere MQ messaging provider at which the Activation Spec is to be created.

Activation Spec Administrative Name

The administrative name assigned to this Activation Spec.

JNDI Name

The name and location used to bind this object into WebSphere Application Server JNDI.

Destination JNDI Name

The JNDI name of the destination JMS queue or topic used by the message-driven bean.

Destination JNDI Type

The type of the destination specified by "Destination JNDI Name" parameter.

Activation Spec Administrative Description

An Administrative Description assigned to Activation Spec.

Client Channel Definition URL

A URL to a client channel definition table to use, for this Activation Spec, when contacting WebSphere MQ.

Client Channel Definition Queue Manager

A queue manager name, used to select one or more entries from a client channel definition table.

Additional Options

Used to either override defaults or pass Custom Properties.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Messaging System Type

The name of the messaging provider. Pass in either WMQ or SIB.

Scope of the Activation Spec

Scope of the messaging provider at which the JMS Activation Spec is to be deleted.

Activation Spec Administrative Name

The administrative name assigned to this WebSphere MQ messaging provider Activation Spec.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Scope of the Connection Factory

Scope of the WebSphere Default messaging provider at which the Connection Factory is to be created.

Connection Factory Administrative Name

The administrative name assigned to this Connection Factory.

Bus Name

Name of the service integration bus to which connections are made.

JNDI Name

The name and location used to bind this object into WebSphere Application Server JNDI.

Connection Factory Type

Type of Connection Factory to create. Should be one of Queue or Topic. To create a generic connection factory, leave this parameter unset. This parameter is being used only if Connection Factory is going to be created. Since factory type can’t be updated in existing factory, this parameter will be omited if Connection Factory already exists.

Connection Factory Administrative Description

An Administrative Description assigned to Connection Factory.

Additional Options

Used to either override defaults or pass Custom Properties.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Scope of the Connection Factory

Scope of the WebSphere MQ messaging provider at which the Connection Factory is to be created.

Connection Factory Administrative Name

The administrative name assigned to this Connection Factory.

Connection Factory Type

Use this parameter to determine whether a unified connection factory, a queue connection factory or a topic connection factory is to be created. This needs to be one of the values from CF, QCF and TCF. Default is CF. Since factory type can’t be updated in existing factory, this parameter will be omited if Connection Factory already exists.

JNDI Name

The name and location used to bind this object into WebSphere Application Server JNDI.

Connection Factory Administrative Description

An Administrative description assigned to Connection Factory.

Client Channel Definition URL

A URL to a client channel definition table to use, for this Connection Factory, when contacting WebSphere MQ.

Client Channel Definition Queue Manager

A queue manager name, used to select one or more entries from a client channel definition table.

Additional Options

Used to either override defaults or pass Custom Properties.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Messaging System Type

The name of the messaging provider. Pass in either WMQ or SIB.

Scope of the Connection Factory

Scope of the WebSphere messaging provider at which the Connection Factory is to be deleted.

Connection Factory Administrative Name

The administrative name assigned to this Connection Factory.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Commands

Commands to be entered to wsadmin. Use one command per line.

Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'

Application Name

Name of the web application to be deploy. i.e: 'webapp'.

Application Path

Absolute path of the application to deploy. i.e: '/path/to/webapp.war' or 'c:/mydir/webapp.war'.

Additional Commands

Additional commands to be entered for wsadmin.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Specifies logical name to be given to installing enterprise application. Do not include whitespaces in application name.

Application Path

Absolute path of the application to deploy. Use "/" as the path separator on both linux and windows i.e: '/path/to/webapp.war' or 'c:/mydir/webapp.war'.

Target cluster

Name of the cluster on which to deploy enterprise application. Not required in WebSphere Base Edition. Enter either target cluster or target server(s).

Target server(s)

Specify single or list of standalone application servers on which to deploy enterprise application. Specify servers in the form Node=server. For e.g. Node01=Server1,Node02=Server2. Not required in WebSphere Base Edition.

Map modules to servers

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. Give input in format [ "Module1Name" Module1URL server1][ "Module2Name" Module2URL server2 ] E.g. [ "Increment EJB module" Increment.jar,META-INF/ejb-jar.xml WebSphere:cell=Cell01,node=Node01,server=singleServer ]

Additional deployment parameters

Specify any additional options for AdminApp. Install object in case not listed in this input form. For more information about each of the supported arguments, refer to 'http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rxml_taskoptions.html'.

Directory to install application

Specifies the directory to which the enterprise archive (EAR) file will be installed. Default is profile_root/installedApps/cell_name/application_name.ear directory.

Precompile JavaServer Pages files?

Specify whether to precompile JavaServer Pages (JSP) files as a part of installation. The default is not to precompile JSP files.

Distribute application?

Specifies whether the product expands application binaries in the installation location during installation.

Use binary configuration?

Specifies whether the application server uses the binding, extensions, and deployment descriptors located with the application deployment document, the deployment.xml file (default), or those located in the enterprise archive (EAR) file. Default is to use bindings located in deployment.xml.

Deploy enterprise beans?

Specifies whether the EJBDeploy tool runs during application installation. Default is false(true for EJB 3.0 modules).

Create MBeans for resources?

Specifies whether to create MBeans for resources such as servlets or JSP files within an application when the application starts. Default is create MBeans.

Override class reloading settings for web and EJB modules?

Specifies whether the product run time detects changes to application classes when the application is running. If yes, then on such changes application is stopped and restarted to reload updated classes.

Deploy web services?

Specifies whether to deploy web services. Default is do not enable Deploy web services.

Process embedded configuration?

Specifies whether the embedded configuration should be processed. An embedded configuration consists of files such as resource.xml, variables.xml, and deployment.xml.

Allow EJB reference targets to resolve automatically?

Specifies whether the embedded configuration should be processed.

Deploy client modules?

Select if the file to deploy has one or more client modules and want to configure environment entries for the client modules. Default is do not enable Client Module.

Validate schema?

Specifies whether to validate the deployment descriptors against published Java EE deployment descriptor schemas.

Synchronize active nodes?

Specify whether to synchronize active nodes. Applicable only for Network Deployment installation. Enabled by default.

Start application?

Specify whether to start application or not. Enabled by default.

Reload interval in seconds

Specifies the number of seconds to scan the application’s file system for updated files. Default is 3 seconds.

Validate resource references

Specifies whether websphere examines the application references specified during application installation or updating and, if validation is enabled, warns you of incorrect references or fails the operation.

File permission

Specifies access permissions for application binaries.

Customized file permission

Provide custom file permissions if not listed in File permissions drop down.

Business level application name

Specifies whether websphere creates a new business-level application with the enterprise application that you are installing or makes the enterprise application a composition unit of an existing business-level application. The default is to create a new business-level application.

Client deployment mode

Specifies whether to deploy client modules to an isolated deployment target (Isolated), a federated node of a deployment manager (Federated), or an application server (Server Deployed). Default is Isolated

Wsadmin Commands

Commands to be entered to wsadmin. Use one command per line.

Wsadmin Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'.

Wsadmin Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Wsadmin Additional Arguments

Additional arguements to be passed to wsadmin.

Context root

Applicable only to web applications (WAR). Specifies the context root of the web application (WAR). A context root for each web module is defined in the application deployment descriptor during application assembly. Use this field to assign a different context root to a web module. The context root is combined with the defined servlet mapping (from the WAR file) to compose the full URL that users type to access the servlet. For example, if the context root is /gettingstarted and the servlet mapping is MySession, then the URL is http://host:port/gettingstarted/MySession.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Want to add external bundle repository?

If your OSGi applications reference bundles that are stored in an external bundle repository, you must configure a link (name and URL) to the repository so that the provisioner can retrieve the bundles when required.

External Bundle Repository Name

Name of the external bundle repository to configure.

External Bundle Repository URL

URL of the external bundle repository to configure.

List of bundles to add to local repository

Comma separated list of bundles to add to internal bundle repository.E.g. C:/installableApps/com.ibm.samples.websphere.osgi.logging.api.jar,C:/installableApps/com.ibm.samples.websphere.osgi.logging.impl.jar

EBA file Path

Absolute path of the OSGi application to deploy. i.e: '/path/to/blog.eba' or 'c:/mydir/blog.eba'.

Application Name

Name to be given to newly deployed OSGi application.

Target Deployment Unit

Deployment Unit on which to deploy the OSGi application. For e.g cluster=cluster1 or node=node01,server=server1

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. If the path in which wsadmin is stored in the path environmental variable, the absolute path is ommited. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Name of the application to undeploy. i.e: 'webapp'.

Commands

Commands to be entered to wsadmin. Use one command per line.

Java Parameters

Java options to be passed to wsadmin, separate them using semicolons (;).

Classpath

Jars to be passed to the wsadmin classpath. It is a string containing paths (semicolon-separated) the required JARs to execute wsadmin in a particular job. i.e: 'c:/MyDir/Myjar.jar;d:/yourdir/yourdir.jar' or '/MyDir/Myjar.jar;/yourdir/yourdir.jar'

Additional Commands

Additional commands to be entered for wsadmin.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Name of the web application to be updated. i.e: 'webapp'.

Content Type

Specifies to type of content to update. Use File option for updating a single file, Partial Application option for updating application partially, Module option to add/update a module to the deployed application, Application option for updating the entire deployed application.

Operation

Specifies to type of operation to perform as part of update procedure. Use Add option to add new content, Update option to update existing content, AddUpdate option to add content and to replace if already exist, Delete option to remove existing content respectively.

Content

Specifies the file that contains the content that you want to update. For example, depending on the content type, the file could be an EAR file, a module, a partial zip, or a single file.Not required for Delete operation.

Content URI

The relative path beginning with the installed application archive file to the file to be replaced or added. For example, if the file is located at com/company/greeting.class in module hello.jar, specify hello.jar/com/company/greeting.class for the relative path

Cluster Name

Name of the cluster on which application is deployed.

Server Name

Name of the server on which application is deployed.

Additional Parameters

Additional parameters to pass while updating entire application or module/s, if required. For e.g. -nodeployejb, -BindJndiForEJBNonMessageBinding etc.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Absolute Path

Absolute path of wsadmin, including filename and extension. i.e: '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Application Name

Name of the web application to be checked. i.e: 'webapp'.

Application State Checked

Application State that is being checked, with any applicable retries based on wait time parameter. Any state that is not the desired state after any applicable retries, will be returned as a failure by the procedure.

Wait Time

Maximum duration of check application state retries.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Wsadmin Path

Path to wsadmin. If the location of wsadmin is in the PATH environment variable, then just the script name can be specified omitting its full path. E.g. '/path/to/wsadmin.sh' or 'wsadmin.bat'.

Name of the Node

Name of the Node, which should be checked.

Success Criteria

Conditions that must be met for successful completion of the procedure.

Credentials to be entered

The credentials needed to check the status of the page.

Target URL

URL of the page to be checked.

Maximum Elapsed Time

Defines the maximum time in seconds that the job will try to check into the server. Blank implies no wait time (URL only checked one time).

Success Criteria

Indicates the expected correct result to be obtained when running checking the server.

Configuration Name

Name of the configuration to be used. URL, port and credentials are retrieved from the given configuration.

Maximum Elapsed Time

Defines the maximum time in seconds that the job will try to check into the server. Blank implies no wait time (URL only checked one time).

Success Criteria

Indicates the expected correct result to be obtained when running checking the server.

Configuration Name

The plugin’s configuration name.

Resource Names

List of resources, on which discovery procedure should run. Enter multiple values on separate lines.