ActuateOverallPresentation Final

1
Experience
Value
>> Delivering Value
Navisys Report Generation Process
Using
Actuate

>> Delivering Value
>> Delivering Value
2
Insert Customer Logo
Agenda
Introduction To Reports
Importance Of Reports In An Organization
Reports In Navisys
Capability Of Actuate And Why Actuate In Navisys
Categorization Of Reports According To Navisys Standards
Approach Of Navisys In The Design Of Reports
Actuate Over All Architecture
Archival Retention Policy For QA3, Stage, Production
Files and Deployment, Naming Convention Of New Report
Database Names And Users
Servers

>> Delivering Value
3
Agenda (Contd)
Serena Tracker And Version Manager
Life Cycle Of An SCR [various documents to be maintained]
Production Support For Reports

>> Delivering Value
4
Introduction To Reports
A Simple Definition:
A Report provides
valuable,
accurate
and timely information
for many organizations like Educational
institutions, Financial institutions
including Insurance and Banking Sector,
Medical Centers and so on.,
>> Delivering Value
5
Importance Of Reports In an
Organization
A report provides Sensitive Information
That Helps
Top level Management in an organization
to be aware of what is happening in their
business
In timely and critical decision making
Reports provide records that are needed for
Auditing in an organization
>> Delivering Value
6
Reports In Navisys
In Navisys Reports are designed and developed
using Actuate E Reporting Designer Professional
Reports are circulated internally
Navisys uses reports for Auditing
Currently Navisys reports are being generated
for two companies
a)AIG SunAmerica Life Assurance Company
b)First SunAmerica Life Insurance Company

>> Delivering Value
7
Capabilities Of Actuate
Actuate is a powerful web report generation
tool that enables developers to design and
quickly develop tightly integrated, highly
flexible enterprise reports from data sources like
Oracle, Sybase, SAP, Progress SQL 92, XML,
Flat Files, ODBC,MS-SQL, DB2, General Open
Database Connection, Actuate Data Integration
Service Connection
Oracle And Flat Files are used as source of data
in Navisys
>> Delivering Value
8
Features And Benefits Of
Actuate
Fast, Complete report design development
Flexibility and power for precise control
Interactive, Personalized, actionable
reports
Component based Report Development
End User Training is not required
Provides Look and Feel Environment
Single Sign on
>> Delivering Value
9
Actuate In Navisys
Actuate is a web enabled designer tool that allows end
users to view the reports from web.
Actuate supports Report Bursting technique which
helps to develop a single report object Executable (rox)
that generates multiple report object instances (rois). In
Navisys this technique is used to generate report
outputs for various different companies available in
T_LINC_NAME_COMPANY table using only a single
design file.
we can have different security permissions for each user
to view the reports.
>> Delivering Value
10
Categorization Of Navisys
Reports
Reports in Navisys are separated into various categories so that it becomes easy for
identification, addition of new reports and deletion of an existing report.
Reports in Navisys are classified based on Purpose of The Report into the following
categories:

Categories Of
Navisys Reports
Accounting
Actuarial
Appless
List Bill and
Market Timer
New Business
Policy Ownership
Service
Production
Payout
>> Delivering Value
11
Categorization Of Navisys Reports
(Contd)
1)Accounting:
Reports under this category deals with variable investment
option balancing report, Accounting entry reports and the reports
for the SAP subsystem.
2)Actuarial:
Actuarial reports provide various breakdown details of all
account balances for the entire account base at the end of each month.
This is used to make sure that the company has sufficient reserves to
meet NAIC (National Association of Insurance commissionaires)
and federal guidelines.
3)Appless :
The reports produced in this subsystem include detail and
summary Information for the activity in the previous days night cycle.
The information is sent to Sun America via an interface on a daily basis.
These reports are generated based on the information from Interfaces.

>> Delivering Value
12
Categorization Of reports(Contd)

4) List Bill and Market Timer :
This system summarizes the reformatted and resorted data from List bill system.
This system shows premium by group within the operating companies.
5) New Business :
New application for accounts is processed through this system. These Applications
come to Sun America either in application format or apples format. Both these
Formats are taken by this system and reports are generated to monitor the processing
of this system.
6) Policy Ownership Service :
Policy Ownership Services reports are used to capture the processing data
associated with the Account Administration system. These reports include any data
pertaining to transactions processed and rejected. The data is broken down by
transaction type as well as processor id

