Even if it is not a daily task, a Siebel server administrator must be able to create additional component definitions and make the respective components available in the enterprise.
The following example explains how to use the create compdef command to create a new component definition for a workflow monitor agent. Workflow monitor agents are background components that monitor the Siebel database for certain events and execute the actions defined in so-called workflow policies. When we inspect the example more closely we find that the new component definition will have an alias name of EvalWorkMon,its component type will be set to WorkMon and it will belong to the Workflow component group.
The run mode will be background. The above example also shows how to set the full name and description text for the new component definition as well as how to provide values for some In order to make the new component definition available, we must activate it using the following command:activate compdef EvalWorkMon. The activate compdef command sets the component definition's status from Creating to Active, thus enabling the instantiation of components.
However, the new components will not be available on any Siebel server before the server itself is restarted. It is highly recommended to put complex commands like the above example in text files. The reason for this is that the text file can be saved and reused later to create the same component definition in other environments, which is a very likely scenario.
Furthermore, storing the creation scripts and other frequently used commands in text files allows for easier documentation of changes. The read command can be used to open a text file and execute the commands in that file while we have a Siebel Server Manager session window open. The following example explains how to use the read command:. The Siebel Server Manager command line also allows administrators to control the assignment and enablement of component groups to Siebel servers.
The following table provides examples for assigning, enabling, disabling, and removing a component group association for a Siebel server:. As we learned in this,component groups are already pre-assigned to all Siebel servers but not yet enabled.
If our task is to enable a component group on a specific server,the only command needed would be similar to the following:. In order to speed up the start up of a Siebel server, it is beneficial to set certain components to manual start up. This will cause the component to be in shutdown state when the server is started, thus consuming no CPU or memory.
The Siebel Server Manager command to set components to manual start up mode is similar to the following example:. To set the start up mode to automatic, we can use a command similar to the following:. To view the current start up mode for a server's components, we can use a command similar to the following:. During a srvrmgr session, we can use the set server command followed by the logical Siebel server name to focus the prompt on that server.
The following table describes the commands to control server components. As discussed above, we can use the set server command followed by the logical Siebel server name to specify the target server for the commands. The examples in the table assume that the server has been set, and use the English Call Center object manager as the target component.
While the graphical user interface GUI allows administrators to store job templates and repeating job definitions for batch components,the Siebel Server Manager command line only provides commands to start tasks—the server manager term for jobs—immediately. However, if we wish to invoke a task for a background component while the Siebel server is running, the command line is the only location to accomplish that.
In the following example, we use the start task command to invoke a task for the Generate New Database component. The above command invokes a task for the Generate New Database component and passes one parameter override to the task.
Important Siebel Server Commands using srvrmgr in Windows Siebel Spool and Read commands To get all the sql generated by Siebel tools we need to spool in a local file using The following list gives an example procedure of how to use the cfgmerge utility Hi, I have a problem with spool. I need to create a text file with UTF8 format.
In my environment I have the registry parameters below: ACP: Remote logons are required to execute srvrmgr utility. The srvmgr output must be either spooled or redirected to get stored in the flat file.
For details on how to do this, refer to Document When examining these spools, we found the cause of this problem..
For every action we perform in Siebel , like navigate to view, create a new record, query for some data etc, Siebel generates a SQL query which runs at the database and data is being displayed on the UI. Siebel spool file is a text file that contains each query executed at the database. So whenever you see any performance issue like navigation on some view is taking time, query on some applet taking time , you can use this file to check for the query which is culprit and responsible for the delay.
We just need to perform the below mentioned steps to make the spool enable in the system : a Right click on the icon, which is being used to open the dedicated client. Now you will see a file gets generated with a name "spool. How I can use it for performance Issue.
As soon as you see any performance issue in the application, take the same SRF that is being used in thin-client and open a Siebel dedicated client session with the same SRF after enabling the Spool. Monday, July 25, How to find the relationship between siebel Entities. This is very common and basic question comes in our mind while we are working as a siebel developer. Through this post i am going to explain you how we can able to find the relationship between the two entities with the help of siebel Tools.
Is Guessing is the right approach?? Now we are going to have a look about the following 1. To find out the exact relation, check the "Inter Table" Column in Link object definition. If Inter Table column is specified with any value indicates means two entities are having M: M relationship with each other. If record is present and "Inter Table" property is blank it indicates those two entities are in 1:M relationship.
In Link Object definition there is no query results found then the relationship between those two entities are not in 1:M or M:M relationship.
0コメント