Installing a standalone JMS
module refers to making the module file known to WebLogic Server. After
you have installed the module, you can start it so that users can begin
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the left
pane of the Console, select Deployments.
Install Application Assistant, locate the module
you want to install, and click Next.
Specify whether you want to target the installation as an
application or a shared library.
In Scope, select whether you want to install the
standalone JMS module globally, to a resource group template, or to a
resource group at the domain or partition level, and click
Select the server instances or clusters to which you want to
deploy the application or module, and click
Note: If you have not created additional Managed
Servers or clusters, you will not see this assistant
Optionally update additional deployment settings. These settings
The deployed name of the module.
How the source files are made available to all targeted
Managed Servers and clusters.
How the deployment plan source files are made available to
all targeted Managed Servers and clusters.
Typically, the default values are adequate.
Review the configuration settings you have specified, and click
Finish to complete the installation.
If you choose to immediately go to the deployment's configuration
screen, select the pages to set additional configuration settings for
the module. If you choose to change this information later, you return
to the Deployments table, which now includes your newly
To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).