>> Delivering Value
13
Categorization Of Navisys Reports
(Contd)
7) Production :
Production reports are basically used to track the
transactions, both Financial and non-financial that have
happened on a given day. This includes both POS and
New Business transactions. These reports are used to
track the no. of transactions, type of transactions, Users
who processed the transactions, no. of transactions
processed by each user.
8) Payout :
These reports are designed and developed to capture the
activities happening in the payout phase. This is under
construction.
>> Delivering Value
14
Approach of Navisys in the design of
reports
Reports Are
Broadly classified into
Two types Based On
the Location Of the query

Non-Optimized
Reports
Optimized
Reports
>> Delivering Value
15
Non Optimized Reports:
Here queries are written inside the report design itself to
retrieve data directly from tables.
These reports are placed in the Reports folder of Opalis.
Optimized Reports:
Here Oracle Procedures are used to retrieve and insert data
into temporary tables.
These reports are placed in the Reports New folder of
Opalis.
Further
Some Navisys reports use text files as the source of data.
These reports falls under the Appless Category.
These reports are generated after the completion of Interface
Jobs.

Approach of Navisys in the design of reports
(Contd)
>> Delivering Value
16
Actuate Overall
Architecture
Over all Architecture of actuate can be Explained by
splitting it into
Client Side Component
Server Side Component
Client Side Component:
Contains a normal Browser where we type the URL
(Uniform Resource Locator) to view the report
Example:url for accessing the QA reports is
http://qarpts.sunamerica.com/acweb/

IIS Web Server keyword indicates that
you want to access the
Report Encyclopedia
Protocol

>> Delivering Value
17
Server side Components:
5 Components:
Web Server
Report Cast Agent
Actuate Report Server
Actuate Encyclopedia
Report Cast
Actuate Overall Architecture (Contd)
>> Delivering Value
18
Client Side
Browser
request
Web Server
Client Side
Report Cast Agent
Actuate Report Server

Oracle
Database
View Process
Actuate Administrator Server
Factory Process Persistent Object
Actuate Encyclopedia
Server Side
response
web server extension that enables users to locate and
access the reports in a Report Encyclopedia on an
Actuate Report Server. Report Cast generates HTML and
DHTML pages based on templates.
Transfers The Request To The server
Contains collection of folders *) the rox files (present in Sources Folder) and roi files
(present in Report Outputs Folder) *) the users who can access the roi files
*) the roles and the privileges
*) active folder, completed folder, Scheduled request folder
Actuate Architecture Diagrammatic Representation
Report Cast
(IIS-Internet Information Server)
Hosts all the scripts, programs
And serves the request using HTTP
(Hyper Text Transfer Protocol)
Flat
Files
>> Delivering Value
19
Actuate Overall Architecture(Contd)
Actuate Administrator sever :validates users and user requests.

View Process: used to view the report roi in DHTML or PDF
format. There is a single view process per report server.

Factory Process: executes the report object executable (rox) and
generates the Report object instance (rois).There are multiple
Factory process per server.

Actuate Persistent Object: This server process manages an object
that exists until the report file is deleted

Actuate server can execute 5-7 reports at a time.

Actuate Report Server Components
>> Delivering Value
20

Archival Retention Policy for QA3, Stage and
Production:
Reports are of prime importance as they are required for
Auditing
So Sun America has the Practice of archiving the
reports
Archival period varies depending on the environment
After the elapsed period, the reports are archived to
TAPE DRIVES so that they can be used in future.
Environment Retention Policy
QA3 3 Months
STAGE 3 Months
PRODUCTION 6 Months
>> Delivering Value
21
Files and Deployment, Naming
Conventions for a new report:
Files:

New Design
Save
DesignName.rod
(Report Object Design)
Compile (Build and Run)
3 Files Are Generated
DesignName.rox
(Report Object Executable)
DesignName.bas
(Basic Source file)
DesignName.roi
(Report Object Instance)
>> Delivering Value
22
Files (Cont)
Apart From these Files there are,
a) .ROL (Report Object Library) File
A library File is one that contains all commonly used templates,controls
like logos, textbox, labels, frames
b) Help File
This File contains the help information for particular report in the form
of HTML page
To view the help information click on the HTML link available on
the report output
Note:
*) If there is no data to be displayed in a report for a particular cycle date, then
report has to display No Activity Run For This Report in the content frame
of the report
*) TOC (Table of Contents)
It is a link that is available on the report output via web, on clicking this link
we will get the set of sub companies that are available under that company.so
we can easily navigate through the reports data particular to a sub company
>> Delivering Value
23
Files (Contd)
ReportObject
Design
(.rod)
SAGlobalLib.rol

