5.10 Understanding Grid ID Usage in the Audit Database

The Orchestration Grid ID is created using either the config or guiconfig configuration wizard operations or the zosadmin create -g command. The grid name you specify is displayed as the name for the container placed at the root of the tree in the Explorer panel of the Orchestration Console.The value for the Grid ID is saved in the /var/opt/novell/zenworks/zos/server/zos.conf file by the property system.property.com.novell.zos.server.gridId. Historical records of job instances (also known as “workflows”) run on the Orchestration grid are stored in the audit database (if included in the Orchestration Server installation) and are indexed by Grid ID. If you change the value of the Grid ID, the Orchestration Console loses access to these records.

For instance, testing has shown that if you choose to upgrade the Orchestration Server using the zosadmin create --upgrade -g option (that is selecting a Grid ID) instead of the config or guiconfig operations, it is possible that you might not use the existing Grid ID value or that you might neglect to use a value with the command. In this case, the default (the fully-qualified domain name of the current host) is used, which could differ from the original value for the Grid ID.

If this happens, any workflows recorded in the audit database prior to the upgrade are not displayed in the Orchestration Console, but they are still recorded in the gridid column of the workflows table in the database.

NOTE:You can use an SQL query if you want to retrieve the workflows. The first part of such a query might look like this:

SELECT * FROM workflow WHERE gridId = 'labzos.pso.lab.novell.com_Grid' AND ...

Keep in mind that the original Grid ID is not lost. If you want a report on that ID, you can use the zosadmin audit* commands with a -g option to yield a report showing the old Grid ID.

If you want to change the Grid ID, you have several options: