B Using PARDeploy Utility

This appendix introduces you to the PARDeploy utility and explains how you can use it to perform critical tasks such as exporting Deployment Procedures, importing PAR files, and so on. In particular, this appendix covers the following:

• Overview of Provisioning Archive (PAR) Files

• Overview of PARDeploy Utility

• Checking Oracle Software Library

• Exporting Deployment Procedures

• Importing PAR Files

Overview of Provisioning Archive (PAR) Files

Provisioning Archive (PAR) files are archive files that contain one of the following:

• Deployment Procedures and the associated Oracle Software Library (Software Library) entities, such as components, directives, images, and so on.

• Only the Software Library entities, such as components, directives, images, and so on.

When you install Enterprise Manager Grid Control, by default, all Deployment Procedures are installed in the form of Provisioning Archive (PAR) files at the following location:

$ORACLE_HOME/sysman/prov/paf

For example, all application server-related Deployment Procedures are stored in asprov.par file.

To use the Deployment Procedures in Enterprise Manager Grid Control, you need not have to import or export these PAR files. The only prerequisite is to set up Oracle Software Library (Software Library). Once you set up the Software Library, Enterprise Manager Grid Control will automatically extract the contents of these default PAR files and configure them so that you can start using the Deployment Procedures from the Grid Control console.

Overview of PARDeploy Utility

Over a period of time, you might have customized some Deployment Procedures, and you might want to reuse them in another instance of Enterprise Manager Grid Control. Under such circumstances, you might want to export the customized Deployment Procedures from one instance of Enterprise Manager Grid Control, and deploy them to another instance of Enterprise Manager Grid Control.

PARDeploy utility is a tool offered by Enterprise Manager Grid Control that helps you perform these functions using the command line interface. Essentially, PARDeploy utility helps you:

• Export Deployment Procedures and its associated components and directives as PAR files

• Import PAR files to the same instance or any other instance of Enterprise Manager Grid Control

PARDeploy utility is located in the $ORACLE_HOME/bin directory, and the PAR files are located at $ORACLE_HOME/sysman/prov/paf.

The following is the usage information displayed when you run $ORACLE_HOME/bin/PARDeploy:

PARDeploy -action <deploy|view> -parFile <file> -force(optional)
PARDeploy -action <deploy|view> -parFile <file> -force(optional) -ssPasswd <password>
PARDeploy -action <deploy|view> -parDir <dir> -force(optional)
PARDeploy -action export -guid <procedure guid> -file <file>      -displayName <name> -description <desc> -metadataOnly(optional)
PARDeploy -check
PARDeploy -help 

Additionally, the following options are provided:

Table B-1 PARDeploy Options