Standard Headers/Detail frame

Standard Controls

Database Connection Objects

Text/Label/Line Controls

Report Object/Sequential
Section/Group Section

SAParamFetch.bas
Contains Functions To
Fetch The Cycle Date
From Param Files For The
Report

SAGlobalVars.bas
Declaration and Definition
Of Global Constants
For Reports

SALogoFetch.bas
Contains Functions For
Fetching The Company
Logo Based On The
Internal Company Code
SAErrorHandler.bas
Contains Functions For Logging The
Errors Into SAReportErrorLog.txt

A Detailed Sketch Of The Files:
>> Delivering Value
24
The .rod files of the report design will be checked in the
version manager. They will not be available in any of the
actuate servers.
In QA 3,Stage,and Production
The compiled .rox files are deployed in the actuate server
using using the following location:

The generated outputs(.roi files) will be placed in the
following location

SunAmerica Enterprise Reports Policy Administration System Sources
SunAmerica Enterprise Reports Policy Administration System Outputs
Deployment Of These Files
Navisys is using Perl Scripting to achieve this
>> Delivering Value
25
Naming Conventions Of A New
Report
Standard naming convention allows us to identify a
report easily.
Naming convention used in Navisys not only provides a
standard convention but also provides an overall
functionality of the report.
Example:ACCM1D001- be the report ID

the first three characters signify the
Category of the report
Here ACC-Accounting
signifies whether the
report is generated
for a
single(S)company
Or For
multiple
(M)companies
signifies the version
of the corresponding
report.
signifies the frequency at which the report
is generated In Navisys
Reports are generated on the following
basis namely:
D-Daily
W-weekly,M-Monthly
Q-Quarterly,Y-Yearly
last three characters signify the
SERIAL number of the report
Under that category
>> Delivering Value
26
Naming Convention For DBCR (Database
Change Request)
Temporary tables and packages are deployed into
the respective database using SUNDB schema
Necessary grant scripts are provided for various
users to run the reports in respective environment
Naming Convention For Tables:
Signifies that table
is in Sun Database
Schema
Signifies that it is a
table
Actuate Table
Management
Temporary
Name Of The Table
SUN_T_ATTM_TEMP_tablename
>> Delivering Value
27
Naming Convention For DBCR (Contd)
Naming Convention for Packages and Procedures
Mainly packages and procedures are used for retrival and
insertion of data into temporary tables.
Naming Convention For Package File Name Before
Checking into VM:
Example:DBCR_SUNDB_ACC.sql

Signifies that
Sun Database
Schema is used for
Deploying the SQL script
Signifies that it is a
Database Change Request
Specifies under which
category this script
belongs to. Here it is
Accounting
>> Delivering Value
28
Naming Convention For DBCR
(Contd)
Naming Convention For A Package:
Example: PAR_REPORTS_ACC
Signifies that this is a
Package
Signifies that this package
is for reports
Signifies the Category of
report for which this
package was developed.
Here it is Accounting
>> Delivering Value
29
Naming Convention for Packages
and Procedures (Contd)
Naming convention For Procedures:

Example: SUN_PRC_AT_I_PROCNAME
Signifies that SUNDB
schema is used for
deploying the SQL
scripts
PRC signifies that
it is a procedure
Signifies that this
procedure is for
Actuate
This Signifies that this procedure is
used for INSERTING' records into
the temporary tables.This
Character indicates the Data
Manipulation Language the proc
will do.
Similarly, S- selecting,U-Updating
This Signifies
the name of the
procedure
>> Delivering Value
30
Database Tables Frequently Used For Reports

