2 Oracle JRF Custom WLST Commands

Oracle JRF (Java Required Files) consists of those components not included in the WebLogic Server installation that provide common functionality for Oracle business applications and application frameworks.

This chapter provides detailed descriptions of custom WLST commands for Oracle JRF, including command syntax, arguments and command examples.

Oracle JRF consists of a number of independently developed libraries and applications that are deployed into a common location. The following components are considered part of Oracle JRF: Oracle Application Development Framework, Oracle Fusion Middleware Audit Framework, Dynamic Monitoring Service, Fabric Common, HTTP Client, Infrastructure Security, Java Object Cache, JMX Framework, JPS, logging, MDS, OJSP.Next, Oracle Web Services, Oracle Web Services Manager, Oracle TopLink, UCP, and XDK.

• Oracle JRF Commands
  The WLST JRF commands let you configure a Managed Server or cluster with Oracle JRF applications and services or to copy the applications and services from one Managed Server or cluster and apply them to another Managed Server or cluster.

Oracle JRF Commands

The WLST JRF commands let you configure a Managed Server or cluster with Oracle JRF applications and services or to copy the applications and services from one Managed Server or cluster and apply them to another Managed Server or cluster.

Use the commands in the following sections to configure Managed Servers with Oracle JRF application.

Based on use with WLST, the commands can be:

• Online - Indicates that the command can only be used when connected to a running server.

• Offline - Indicates that the command can only be used when not connected to a running server.

• Online or offline - Indicates that the command can be used in both situations.

The JRF commands are described in the following sections:

• applyJRF
  This command configures a Managed Server or cluster with Oracle JRF applications and services.
• cloneDeployments
  This command copies the applications and services from Managed Server or cluster and applies them to another Managed server or cluster.

applyJRF

This command configures a Managed Server or cluster with Oracle JRF applications and services.

Use with WLST: Online or Offline

Description

Configures a Managed Server or cluster with Oracle JRF. Managed Servers that are added by product templates during the template extension process do not need to be explicitly configured with JRF using this command.

Use the applyJRF command when additional Managed Servers or clusters are added to a domain after it is initially extended with a product template. The applyJRF command is required any time you add a Managed Server to a JRF-only domain, or if you add a Managed Server that has been configured for JRF to a domain that contains other Oracle products.

Note:

The applyJRF command cannot be used in online mode when Oracle Restricted JRF template is used.

When the applyJRF command is used in offline mode, the Oracle Restricted JRF template is applied successfully. However, a message "You will need to be connected to a running server to execute this command" is displayed; you can ignore this message.

Syntax

applyJRF(target, [domainDir], [shouldUpdateDomain])

Argument	Definition
target	The name of the Managed Server or cluster to be configured with JRF applications and services. A value of an asterisk (*) for the target indicates that all clusters and standalone Managed Servers should be configured with JRF.
domainDir	The absolute path of the WebLogic Server domain.
shouldUpdateDomain	An optional boolean flag that controls how domain updates are carried out. When you set it to true (the default), the function implicitly invokes the following offline commands: readDomain() and updateDomain(), or the online commands: edit(), startEdit(), save(), and activate(). When you set it to false, you must call WLST commands to update the domain.

Example

The following example configures the Managed Server server1 with JRF:

wls:/offline> applyJRF('server1', '/my_path/user_templates/domains/my_domain')

cloneDeployments

This command copies the applications and services from Managed Server or cluster and applies them to another Managed server or cluster.

Use with WLST: Online or Offline

Description

Replicates all deployments targeted to a particular Managed Server or cluster on a second Managed Server or cluster. This command is provided as a convenience to configure a new Managed Server or cluster so that it has the same deployments as a pre-existing Managed Server or cluster.

The cloneDeployments command does not create new Managed Servers, and it does not copy properties other than deployment information to the target Managed Server.

Syntax

cloneDeployments(domain, source, target, [shouldUpdateDomain])

Argument	Definition
domain	The absolute path of the WebLogic Server domain. Ignored if the domain has been read, or if connected in online mode.
source	The name of the Managed Server or cluster from which you want to clone deployments. This must be the name of a valid Managed Server or cluster.
target	The target Managed Server or cluster that will receive the source server's applications and services. The target Managed Server must already exist.
shouldUpdateDomain	An optional boolean flag that controls how domain updates are carried out. When you set it to true (the default), the function implicitly invokes the following offline commands: readDomain() and updateDomain(), or online commands: edit(), startEdit(), save(), and activate(). When you set it to false, you must call WLST commands to update the domain.

Example

The following example replicates the deployments from sourceServer to destinationServer:

wls:/offline> cloneDeployments( '/my_path/user_templates/domains/my_domain',
 'sourceServer','destinationServer', 'false')