20.07.2014 Views

COGNOS Business Intelligence Series 7

pes.pdf

pes.pdf

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix B: Batch Administration<br />

KILL<br />

Stops the process for the object. The following example, stops the current processes for the Great<br />

Outdoors cube:<br />

KILL "Great Outdoors"<br />

LIST<br />

Lists all the objects in the specified folder. The following example lists all objects in the folder<br />

"/docs/recent reports":<br />

LIST "/docs/recent reports"<br />

If no folder is specified, all the objects in the current folder are listed.<br />

MOVE<br />

Moves an object and its associated overridden properties to a new object, while leaving behind a<br />

shortcut to the new object to prevent broken links. The following example creates a new object<br />

"bls" in the "/new/" folder. It also replaces the original object "gnt" with a shortcut of the same<br />

name, linked to "bls":<br />

MOVE gnt "/new/bls"<br />

NOTIFY<br />

Invokes a cube update notification process. This process includes<br />

• updating the Modified date and time for all the related cube and Report NewsItems in<br />

Upfront to the date and time when you run the NOTIFY command<br />

• changing the status of these NewsItems to Unread to reflect the fact that the cube data has<br />

changed<br />

• running the related PowerPlay Agents that had been scheduled to run on cube refresh<br />

Before running the NOTIFY command, you must ensure that the refreshed cube has been copied<br />

successfully to the location as defined in PowerPlay Enterprise - Server Administration. You must<br />

also ensure that the user has specified the connection to the PowerPlay Enterprise Server<br />

containing the refreshed cube.<br />

The NOTIFY command uses the following syntax:<br />

NOTIFY {(CUBE_OBJECT objectname | CUBE_FILE filename)} EVENT = UPDATE [ON_ERROR<br />

IGNORE | FAIL]<br />

• CUBE_OBJECT objectname<br />

Use this option if you know the name that you have assigned to the cube.<br />

The following example invokes a cube update notification process on the refreshed cube<br />

Great Outdoors.mdc, specifying the object name "Great Outdoors":<br />

NOTIFY CUBE_OBJECT "Great Outdoors" EVENT=UPDATE<br />

• CUBE_FILE filename<br />

Use this option when you want to reference the cube filename.<br />

The following example invokes a cube update notification process on the refreshed cube<br />

Great Outdoors.mdc, specifying the file path:<br />

NOTIFY CUBE_FILE "C:\Program Files\Cognos\cer4\ppserver\great_outdoors.mdc"<br />

EVENT=UPDATE<br />

• ON_ERROR<br />

The optional parameter ONERROR specifies the result of the command if the update<br />

notification failed for one of the listed objects.<br />

IGNORE - the command is considered successful if update notification is successful for at<br />

least one object.<br />

FAIL - the command is considered a failure if update notification failed for one of the listed<br />

objects.<br />

PUBLISH<br />

Publishes an object to the portal (Upfront or Cognos Connection). The following example adds<br />

the object "Marketing" as an Upfront NewsItem:<br />

Enterprise Server Guide 105

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!