Table Name
T_LINC_NAME_COMPANY
T_LIPR_POLICY_ROLE
T_LITC_TRANSACTION_COMMON
T_LIPC_POLICY_COMMON
T_LITT_TRANSACTION_TYPE_CODE
T_LINM_NAME_MASTER
T_LINC_NAME_COMPANY
T_LIPL_PLAN
T_LIPY_PLAN_TRAN_TYPE
T_LFUN_USER_SECURITY_NAME
T_LICO_CONFIRM_LOG
T_LICD_CONFIRM_DETAIL
>> Delivering Value
31
Database Names And Users
In Sun America, there are three different environments
namely QA, Stage, Production
Each environment has got its own Database and Access
Rights are provided to Users to access these Databases
Environmen Database User Name under the
which the reports
QA HOQA3 NV04_QA_ATU_REPORTS
STAGE (2 DBs) HOS1,HOS1B NV04_STG_ATU_REPORTS
PRODUCTION
(2 DBs)
HOP1,HOP1B NV04_PROD_ATU_REPORTS
>> Delivering Value
32
SERVERS:
Sun America has provided three different Servers for
maintaining reports
Environment Server Name
IP Address Opalis
Service
Name
Actuate Management
Consoles(Actuate
Encyclopedia)User
Name
QA WH-DWENTRPT1 165.30.130.226 whqwndoc1 runreporthigh
Stage
WH-QWENTRPT1
165.30.130.229 STGOPALIS1 runreport
Production SAIPWRPT1 165.30.130.228 PRDOPALIS1 runreport
>> Delivering Value
33
Serena Tracker and
VersionManager
Serena Tracker:
Serena tracker provides details of an SCR
It keeps track of the Status of the SCR
URL for Accessing the Serena Tracker is:
http://whpwnpvcs1.sunamerica.com/tmtrack/tmtrack.dll?LoginPage&Template=logi
nform&Message=
various fields inside the tracker are

Field Name Description
State Change History Field Shows Status in a Flow Chart Format
Standard Fields Shows details of SCR like description,
release number,environment,severity
User Fields Shows names of the Project members involved
Approval Fields Shows approved release date
Manager Fields Shows Executive summary, Business priority
request,BRD due date etc
System Fields Shows SCR Owner, Last Modifier name,last
State change,current status like programming,testing
Change History Shows history of changes the SCR has undergone
>> Delivering Value
34
Serena Tracker and Version
Manager(Contd)
Version Manager:
Version Manager keeps track of various
versions of source code (.rods, DBCRs,
scripting files, .html)
It maintains the source code from the first
version to the latest version
URL for Accessing the Version manager is:
http://whpwnpvcs1.sarm.aigrs.net/Intel-
Architechture
>> Delivering Value
35
Life Cycle Of An SCR
Navisys follows a systematic approach to deal with the issues that arises in the
system
Problem Arises-An SCR (System Change Request) will be raised
SCR Identified by a unique number
Serena Tracker-Keeps track of the Status Of The SCR
The following Approach is employed by Navisys to improve the software
Engineering process.
a) Analysis Phase
b) Design/Programming/Development and unit testing Phase
c) QA testing Phase
d) Stage testing Phase
e) Final Delivery (Production)
>> Delivering Value
36
Flow Chart Of SCRs Life Cycle
Analysis Phase
Design/Development/Programming And Unit
Testing Phase
QA Testing Phase
Succeeds
Fails
Stage Testing Phase
Final Delivery(Production)
Succeeds
Fails
>> Delivering Value
37
(Contd)
Phase 1:Analysis
Preliminary Analysis Of the SCR
Three Documents are to Prepared are shown below and they have to be sent to the
Reviewer
In case of SR, we should prepare SDS [Software Design Specification] from the BRD and
should be sent for review.
We should get the reviewer comments to proceed further.

Name Of The Document Purpose Of The Document
Analysis Template Provides an overall analysis Of SCR like Size of the
SCR,Kind Of fix (Data/Code) required. If necessary screen
shots of the problem is attached
Impact Analysis Provides a detailed analysis of the SCR based on Functional
and Technical aspect.It also specifies the
Module affected, Programmer assigned, estimated man hours
Navisys Testing Assignment contains the steps of how to test the SCR fix
>> Delivering Value
38
(Contd)
Phase 2:Design/Programming/Development and unit testing
changes that are to be made in the design/code are carried out
if unit testing is needed, unit test cases are prepared and carried out
We should be receiving code review and unit test review documents from the reviewer
After getting reviewers feedback, we have to check in the code in the version
managerand provide an appropriate label (this should follow the naming convention
Appended with the environment the code will be moving for e.g. SCRnumber_QA
indicates that this SCR is moving to QA)
The following documents are to be sent to the On-Site Coordinator

