Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 18 529618 - 001
Deploying Metadata
After compiling the metadata, you must deploy it to the NonStop server. Follow these
steps to ensure that the metadata will be available whenever RTID is started.
1. Use FTP to copy the class file in binary mode to the
/examples/rtsc/com/hp/rtsc/documents folder in your RTID OSS install directory
on the NonStop server.
2. If this is a new metadata definition, create an entry in the DOCCLASS table. The
RTID framework looks up this table and determines the class to load, in order to
process the given document. For example, to add Orders05 metadata, you would
use the following SQL command:
insert into =DOCCLASS values(“com.hp.rtsc.documents.Orders05”,
“Metadata for ORDERS05”, current)
3. Restart the RTID framework to pick up the updated metadata.
RTID test drivers use the DOCCLASS table to know what metadata classes to load.
If you do not want to deploy the metadata before testing it, you can load the new
metadata class by specifying the -c parameter to the test driver. All the test drivers
discussed in this manual handle the -c parameter as in the following example:
java Dispatch -c com.hp.rtsc.documents.NewOrders05 <other params>
You will see the following message displayed on the screen:
Loading variant/aliased document definition ORDERS05 from
com.hp.rtsc.documents.NewOrders05
Alternatively, you can deploy metadata dynamically, as described next.
Dynamically Deploy New or Updated Metadata
Once Director metadata has been deployed in a production system, it might not be
desirable to shut down and restart the Director server whenever you wish to deploy new
or updated metadata. In such cases, you can deploy metadata dynamically.
Adding a New Document Type
To add a new document definition (unrelated to any existing one), you create, compile,
and test the source file, as described in “Creating Native Document Metadata” or
“Creating IDoc Metadata.” Then you use the Director management interface to load the
metadata, as described in “Dynamically Deploying Metadata,” below.