Indexing the 3DSpace Index Search ServerYou must index information in the 3DEXPERIENCE platform database before it is included in a Process Composer search. The full-text search server collects data extracted from the database and makes the data available for rapid retrieval. However, you must index the search server before new data becomes available to users. It is recommended that you index the search server at regular intervals; for example, every five minutes. The interval you choose depends on the size of your database and the amount of work that is being done by your users. The interval determines when changes to your database become available for users that are using the search capability. For details about indexing, see the following guide in the online documentation: Installation and Setup | Administrate | 3DEXPERIENCE Platform | 3DSpace Administration | 3DSpace Index Adding Simulation Attributes to the Search IndexingTo use simulation attributes in a search, you must add the attributes to the search server indexing by customizing the config.xml index configuration file of ENOVIA Business Process Services. See the 3DSpace Index guide in the online documentation: Installation and Setup | Administrate | 3DEXPERIENCE Platform | 3DSpace Administration | 3DSpace Index For example, you could add the following XML elements in the config.xml file: <BOTYPE name="Simulation" includes="basic,titleField,workspacesField, SCETemplateCreatedWith,SCEAttributeGroup,SCEJobStatus,SCEUpToDate,SCEJobStart, SCEJobEnd,SCEmySimAttribute"/> ... <BOTYPEFIELDS name="SCEmySimAttribute" application="SCE"> <FIELD name="SCE_mySimAttribute" select="attribute[mySimAttribute]" type="STRING,PARAMETRIC" sixw="ds6w:mySimAttribute"/> </BOTYPEFIELDS> After editing the config.xml file, reapply the changes with these MQL commands: MQL> set context user creator; MQL> set system searchindex file <path>/config.xml; Then rebuild the baseline index using this command: MQL> start seachindex mode full; |