Name Of The Document Purpose Of the Document
Code Move Request Tells to which environment the code is
moving
Release Notes Tells the location of the code and its version
in version manager
>> Delivering Value
39
(Contd)
Two mails are to be sent at this stage
Office Model Approval Mail:
This mail should be sent to office model group requesting approval for
the SCR to move to QA
Navisys Testing Assignment should also be attached with mail
SWAT approval mail:
If changes are made in Database then SWAT approval mail should be
sent to the ON-SITE DBA along with the execution plan
Swat approval field in Tracker should be changed to IN REVIEW
which the DBA will change to APPROVEDif the execution plan looks
good
SWAT APPROVAL is required when the SCR is moving to QA or
Production
Note:
Reports dont have DEV environment, So we need to generate DEV results
by pointing to DEV DB from the local Desktop

>> Delivering Value
40
(Contd)
Phase 3:QA Testing
The configuration management deploys the code in QA and QA
testing will be done by the QA team
If they are Ok with it, they will change the SCR Status to
AWAIT STAGE MOVE
Prepare Release notes, code move request and send it again to On
Site Co-coordinator
Send Office Model Approval Mail To Office Model group
requesting to move SCR from QA to Stage
When the SCR is moving to STAGE, we need to raise
PCM (Production Code Move) using Peregrine Service Center

>> Delivering Value
41
(Contd)
Phase 4:Stage Testing
QA or UAT or BSST team perform User Acceptance Testing in
Stage
If the SCR completes the UAT requirements successfully,BSST
sign off notes will be attached in the tracker
The status of the SCR will be now changed to AWAIT PROD
MOVE
Phase 5:Final Delivery
BSST notes are attached to peregrine ticket for that corresponding
SCR
Release notes should be sent to the on-site coordinator
Finally, the configuration management team deploys that in
production

>> Delivering Value
42
(Contd)
These following are the list of Documents that are
to maintained during the life cycle of an SCR
Analysis Template
Impact Analysis
Navisys Testing Assignment
Release Notes
Code Move Request
Code Review
Unit Test Review

>> Delivering Value
43
Detailed Sketch Of SCRs Life
Cycle
Phase Documents/Mails/Activities Sent Tracker Status
From To

Analysis Template Document Programmer Reviewer SCR Status
Impact Analysis Document Analysis
Navisys Testing Assignment Document
Review Documents Reviewer Programmer

Necessary Design/coding SCR Status
Unit Testing (if required) Programming
Code Review Documents Reviewer Programmer
Unit Test Review Documents
Check In The Code In Version Manager
Release Notes,Code Move Request Programmer On-Site Coordinator

Office Model Approval Mail(Request Programmer Office Model Group SCR Status
to move SCR to QA) based on Dev results
Attach Navisys Testing Assignment to
this mail

SWAT Approval Mail along with Execution Programmer On-Site DBA SWAT Approval Field
plan (SWAT Approval mail is required if In Review
Changes are made to DB)

Approved
Analysis
Development
Await QA
Move
Dev Test
Failed
OK Not OK
If Execution
Plan is Good
>> Delivering Value
44
Detailed Sketch Of SCRs Life Cycle
(Contd)
Phase Documents/Mails/Activities Sent Tracker Status
From To
QA Team Performs Required Testing SCR Status
Using The Attached Navisys Testing
Assignment Document
Release Notes,Code Move Request Programmer Onsite Coordinator
Office Model Approval Mail Programmer Office Model Group
(Request to Move SCR From QA To Stage)
Raise A Production Code Mode (PCM)
Ticket Using Perigrine Service Center

QA/BSST/UAT team performs Stage
Testing SCR Status

QA/BSST/UAT Team attaches the BSST/QA/UAT Tracker
BSST Sign Off Notes to Tracker if it Team
succeeds the Stage Testing

Release Notes Programmer On-Site Coordinator
BSST Sign Off Notes
attached to PCM

Configuration Management Team Deploys
the code in Production
QA Testing
Stage Testing
Final
Delivery
Await
Stage
Move
Succeeds Fails
QA Test
Failed
Succeeds Fails
Await
Prod
Move
UAT Test
Failed
>> Delivering Value
45
Production Support For
Reports
Reports will be running in all the three environments
in Sun America
We need to provide level 1 support to ensure their
smooth run
Service Level Agreement:
An agreement between Sun America and External
Entities Stating that Sun America will provide services
to those External Entities without any interruption
To meet the SLA, Sun America, AIGSS and HCL
Operations Noida coordinate each other
>> Delivering Value
46
Production Support For
Reports(Contd)
Types Of Support:

