How to run Windows Batch scripts from ePM Workspace

In order to run/call windows batch scripts from workspace,we need a generic job which should call the batch scripts.

Hence we need to create one Generic Job in EPM Workspace with cmd.exe to execute .bat files.

Ø  Log in Workspace

    http://hostname:9000/workspace/

Ø  Navigate to Navigate-->Administer-->Reporting and Analysis-->Generic Job Applications

Ø  Click on + symbol to create new Generic Job application

And provide the below details

Product Name: anything

Product Host:epm server host name

Command Template: $PROGRAM $PARAMS

Executable: %WINDIR%\System32\cmd.exe

Now we are good to use CMD (above created Generic Job) in Jobs import.

Import any .bat file and select CMD as the Job Factory Application during the batch file import.

Passing current logged in USERNAME to generic jobs-EPM Workspace

There are some situations where we need to have current logged in username to evaluate the things in the jobs.
For example if you want to do specific operation related to specific user (let say particular user's authorized data from a table) ,you will need the username dynamically from the current session so that you can use that name in the filters to avoid other users data.

Using workspace variable $FIXED_USERNAME, it can be doable.

While importing the job into workspace create a parameter with any name and choose default value as "User $FIXED_USERNAME as default value" option. You will also notice that this parameter will not be displayed when you try running job.

Production Reporting Configuration in Workspace

After the successful EPM configuration then we should be able to launch the workspace using below url.

http://hostname:9000/workspace/

Below are the steps that need to be performed in Workspace in order to work with SQR Production Reporting stuff. 

1.Check if Reporting and Analysis Framework is enabled in workspace ,if not enable it
2.Create Production Reporting Engine
3.Create Production Reporting Database Server

1. Enabling Reporting and Analysis Framework in Workspace

• Navigate to Navigate-->Administer-->Workspace Settings-->Server Settings 
• Open Enabled Products
• Make sure Reporting and Analysis Frame work selected/enabled
• If not selected, then select the check box and re-login workspace

2. Creating Production Reporting Engine

•  Navigate to Navigate-->Administer-->Reporting and Analysis-->Production Reporting Engine
• Click on + symbol to create new Production Reporting Engine  .

Lets create a SQL Server Production Reporting Engine.

Select “MS SQL Server” as the Engine type and provide the sqr.exe location as Product Location

For example

C:\Oracle\Middleware\EPMSystem11R1\products\biplus\bin\SQR\Server\ODBC\bin

Note: for MS SQL Server there is no specific SQR server engine available in the installed server, It has to connect through ODBC. Hence ODBC path provided for this engine

 

 

3. Creating Production Reporting Database Server

• Navigate to Navigate-->Administer-->Reporting and Analysis-->Production Reporting Database Servers
• Click on + symbol to create new Production Reporting Database Server . 
• lets create a MS SQL Server database server
  Note: Before this , create a 32 bit ODBC DSN with DataDirect 7.0 SQL Server Wire Protocol driver in the Windows Server where SQR engine installed and configured.
  Use %WINDIR%\SysWOW64\odbcad32.exe to open  32 bit ODBC manager and Add new to create one DSN in System DSN tab
  Use the DSN name as sql server database name to avoid connectivity problems from the workspace. 

Now we should good to start Production Reporting jobs from workspace.