EPM 11.1.2.1 Deployment Report

In 11.1.2.2 a new feature was added to the Shared Services registry command line utility which allows the generation of a deployment report, I briefly highlighted the new addition in my 11.1.2.2 installation blog.

The report lists out the following information

• EPM Deployment Topology Report

• Logical Web Addresses — all logical Web applications and all Web servers that are configured

• Application Tier Components — the components configured for each EPM Instance in this deployment, including the Web application URL and domain name for each Web application
   
• Database Connections — all databases configured for EPM System products
   
• User Directories — user directories used by EPM System products; configured security providers are listed in the same order as configured in Shared Services
   
• Data Directories — data directories used by EPM System products, indicating the directories that need to be on a shared file system

• EPM Deployment History Report — configuration history of activities on the specified date for each server in the deployment

The report would usually be generated after completing an installation and is useful for keeping a track of the EPM environment, problem solving or just a general understanding of what has been deployed and where.

It is worth nothing this only a summary report and the standard registry report can be run for more detailed information.

This type of report would be beneficial for prior versions and luckily it is available for 11.1.2.1 in the form of patch so I will go through the process of getting up and running with it.

The patch details are “Patch 13530721: Patch for 13530702 EPM System does not provide a report containing deployment information.”

Download the patch from Oracle Support and extract to

<MIDDLEWARE_HOME>\EPMSystem11R1\Opatch

Once the patch has been extracted it can be applied from command line using the following

Change directory to <MIDDLEWARE_HOME>\EPMSystem11R1\Opatch

Windows

opatch.bat apply 13530721 -oh <MIDDLEWARE_HOME>\ EPMSystem11R1-jre MIDDLEWARE_HOME\jdk160_21

e.g.
opatch.bat apply 13530721 -oh E:\Oracle\Middleware\EPMSystem11R1 -jre E:\Oracle\Middleware\jdk160_21

*nix

./opatch apply 13530721 -oh <MIDDLEWARE_HOME>/ EPMSystem11R1-jre <MIDDLEWARE_HOME>/ jdk160_21 -invPtrLoc <MIDDLEWARE_HOME>/ EPMSystem11R1/oraInst.loc

Once the patch has been applied the deployment report can be generated from command line.

Change directory to <MIDDLEWARE_HOME>\user_projects\<instance_name>\bin

Execute the following command

Windows > epmsys_registry.bat report deployment
*nix > epmsys_registry.sh report deployment

EPM services do not have to be running to run the report as the utility communicates directly with the Shared Services Registry relational database.

The report is in html format and once generated it can be found at

<MIDDLEWARE_HOME>\user_projects\<instance_name>\diagnostics\reports\deployment_report.html

e.g.
E:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\deployment_report.html

Please note if the report is run again it will overwrite an existing one so it is probably best to timestamp or archive the report.

In 11.1.2.1 the report is broken down into five sections

Logical Web Addresses

Application Tier Components

In the 11.1.2.1 report the FM cluster names are not displayed as this information is not stored in the Shared Services Registry until 11.1.2.2

Database Connections

User Directories

Data Directories

The 11.1.2.1 report does not contain the deployment history as this only available from 11.1.2.2+ due to the changes in the Shared Services registry.

Even though the 11.1.2.1 report does not contain all the information that is available in the 11.1.2.2 version it is definitely worth considering applying the patch and generating a deployment report for your EPM environment.