Level 0 Support
Level 1 Support
Level 2 Support
Provided by HCL Operations Noida.They Trigger and
Monitor Reports in Each Environment. If they find a
Problem they will escalate it to Level 1 Support
Provided by AIGSS. Provides solutions to
problem faced by HCL.If they are unable to
solve the problem they will escalate the
problem to Level 2 support
Provided by Sun America. Provides solutions in
case level 1 support is unable to do it
HCL will be raising Peregrine Tickets to keep track of the escalations.
These three support groups ensures that SLA is met 100%.
>> Delivering Value
47
BCV2 SPLIT
Previously all the cycles(Pre Batch,Multicylce,Interfaces,
Reports,Docucorp) hit the HOS1 and HOP1 databases. Due
to this the performance was reduced drastically
Then, Sun America came up with a solution called
BCV2 (Business Continuance Volume)
In BCV2 an image copy of HOS1 to HOS1B and HOP1 to
HOP1B are taken
There after the cycles (Pre-Batch, Multi Cycle and
Interfaces) hit the HOS1, HOP1 databases and Reports,
Docucorp cycles hit the HOS1B, HOP1B databases
>> Delivering Value
48
Opalis Intergration Server
(OIS)
Opalis Robot is an IT process automation software that
increases the productivity and efficiency of performing
certain repeated tasks
It coordinates IT processes through the use of
workflow, conditional logic, event based scheduling,
and other features such as integration between popular
system management
>> Delivering Value
49
Opalis Robot( Contd)
Benefits Of Opalis Robot:
Achieve Process Control
Reduce Operating Costs
Improve Return on Existing Technology Investments (ROI)
Increase Productivity
- Automate Repetitious Tasks
- Allow Humans to Deal with Exceptions
Checklists:
Actually we in Navisys, Design and Develop new reports, automate their
execution using Opalis robot. Then HCL Operations Noida takes care of
triggering these reports
We prepare and give a checklist to HCL operations, so that they can logon
to OpalisRobot and trigger the reports as specified in the check list
>> Delivering Value
50
Opalis Folder Structure:
In QA3 and Production, the Following Folder Structure is Used

OpalisRobot
This Folder Contains Opalis Jobs For
all Non-Optimized Report Category

This Folder Contains Opalis Jobs For
all Optimized Report Category

Note:
In Stage,we dont have the Reports Folder
Opalis Jobs For Both Optimized and Non-Optimized Reports Category are
Placed in the Reports New Folder
Reports
Reports New
>> Delivering Value
51
Actuate Files Needed For Automation Of Report
Generation (a.Configuration Files)
There are two XML files used for actuate.They are in Location
D:\Enterprise Reports\Batch\config
ReportRunPrarams.xml
This xml maintains a mapping of all report names and the associated actuate
programs and parameters.
This xml file contains the following objects for each report
1) report-name-specifies the report name
2) rox-name-specifies the .rox (report object executable) name
3) 4 parameters that specifies the path in actuate server
a) Folder in server where the corresponding .rox is present
b) Path in server where common .rov (report object value) is present
c) Folder in server where the corresponding .roi is present
d) Constants for setting the max version of reports for each group
(Not used now)

>> Delivering Value
52
XML Schema for ReportsRunParams.xml
<report>
<report-name> </report-name>--------Specifies the reports name
<rox-name> </rox-name> -----------Specifies the .rox name
<pram id=1>
<name>-1</name>
<value> </value>--------------Folder in server where the corresponding .rox is present

</param>
<pram id=1>
<name>-2</name>
<value> </value>---------------Path in server where common .rov is present
</param>
<pram id=1>
<name>-3</name>
<value> </value>---------------Folder in server where the corresponding .roi is present
</param>
<pram id=1>
<name>-4</name>
<value> </value>----constants for setting the max version of reports for each group-Not used now
</param>
</report>

>> Delivering Value
53
FeedfilesMapping.xml

This xml file maintains the report name, the source and destination location of files
that provides data for reports that uses flat files.

This xml file contains the following objects for each report
1) report name - specifies the name of the report
2) source-file - specifies the Source files location
3) destination-file- specifies the destination location to copy the source file

XML Schema for FeedFilesMappingxml

<report>
<report-name> </report-name>-------- specifies the reports name
<source-file> </source-file>----------- specifies the Source files location
<destination-file> </destination-file>----- specifies the destination location to copy the source
file
</report>

>> Delivering Value
54
Actuate Needed For Automation Of Report Generation
(b.Batch Files)
The following Batch files are required to execute various scripts for report generation
All these files are in location D:\Enterprise Reports\Batch\jobs

