3DLive.Environments | Defines the environment for 3DLive Examine searches. The environment is a group of business process apps. The values for this property become options in the Environment drop-down list in the 3DLive Examine Search Criteria dialog box. The next property determines the object types each environment supports. For example: 3DLive.Environments = Engineering BOM,XCAD Design | Comma-separated list of app names |
3DLive.Domains.<ENVIRONMENT_NAME> | Defines the object types available for opening in 3DLive Examine and searching from
within an environment specified above. The defined
types become options in the Object pull-down list when that environment is selected.
<ENVIRONMENT_NAME> must match an environment defined in the
3DLive.Environments property (replace spaces in the environment names with underscore characters). Use the symbolic names for the administrative types.
For example: 3DLive.Domains.Engineering_BOM = type_Part,type_HardwarePart,type_ProductConfiguration,type_Products,type_HardwareProduct | Comma-separated list of symbolic names for object types supported by the environment |
3DLive.ExpandRelationshipPattern.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | Defines the relationship names to use to expand objects when searching where <ENVIRONMENT_NAME> matches a value defined in 3DLive.Environments property, and the <OBJECT_SYMBOLIC_NAME> is
defined for that environment's 3DLive.Domains. property. In the property name, use symbolic names for object
types. For example:
3DLive.ExpandRelationshipPattern.Engineering_BOM.type_Part = EBOM | Relationship name |
3DLive.ExpandTypePattern.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | Defines a pattern for the names of objects (not the object type) that can be found when searching using the above relationship. For example: 3DLive.ExpandTypePattern.Engineering_BOM.type_Part = * In this example, any object (based on the * wildcard) connected to the Part
using the EBOM relationship should be found. If the expand type pattern property is blank, the
object is not expanded during searches.
| Pattern text, can include the * wildcard |
3DLive.ViewTable.<ENVIRONMENT_NAME>.<TABLE_SYMBOLIC_NAME> | Defines the configurable table used to display the search results.
| Symbolic name of the table. |
3DLive.ImagePaths.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | Defines how the system navigates to images for the defined object type within the specified environment. When searching
for an image, the system follows the defined paths until it finds an Image Holder object, then
checks that object for a file checked into the format defined by the next property. If none are found, the system continues
searching the defined image paths.
Provide a comma-separated list of valid MQL expressions to define the value. For each
defined image path (for an environment), you must also define the image formats. For example:
3DLive.ImagePaths.Engineering_BOM.type_Part =
$<to[relationship_ImageHolder].from.id>,$<from[relationship_PartSpecification].to.id> | Comma-separated list of MQL expressions |
3DLive.ImageFormats.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | Defines the formats to check for each path defined in the above property. If you define 4 paths, you must define 4 image formats. When following the first path, the app uses the first defined format. When following the second path, it uses the second defined format, and so on. You can provide the
same format for all paths, if appropriate. For example: 3DLive.ImageFormats.Engineering_BOM.type_Part = format_generic,format_CGR | Comma-separated list of symbolic names of image formats |
3DLive.ThumbnailPaths.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | Defines the paths/formats for a 2D image associated with a 3D image. The ThumbnailPaths property follows the same format as the ImagePaths property; the
ThumbnailFormats property follows the same format at the ImageFormats property.
| Comma-separated list of MQL expressions |
3DLive.ThumbnailFormats.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | Comma-separated list of symbolic names of image formats |
3DLive.Trace | Enables or disables debug logging. When set to true, the connector between 3DEXPERIENCE platform and 3DLive Examine generates a debug log file 3Dlive.log at this location: /server/logs/. | True or False |
3DLive.Session.ExpiryTimeInMins | Sets the number of minutes after which the server reinitializes the cached 3DLive Examine session. | Positive integer |
3DLive.SkipIntermediateNodesDuringExpand.<ENVIRONMENT_NAME>.<OBJECT_SYMBOLIC_NAME> | When true, the connector between 3DEXPERIENCE platform and 3DLive Examine ignores intermediate objects when expanding the defined object type within the defined environment. | True or False |