Create a custom entity- Inventory

The entity schema defines the platform, entities, and fields of an asset for which the data collector collects data. You can create a new entity schema only when you do not want to use any of the predefined platforms for data collection.

To create a custom entity- Inventory

  1. Go to Settings > Schema Manager.

  2. Select Create new entity schema to launch the Create New Entity Schema wizard.

  3. In the Select or Create New Platform panel, select Create a new platform.

    In the Name box, type Custom and click Next..

    This platform is used to create the header information in the CSV file.

    See Creating a CSV file .

  4. In the Specify Entity Details panel, in the Name box, type Inventory as the name of the entity.

  5. In the Specify Entity Details pane, select Extend an existing entity.

    From the platform drop-down list, select Windows.

    From the entity drop-down list, select Machine.

    Select the folder path where you want to create the entity schema xml files and click Next.

  6. In the Add Fields panel, click Add to add new fields for the entity.

  7. In the Create New Field dialog box, create four fields as follows.

    The number of primary fields for the new entity, Inventory must match the number of primary fields of Windows Machine. The objective to create the custom entity is to include the fields to the Windows Machine asset type. You must add the primary fields of Windows Machine as the primary fields of the entity, Inventory.

    Let us add the four fields with the following details:

    Domain/Workgroup Name - Primary

    String data type

    Machine Name- Primary

    String data type

    Vendor Name

    String data type

    Address of the Vendor

    String data type

    Date/Time of Contract Expiry

    DateTime

    Click Next.

  8. In the Specify Entity Name Fields panel, select Domain/Workgroup Name and Machine Name from the Available fields list and add them to the Selected fields list.

    The added primary fields form the name of the new entity.

    From the list of Separators, select # and click Next.

  9. In the Specify References panel, from platform list, select Windows and in the Parent entity list, select Machine.

    Associate the fields of the <Windows>.<Machine> with the fields of the <Custom>.<Inventory> as follows:

    Domain/Workgroup Name

    Domain/Workgroup Name

    Machine Name

    Machine Name

    The panel lets you create relation between the new entity and an entity of the predefined platform. A parent-child relation is created between the entity of the predefined platform and the new entity that you are creating. You can associate the primary fields of the new entity with the primary fields of the parent entity to create a parent-child relation. The parent-child relation lets you collect data for the parent entity along with the child entity.

    The fields of the panel and their descriptions are as follows:

    See About referenced entity fields.

  10. In the Summary panel, review the details of the created entity and click Finish.

  11. Close the Control Compliance Suite Console.

  12. Copy the XMLs at the following paths:

    • <installdir>\Symantec\CCS\Reporting and Analytics

    • <installdir>\Symantec\CCS\Reporting and Analytics\Application Server

    • <installdir>\Symantec\CCS\Reporting and Analytics\DPS

  13. Restart the Symantec Application Server Service and the Symantec Data Processing Service and launch the Control Compliance Suite Console again.

    Now that you have a custom entity INventory that extends from Windows Machine, you can include the newly added fields to the Windows Machine.

More Information

Extending Windows Machine to include the fields from Inventory

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.