Batch File Name Executes Purpose
ParamUpdate.bat Perl ParamUpdation.pl DAILY
(or)
cscript ParameterUpdation.wsf
/Cycle:DAILY
Updates all the param files with current cycle date
Whose report type is DAILY
Updates all the param files with current cycle date
Whose report type is DAILY
RunReportID.bat Perl ReportBatch.pl RUN Report ID
(or)
cd E:\Enterprise Reports\Batch\jobs
cscript ReportBatch.wsf /Process
:RUN/
ReportName:ReportID
Runs a report by taking the Report ID as argument.

Changes to the Specified Directory
Runs the report by taking RERPORT ID and RUN as
arguments.
CopyReportID.bat cd E:\Enterprise Reports\Batch\Jobs
cscript ReportBatch.wsf /Process
:COPYFEEDS/ReportName:ReportID
Changes to the specified directory
Copies files from Source location to Destination Location by
taking COPYFEEDS and REPORTID as arguments
CleanUp.bat cscript CleanUp.wsf Takes the current logs of Param Jobs, Copy Jobs, Run Jobs
and append those log files name with the previous days cycle
date.
These log files are in folder
D:\Enterprise Reports\Batch\Log
>> Delivering Value
55
Generation (c. Perl/VB/Windows Script Files)
The following perl/VB/Windows script files are used for Report generation

Perl/VB/Windows Script
File Name
Location Purpose
BatchEnv.pl
BatchEnv.vbs
D:\EnterpriseReports\Batch\common Contains all Environmental Settings.This perl file is
included at the start of each job
DBUtil.pl
DBUtil.vbs
D:\EnterpriseReports\Batch\common This file returns Connection String if the DB
Connection is established successfully
ProcessReport.pl
ProcessReport.vbs

D:\EnterpriseReports\Batch\common This file gets the PROCESS TYPE and REPORT ID
as arguments from ReportBatch.pl/ReportBatch.vbs ,
parses the ReportRunPrarams.xml and executes the
report
ParameterUpdation.pl
ParameterUpdation.wsf
D:\Enterprise Reports\Batch\jobs

Updates all the param files with current
cycle date
ExecuteProc.pl
ExecuteProc.wsf
D:\Enterprise Reports\Batch\jobs This executes the procs by getting
packagename.procname as arguments.It uses
DBUtil.pl to get the Connection String
CleanUp.wsf D:\Enterprise Reports\Batch\jobs Takes logs of Param jobs,Copy jobs and Run jobs
ReportBatch.pl
ReportBatch.wsf
D:\Enterprise Reports\Batch\jobs

This file gets the PROCESS TYPE and REPORT ID
as arguments and pasess
PROCESS TYPE and REPORT ID as
Arguments to ProcessReport.pl/ProcessReport.vbs

>> Delivering Value
56
Opalis Jobs
For Generating Reports Using Opalis the Following Jobs are required.
Note: In QA3,Stage all Actuate Files are in D Drive
Whereas, in Production all Actuate Files are in L Drive
CleanUp Job
This job takes current logs of Param Jobs, Run Jobs (Report), Copy Jobs and saves these
log files by appending the file name with previous days cycle date
This Job will be Triggered First,before triggering any other jobs.

Clean Up
Job
On Triggering
invokes
CleanUp.bat
(D:\Enterprise Reports\
Batch\jobs)
Executes

cscript CleanUp.wsf
(D:\Enterprise Reports\Batch\jobs)

Log files are saved in the location
(D:\Enterprise Reports\Batch\logs)
Fails
Succeeds
Opalis Logs
>> Delivering Value
57
Opalis Jobs (Contd)
Parameter Update Job:
This job Updates all the parameter files present in
D:\Enterprise Reports\ParamFiles
With the latest cycle date present in T_LIBA_BATCH_PARMtable.

Figure Shows The Steps Involved In Updating Param Files:

Parameter
Updation
Job
ParamUPDATE.bat
(This Batch File is present in
D:\Enterprise Reports\
Batch\jobs)
Perl ParameterUpdation.pl DAILY
(or)
csript ParameterUpdation.wsf/Cycle:DAILY
(D:Enterprise Reports\Batch\jobs)
Updates all the ParamReportID.txt
(D:\Enterprise Reports\Param Files)
Opalis Logs
On Triggering
Invokes
Executes
Succeeds
Fails
>> Delivering Value
58
Opalis Jobs(Contd)
Proc Job:
This Job executes the Procedures for the corresponding cycle date and inserts records into the
temporary tables.
Figure Shows The Steps Involved In Updating Param Files:

