Package Resources

This section contains a list of the resources a package can contain. For a list of the available resource types and their descriptions, see Resource Types.

• acl. The definition of a role such as Administrator or Guest. For details, see "Roles Manager" in the Administer section of the UCMDB Help.

• adapter. Contains a description and the capabilities of the deployed federated adapter.

• adapterCode. Contains compiled classes (normally a jar), based-on *.jar files, and configuration files needed for federated adapters. Place these files in the adapterCode\<adapter ID> folder in the zip package. For details, see "Add an Adapter for a New External Data Source" in the Developer Reference section of the UCMDB Help.

• calculatedlinks. Contains the calculated super class for each of the calculated links defined.

• calculatedlinkstriplets. Contains the calculated relationships and their triplets as defined in the CI Type Manager.

• categories. Contains the State definitions used by Impact Analysis. For details on States, see "State Manager" in the Administer section of the UCMDB Help For details on Impact Analysis, see "Impact Analysis Manager" in the Modeling section of the UCMDB Help.

• class. CI type descriptions, such as host, file, switch, and so on. For details, see "CI Type Manager" in the Modeling section of the UCMDB Help.

• cmdbview. Contains the hierarchy rules defined for the base TQL query of each view. For details, see "Modeling Studio" in the Modeling section of the UCMDB Help.

• correlation. Impact rule definitions. For details, see "Impact Analysis Manager" in the Modeling section of the UCMDB Help.

• datamodel. Used to import CI instances into the system. If the CI does not exist in the , an instance of the CI is created. If a CI already exists in the , the values of the CI from the package resource overwrites the values of the CI in the .

• datamodelcreateonly. Used to import CI instances into the system. If the CI does not exist in the , an instance of the CI is created. If a CI already exists in the , the values of the CI from the package resource does not overwrite the values of the CI in the .

• datamodelgenerateids. Used to import CI instances into the system for CITs that require the ID to be calculated dynamically upon deployment (such as CITs with no key attributes).

• dataStore. Contains the integration point defintion.

• discoveryConfigFiles. Configuration files include properties and parameters that are needed to discover components on the system. For details, see "Adapter Configuration" in the Data Flow Management section of the UCMDB Help.

• discoveryJobs. A Data Flow Management (DFM) job includes configuration data, scheduling information, and TQL assignments needed to activate discovery of components. For details, see "Introduction to Universal Discovery" in the Data Flow Management section of the UCMDB Help.

• discoveryModules. A DFM module includes all the jobs needed to discover a specific component in the system. For details, see "Introduction to Universal Discovery" in the Data Flow Management section of the UCMDB Help.

• discoveryPatterns. DFM adapters define which code to run and in which order, declare the input and output CI Types and parameters to be configurable on the DFM jobs related to them. The adapater can be used as an integration adapter or a Discovery adapter. For details, see "Adapter Configuration" in the Data Flow Management section of the UCMDB Help.

• discoveryResources. External resources include all external resources that are needed in DFM, for example, a Visual Basic file, an additional jars file, and so on. For details, see "Adapter Configuration" in the Data Flow Management section of the UCMDB Help.

• discoveryScripts. DFM Jython scripts populates the with data, either by performing Discovery on a network component or during integration with an external data repository. For details, see "Adapter Configuration" in the Data Flow Management section of the UCMDB Help.

• discoveryWizard. Used to define the Discovery Activity dialog box contents. For details, see the section on discovery activities in the Universal CMDB Discovery and Integrations Content Help.

• enrichment. Enrichment rule definitions. For details, see "Enrichment Manager" in the Modeling section of the UCMDB Help.

• identification. Contains the identification defintion of a specific CI type.

• integrationUsers. Used to define a user of type integration.

• modelnotification. Contains filter definitions for model notifications. The data model notification system gives notification of changes that occurred in the . For example, items in the that have been removed, updated, or added.

• report. Report rule definitions, as described in "Topology Reports Overview" in the Modeling section of the UCMDB Help.

• schedulerJob. Tasks that have been defined to run in the Scheduler. For details, see "Scheduler" in the Administer section of the UCMDB Help.

• singletqlref. Contains TQL template and perspective instances. For details, see "Modeling Studio" in the Modeling section of the UCMDB Help.

• tql. TQL query definitions. For details, see "Topology Query Language (TQL) Overview" in the Modeling section of the UCMDB Help.

• typedef. Predefined Enumeration definitions that relate to attributes of type Enumeration, such as severity levels, admin states, and so on. For details, see "System Type Manager" in the Modeling section of the UCMDB Help.

• users. The definition of a user and the user's role. For details, see "Users and Groups" in the Administer section of the UCMDB Help.

• validlinks. All predefined, valid connections (relationships) between CITs.