Templates for Different Runtime Entities
The following table identifies several YAML files used for different types of configuration for Siebel CRM runtime entities, and provides sample data formats. This topic is part of Making Incremental Changes to Your Siebel CRM Deployment on OCI.
| Name/Description | Sample Data Format |
|---|---|
|
Enterprise parameters File: enterprise.yaml Add under parameters header. |
In enterprise.yaml
|
|
Server parameters File: server_edge.yaml Add under parameters header in applicable section. |
In server_edge.yaml:
|
|
Component parameters File: server_edge.yaml Add under parameters header in applicable section. |
In server_edge.yaml:
|
|
Component definitions File: comp_definitions.yaml Add under component_definitions header. |
In comp_definitions.yaml:
|
|
Component group definitions File: comp_definitions.yaml Add under component_groups header. |
In comp_definitions.yaml:
|
|
Named subsystem definitions File: named_subsystem.yaml Add under named_subsystem header. |
In named_subsystem.yaml:
|
|
Enable component group on a server File: server_edge.yaml Add under component_groups header in applicable section. |
In server_edge.yaml:
|
|
Enable components on a server File: server_edge.yaml Add under component_groups header in applicable section. |
In server_edge.yaml:
|