Proc
Job
Perl ExecuteProc.pl /ProcName:
packagename.procname (Or)
cscript ExecuteProc.wsf /ProcName:
Packagename.procname
(D:\Enterprise Reports\Batch\iobs)
Opalis Logs
Executes
Takes
PackageName.
ProcName As
a Parameter To
Execute
Fails
Corresponding Proc
Gets Executed and
Temp Tables Are Inserted
With Records
DBUtil.pl (or) DBUtil.vbs
Batch\Common)
Fails
On Triggering
CALLS
Succeeds
ParamFiles
Cycle Date
Succeeds And
Returns
Connection
String
>> Delivering Value
59
Opalis Jobs(Contd)
Report Job
This job runs a report as shown in the figure

Report Job
On triggering
invokes
RunReportID.bat
Batch\jobs)
Executes

perl ReportBatch.pl RUN ReportID
(Or)
cscript ReportBatch.wsf /Process:Run
/ReportName:ReportID
Batch\jobs)

ProcessReport.pl
(or)
ProcessReport.vbs
(D:\EnterpriseReports
Batch\Common)
Parses

ReportRunParams.xml
(D:\EntrpriseReports
Batch\Config)

acshell.exe
(D:\EnterpriseReports\Batch\Bin)
Runs The Corresponding .rox
In Actuate Server
.roi generated in the correponding
FolderIn Actuate Server
Calls

Errors Logged into
SAReportsErrorLog.txt
ErrorLogs)

Fails
Succeeds And Invokes
Succeeds
Succeeds
Fails
Fails
Fails
Opalis Logs
>> Delivering Value
60
Opalis Jobs(Contd)
Copy Job
This job Copies the file from source location to destination location as shown in
the following figure

Copy Job
On triggering
invokes
CopyReportID.bat
Batch\jobs)
Executes

cscript ReportBatch.wsf
/Process:COPYFEEDS
/ReportName:ReportID
Batch\jobs)

ProcessReport.vbs
(D:\EnterpriseReports
Batch\Common)
Parses

FeedFilesMapping.xml
(D:\EntrpriseReports
Batch\Common)

Calls

Opalis Logs

Fails
Copies The File From Source Location To
Destination Location
Succeeds
>> Delivering Value
61
Problems Faced By Level 1Reports Production Support
Team
Common Problems Faced By Reports Level 1 support Team in AIGSS and Their Solutions
Problem Description Impact Solution
Disk Space Space is Enterprise Reports'
drive is less
Actuate services, Opalis
services may go down.
Request HCL to escalate it to Environmental
Support
Patch/OS
Upgradation
Sun America might upgrade
their OS or they might
implement patches in
QA/STAGE/Production
HCL might be unable to
bring up the Actuate
and Opalis services
Look for a mail that contains information
regarding patch or OS upgradation.If so, request
HCL to escalate it to Environmental Support

Param
Update
Monthly Job
Failure
Param Update Job fails
And Cycle Date will not be
updated properly in monthly
param Files for monthly
reports
.roi may not be
generated
Manually update the cycle date in the
corresponding file param file
Deployment New version of .rox might be
deployed
Actuate server might
not be able to read the
corresponding .rox file
while running the report
Go to actuate management console
->Sources, check for the date when the
Corresponding .rox was deployed.
If it was the latest deployed one then
tell HCL that it is an deployment issue,
else
Request them to retrigger that report
when the respective DB has less load
>> Delivering Value
62
Problems Faced By Level 1Reports Production Support
Team(Contd)
Problem

Description Impact

Solution

Opalis Hung Up

Opalis may hung up
during the execution of
The Report or Proc job
Proc might not have run

Report might not have
generated

Request HCL DBA to look for the
execution of the proc in the DB.
If the proc is not running in the
DB, check the corresponding
temp table whether it has got
data.
If it has got data then request
HCL to stop the task in Opalis
Else
ask them to re-run the proc job

Check in Encyclopedia for the
report output, if it is not available
then request HCL to retrigger the
report job
Else
request HCL to stop the
respective task in Opalis as
already roi has been generated

>> Delivering Value
63

ActuateOverallPresentation Final

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ActuateOverallPresentation Final

Uploaded by

Copyright:

Available Formats

1

You might also like