Adding Applications

Before indexing the CloudView server, you must specify the applications to index in the config.xml file.

Applications are identified with their product trigrams, for example, DEC for X-CAD Design Management.

The table below lists the main applications and their trigrams:

Application Trigram
Engineering BOM Management ENG
IP Classification LBC
Variant Management FTR
Project Management PRG
Apparel Accelerator for Sourcing and Production? APR
High-Tech Accelerator for New Product Intro? HNP
X-CAD Design Management DEC
Manufacturing BOM Management (MFG) / Configured BOM (ECC) UEBOM

Note: By default, all fields (BOTYPEFIELDS parameter) related to an application that is not active are omitted.

Before you begin:
  • For 3DSpace Index, generate physical IDs for any object to index.
  • Open your working config.xml file, or the file used for the indexing process. The default config.xml file is located in SERVER_INSTALL\Apps\BusinessProcessServices\VERSION\Modules\ENOFramework\AppInstall\Programs.
  • Review Config.xml Parameters for information on the different parameters used in the file.
See Also
About the Index Configuration File
Adding Business Object Types
Adding Business Types Files and File Extensions
Adding Attributes to a Business Object Type
Using Aggregation Rules
  1. To activate an application and all its related fields:
    1. For name, specify the application trigram.
    2. Set the active parameter to true.

      The indexing process will include any BOTYPEFIELDS entry with this application attribute.

    For example, if your company is using the Engineering BOM Management app:

    <APPLICATION name="ENG" active="true"/>
    This means any BOTYPEFIELDS parameter with application="ENG" is included:
    <BOTYPEFIELDS name="part_engineering" application="ENG">
  <FIELD name="REL_EBOM_PART" select="to[EBOM].from.name" type="STRING"/>
  <FIELD name="REL_EBOM_PART_ID" select="to[EBOM].from.id" type="STRING"/>
  <FIELD name="SUB_WHERE_USED" select="to[EBOM Substitute].fromrel.id" type="STRING"/>
</BOTYPEFIELDS>

  2. Using MQL, define the context and apply the config.xml file.

    For more information, see Applying configuration.