Monday, 14 March 2016

Triggers

Not much documentation can be found about triggers. However we were able to successfully make it run on a Windows machine. We use this machine to create and publish Framework Manager models to our Cognos Server. Somehow Java is also included when FM was installed.
First thing we did is to copy these jar files to a folder in the Windows machine:
jarfiles
Let us call that folder c:\trigger\jar\lib
These jar files can be found in one of the the Cognos Server installation folders. In our case the exact folder is:
<Cognos installation folder>\webapps\p2pd\WEB-INF\lib
Next we copied these triggers files in another folder (let us call it c:\trigger\runtrigger)
triggerfiles
I would like to mention that I did not find these files in our current Cognos Server installation folder. I however looked in other installation folders in our production and development environment. Anyway these files can usually be found in
<Cognos installation folder>\webapps\utilities\trigger
 Now we need to know where is the Java folder in our Windows machine. I said earlier that Java is installed together with Framework Manager.  I found it in:
<Cognos installation folder>\bin\jre\6.0
If you don’t have Java in the machine you intend to use, you can install it manually. In any case you need to know which folder is your Java installed as you need to set the JAVA_HOME variable value to that folder.
So we edit the trigger.bat file mentioned above to look something like this:
triggerbat
To manually run trigger.bat, open the command prompt window, then navigate to the folder where it is located in the command prompt:
cd c:\trigger\runtrigger
This is how to run trigger.bat:
trigger “http://<server ip address>:9400/p2pd/servlet/dispatch” “<cognos admin login>” “<password>” “<LDAP name>” “<trigger name>”
where
<server ip address> is the ip address or url of your Cognos server (example: 10.20.30.123)
<cognos admin login> is the login id of Cognos Administrator (or any user with enough admin rights)
<password> the password of <cognos admin login>
<LDAP name> is the name of the Namespace ID which can be found in Cognos Configuration
ldap
and <trigger name> is the name you give to your trigger.


No comments:

Post a Comment