Hi,
Is there a way to trigger from outside of Cognos (command line/script/ect) an import job, that will import to Cognos reports from a specific deployment archive.
I know there is a way of using Cognos SDK for this, but I wanted to know if there are additional option of doing it..
You could always use a command line script to move the archive from one environment to the other and then have a scheduled maint. task from within cognos admin to import the task?
I don't want a schedule that will run in the background all the time... it is a one-time thing, that should happened once I place a specific zip in "Deployment" folder
In that case you can fire an event that houses a job off a trigger:
https://www-304.ibm.com/support/docview.wss?uid=swg21340069
Slightly off topic but I wonder if Cognos license terms are violated if I were to
- set up export-import from Dev to QA using
- export deployment started using trigger
- deployment archive copy
- import deployment started using trigger
- let regular developers (non admins) use above-mentioned export-import system to move stuff from Dev to QA without them having Cognos admin licenses?
It's a question for your Cognos rep. Depends what your licence agreement is.
Usually you get X number of Deverloper, X number of Admins and X Consumers.
My understanding is that you do need admin licenses. But check with your rep.
Quote from: prikala on 05 Nov 2015 02:09:21 AM
Slightly off topic but I wonder if Cognos license terms are violated if I were to
- set up export-import from Dev to QA using
- export deployment started using trigger
- deployment archive copy
- import deployment started using trigger
- let regular developers (non admins) use above-mentioned export-import system to move stuff from Dev to QA without them having Cognos admin licenses?
I think the answer would hinge on which user's credentials are being used by the export/import processes. If a legitimate Admin user creates these processes and the schedule, then anyone firing the trigger would not be logging in with Admin capabilities and would not have their ID running the processes. My feeling is that this would be fine - triggering a schedule from outside of Cognos is not a task only an Administrator can do - "normal" users can create and run schedules too.
As Northern_Monkey and bdbits suggest, the definitive answer will come from your IBM Account Manager, though - check with him/her first :)
MF.