How to display Advanced Server Component Parameters in GUI

The Advanced Component Parameters are hidden by default to prevent user to modify them in application GUI. But we can access them with the following setting:

• Navigate to Administration-Server Configuration -> Components -> Choose Server Manager (alias ServerMgr) Component.
• In Parameters Applet Change "Show Advanced Objects" (alias ShowAdvancedObjects) to TRUE.
• Bounce Servers.

Alternatively you can use server manager command line interface command "list advanced param" to see the parameters.

Adding Logout button in Application Bar

There is a requirement as client asked us to add a Logout button directly in application bar instead of going to File-> Logout. Also it should be an image instead of button.
I have followed the following steps to achieve this requirement.

• First you need to add the custom image to the <SIEBEL_ROOT>PUBLIC\<langauge_folder>\IMAGES folder. Image I used is 'LogOut_New.png'
• Find the Container Web Page for the application you want to add the button. As I am using eCommunication, It is "CC Container Page".
• Navigate to Webpage in object explorer,choose "CC Container Page" and click "WebPage Item" child object Type.
• Create a new Webpage Item with below properties:
• Name : LogoutButton
• Type : ImageButton
• Caption-String Override : <img src="images/LogOut_New.png" alt="logout" height="24" width="24" border="0" align="absmiddle">
• Method Invoked : Logoff
• Item Identifier : 14

Compile Changes and launch application. you will see the logout button on top right corner of the application as shown in below image.

How to enable Object level Check In/Check Out in 7.7

By Default, in Siebel 7.7 and prior versions object level locking is not enabled. So we can not check out object from server repository. Also there is no 'check out object' option visible in right click context menu in Tools. Follow below steps to enable object level check out.

• Add parameter EnableObjectCOCI = TRUE in [Siebel] section of tools.cfg. This will enable option 'check out object' in right-click context menu.
• Login to tools with SADMIN login credentials connecting to Server Data source. 
• Navigate to Projects in object explorer and query for the project which the object you want to check out.
• Right click and choose Toggle Allow Object Locking.

NOTE:  You can only change the Allow Object Locking flag on the Server database using the SADMIN login ID.

If a project has the Allow Object Locking configuration file parameter set to TRUE, and the user is logged in to the server using the SADMIN user ID, the Toggle Allow Object Locking menu option is enabled. When the SADMIN user chooses this option for a project that is already set to allow object locking, a check is performed to determine whether any objects are locked on the server within the project. If there are objects locked within the project, SADMIN will receive an error message. If the project is locked on the server by someone else, the menu option for Toggle Allow Object Locking will not appear.

What are siebns.dat, srvrdefs.dat, omdefs.dat, srvrdefs.run, omdefs.run files

Answer for this question is simple to the users who are siebel administrators. we know that these file are used for the server configuration purpose. I will explain in detail the purpose of these files.

srvrdefs.dat, srvrdefs_sia.dat -- These file contains default configuration parameters of siebel enterprise.srvrdefs_sia.dat is used for SIA applications. These file is copied during siebel server installation. These files contains the definitions and attributes(parameter values, event logging levels, etc.) for enterprises,server,component groups.

srvrdefs.run, srvrdefs_sia.run -- These files are created during siebel server configuration wizard.The information from these files will be used to create siebns.dat file during siebel server start up.

omdefs.dat, omdefs_sia.dat -- These files contains the definitions and attributes for the AOM. These files are specific to language and are copied during installation.

omdefs.run, omdefs_sia.run -- These files are created during siebel server configuration wizard.

siebns.dat -- This file is created during the start up of the siebel server, which reads the siebel server parameters and components informations from this file and enables the required component groups mentioned in this file.

As we know that it is required to restart if we change the component parameter. It is because this change is not available in siebns.dat file. Once we restart siebel server, It will recreate siebns.dat file with updated configutations from srvrdefs.run, omdefs.run files.

Please share your thoughts on this article.

Image is not displayed in Verify Message Popup for Quotes/Orders

This issue is very well known but the solution is simple. It is known for those working on Order Management Module.In the Order/ Quote list applet, on clicking Verify from the menu a pop up displayed with error message shown in the below figure but the image is not displayed showing cross (X) mark.

Configuration Steps:

• Check if there is an image defined for the message type under “Administration - Order Management -> Message Types”. For the Verify button, the Message Type is "Quotes and Orders Verify - Header" and "Quotes and Orders Verify - Line Item".
• To add an image, just select a value for the bitmap field and clear the cache under the applet menu.
• Login and logout of the application and image is displayed on the verify popup applet.                 

To add a new image from your local drive, first it needs to be added to the File System, please follow the below configuration.

• We can add a new file to the file system by going to Administration - Document -> Literature and hitting the New File button.
• Select the new added image bitmap for the message types "Quotes and Orders Verify - Header" and "Quotes and Orders Verify - Line Item" in Administration - Order Management -> Message Types.

The pop-up displayed with image after above configurations.