Option	Description
-force	Forces the Software Library entities to be created or uploaded again. If already present, it creates a new revision.
-check	Checks whether the Software Library is configured.
-file <file>	Represents the PAR file.
-action <deploy|view|export>	Deploys, views, or exports PAR files.
-verbose	Indicates verbose mode.
-help	Displays Help information.
-displayName <displayName>	Indicates PAR file name.
-parDir <dir>	Directory where the PAR files are located.
-metadataOnly	Flag for metadata-only exports.
-guid <guid>	Procedure GUID to export. To export multiple procedures, provide the GUIDs separated by ","
-parFile <file>	Path to the PAR file.
-description <description>	PAR file description.
-ssPasswd <secretStorePassword>	This is optional. If used with -action export; if any of the exported Software Library entity contains a secret property, an Oracle Wallet is created to store the value of the secret property. Oracle Wallet is created using the specified password. You are prompted to enter a password if -ssPasswd switch is used and if password is not supplied as a command line argument. You must use the same password while importing the PAR file in a new repository. If used with -action <deploy|view>; if the PAR file contains any password protected Oracle Wallet (that stores an entity's secret property values), then this parameter is required to open the store. You are prompted to enter a password if -ssPasswd switch is used and password is not specified as a command line argument.

Checking Oracle Software Library

Before running the PARDeploy utility to export or import PAR files, ensure that the $ORACLE_HOME environment variable is set to the Oracle home directory of Oracle Management Service (OMS) and a Software Library path is configured.

To check the Software Library, run the following command:

$ORACLE_HOME/bin/PARDeploy -check

Exporting Deployment Procedures

To export Deployment Procedures, you must first obtain the GUID of those Deployment Procedures, and then run the PARDeploy utility to create a PAR file. This section explains the following:

• Obtaining Deployment Procedure's GUID

• Creating PAR File

Obtaining Deployment Procedure's GUID

To obtain the GUID of a Deployment Procedure using Enterprise Manager Grid Control, follow these steps:

1. In Grid Control, click the Deployments tab.

2. On the Deployments page, from the Deployment Procedure Manager section, click Deployment Procedures.

3. Deployment Procedure Manager page, in the Procedures table, click the deployment procedure you want to export.

4. On the View Procedure page, note the URL of the page from the address bar of the browser.

   The format of the URL should be similar to this:

   http://<OMS host>:<port>/em/console/paf/procedureView?guid=<value of GUID>

To obtain the GUID of a Deployment Procedure using Enterprise Manager Command Line Interface (EM CLI), run the get_procedures verb. This command displays information such as GUID, Procedure Type, Name, Version, and Created By.

emcli get_procedures [-type={procedure type}]

[ ] denotes that the parameter is optional. If you do not provide this paramaeter, then the verb displays information about all the Deployment Procedures. If you provide this parameter, then the verb displays information only about the procedure type you have specified.

Creating PAR File

To create a PAR file that contains one or more Deployment Procedures, run the PARDeploy utility with the export option as the action, and quote the GUIDs of the Deployment Procedures you want to export. Ensure that you separate the GUIDs by a comma.

$ORACLE_HOME/bin/PARDeploy -action export -guid <GUID> -file exportedDP.par -displayName "User exported DP" -description "<description>"

For example, if the GUID of the Deployment Procedure that you want to export is FAC05DD31E3791C3E030579D23106C67, then run the following command:

$ORACLE_HOME/bin/PARDeploy -action export -guid FAC05DD31E3791C3E030579D23106C67 -file exportedDP.par -displayName "User exported DP" -description "Deployment Procedure to be copied to other OMS"

After you run this command, a new PAR file named exportedDP.par is created in the directory where you ran the command. You can then import this PAR file to the same instance of Enterprise Manager Grid Control or another instance, multiple times.

Note:

When a procedure is exported using PARDeploy, any directives or components referred by the procedure are also exported. However, only the latest revision of these directives or components will be exported. If you do not want to export components or directives, you can specify the -metadataOnly flag when running PARDeploy.

Importing PAR Files

You can import PAR files using the command line interface or the graphical user interface offered by Enterprise Manager Grid Control, that is, the console. This section explains the following:

• Importing Using Command Line Interface

• Importing Using Grid Control Console

Importing Using Command Line Interface

This section covers the following:

• Importing Specific PAR File

• Importing All PAR Files

Importing Specific PAR File

To import or deploy a specific PAR file, run the following command:

$ORACLE_HOME/bin/PARDeploy -action deploy -parFile $ORACLE_HOME/sysman/prov/paf/<par_file_name> -force

For example:

$ORACLE_HOME/bin/PARDeploy -action deploy -parFile $ORACLE_HOME/sysman/prov/paf/asprov.par -force

Note:

If you have multiple OMSes in your environment, then you need run the PARdeploy utility only once to deploy any PAR files or to perform other related operations.

Importing All PAR Files

To import or deploy all the PAR files in a directory, run the following command:

$ORACLE_HOME/bin/PARDeploy -action deploy -parDir $ORACLE_HOME/sysman/prov/paf/ -force

Importing Using Grid Control Console

To import PAR files or deploy them to an OMS, you can use the PARDeploy utility. Alternatively, you can also log in to Enterprise Manager Grid Control, navigate to the Deployment Procedure Manager page, and click Upload to upload a PAR file.

Note:

When importing or exporting components and/or directives that contain properties with secret values, you must use the -ssPasswd command and provide the secret store password to create Oracle Wallet. This ensures that the properties with secret values are securely stored using an Oracle Wallet, and can be accessed while importing with only the Oracle Wallet password.

For more information about the -ssPasswd command, see Table B-1, "PARDeploy Options". For more information about importing and exporting Software Library entities, see Exporting and Importing Entities Across Oracle Enterprise Manager Deployments.