Cognos Planning

It is not an in-memory tool.

It has 3 components

o 1. Cognos Analyst

o 2.Cognos contributor administration console

o 3.Cognos contributor web application

it has 3 environments like cognos- PPE,PROD,DEV

There is a single library for all the environments.

1. Analyst-

In analyst ,modelers can build applications .

When modeler built/modify any application ,these changed files also updated in library.

These changes updated through Cognos contributor administration console in Cognos

contributor web application.

2. Cognos contributor administration console-

We can add user groups through this console.

3 types of access- 1) view: only read option , 2)submit: edit/modify option, 3) review/submit:
verify changes then can accept/reject changes , also can edit and read.

We can publish applications through this console.

We can take backup while exporting applications in this console.

Export/import is performed in this console..

3.Cognos contributor web application-

This console is for business users.

Users can enter data

Users can import data from various types of sources like excel , notepad files.

Planning is not integrated with BI ie if BI is down ,there is no effect on planning.

Solution owners can also do deployments and can add users.

 Deployment
Before doing any changes in analyst, we must first take a backup of respective library.

In a library , there are many subfolders also (eg. FY15,FY16 etc) , but we need to take backup of
whole library folder instead of its subfolders.

Logon to planning libraries \\itseelm-nt4422\ashare\Cognos Planning Solutions path

Then we will take a back up of respective library eg. Foldername_BKP

in that folder ,create subfolders and paste library file and rename with current date format.

Deployment backup- Logon to Contributor Administration Console. Go to Start Menu All

Programs IBM Cognos 10 Click on Contributor Administration Console

toolsdeploymentexport model and datanextselect application for which backup

requirednextfinish

naming convention is BIWEB_EXPORT_APPNAME_MODEL/MODEL&DATA_DATE

From monitoring console we can track whether export succeed or failed.

Deployment archive location: itseelm-nt3123.ikea.com/deployment$

In the archive find the exported file and verify whether there are folders named application,
security and library

toolsdeploymentimport select application from archivefinishuncheck libraryselect

appselect cognosgroup not knowntargetone to one map from cognos groups

CREATING NEW APPLICATION AND PUBLISHING

Start Menu All Programs IBM Cognos 10 Click on Contributor Administration Console

Applicationscreate new appapplication wizardselect any

librarynexte.listnextchoose cluster productionfinish

Then publish this package through Contributor Administration Console.

In e.list there is a list of user groups/roles. In e.list we can provide access

Click on e.list , 4 options import,export,insert,delete.

We can import securities from another applications.

In insert , select a usergroup and give rights(view/edit/submit) as required.

 Access Issues

Business users needs to be added in the Cognos_Planning_Contributor group.

Admin access group Cognos_Planning_Administrator

Modelers group Cognos_Planning_Modeler

Admin console access rights is for administrators ,business user can not access.

In access rights -> we can give access/restrict to specific application. There are 5 types of groups-
BN team, IKEA_planning_admin, IKEA_planning_modeler, ISAG, MTP admin, Plan and secure
capacity.

BN team have access to each and everything and they can perform any actions.

IKEA-planning_admin have all the admin rights.

IKEA_planning_modeler have access to all applications but limited access in each application.

Macros
We can schedule macros.

Check job management whether macros ran successfully or not.

If macros got failed , go to application maintenance -> application XML-> save XML to file in both
dev and prod.

After taking backup , select XML and reset deployment to production. It will go to previous stage
where macros ran successfully.

According to IBM policy , we keep record of 3 years only ,so user can lost some data by resetting
deployment ,then it needs to be updated manually.

For creating new macrosnew-> macro name->ok->wait for job-> select app-> validate->ok.

Admin links-> 2 options -> manage links and monitor links, used for synchronization.

In case service is down, we have to restart the service. From job cluster option will go to cluster
production, there will be 3 job servers- 4420, 4421, 4422. Delete the job cluster service. Now to
restart it again we will go to create cluster ->test->service start and verify.

If user is facing problem saving data ,needs to restart planning services, GWDC restarts the
planning services.