Skip to main content

How to provide access of selected Server Realated screen to a Siebel user

Requirements:

Need to provide the access of "Administrator - Server Management" to a non siebel admin user.

Process:

Created a new responsibility named "Admin-ServerManagement" with below views and added the user.

'Server Server/Task View' or 'Server Task/Info Log View' or 'Server Server/Component/Task View' or 'Enterprise Server/Server View' or Server Task History List View or Process Failure Diagnostics or 'Server Task/Parameter View' or 'Server Task/State Value View' or 'Server Task/Statistic View' or 'Server Session/Info Log View' or 'Server Session/Parameter View' or 'Server Session/State Value View' or 'Server Session/Statistic View' or 'Server Server/Session View' or 'Server Server/Compgroup View' or 'Server Server/Info Log View' or 'Server Server/Statistic View' or 'Server Server/Task View' or Batch Job Submission View or Repeating Batch Job List View or 'Server Server/Component/State Value View' or 'Server Server/Component/Statistic View' or 'Server Server/Component/Task View'

Click on the clear cache.

Logged in the user. Opened the site map to search for Administrator - Server Management screen and clicked. On click user received the below error:

SManagement SBL-DAT-00222

Form the object manager manager logs found below errors:

NameServerLayerLog    Debug    5    0003ac48643d1230:0    2023-05-02 09:30:39    10372:   CSSNSClient::Lock(), lockTime:0.001397, m_nLocks:1, m_tid:10372

GenericLog    GenericError    1    0003ac48643d1230:0    2023-05-02 09:30:39    (srsctx.cpp (275) err=2555922 sys=0) SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (GATEWAY-SR:2320).

ObjMgrLog    Error    1    0003ac48643d1230:0    2023-05-02 09:30:39    (sadbconn.cpp (176)) SBL-SDM-00109: Error from Admin Server, SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store (GATEWAY-SR:2320).

GenericLog    GenericError    1    0003ac48643d1230:0    2023-05-02 09:30:39    (srsctx.cpp (373) err=3015669 sys=0) SBL-CSO-01013: Internal: the SCC context has not been initialized

ObjMgrDBConnLog    Delete    5    0003ac48643d1230:0    2023-05-02 09:30:39    DataBase Connection was deleted at 1c9dfa40

ObjMgrMiscLog    Error    1    0003ac48643d1230:0    2023-05-02 09:30:39    (busobj.cpp (1689)) SBL-DAT-00222: An error has occurred creating business component 'Server Server' used by business object 'Server Admin'.

Please ask your systems administrator to check your application configuration.

Solution:

At this point there are two solutions. One is to provide "Siebel Administrator" responsibility to that user clear cache and test. But that user will have all the Admin/Server related views access.

Second option is to provide the admin role to newly created responsibility (Admin-ServerManagement). In this way user will have the rights to access only selected screen not all the admin related screens.

Implementation:

To achieve the second work around on Siebel App server access the "srvrmgr" on command prompt.

Open the command prompt with admin rights.

Navigate to Siebel root directory by using the following:

cd C:\Siebel\15.0.0.0.0\ses\siebsrvr\BIN\

Now login to the "srvrmgr" utility by using the following:

srvrmgr /g gateway1 /e enterprise1 /s server1 /u sadmin /p pwd

Where gateway1= Gateway name, enterprise1=Enterprise name, server1=App Server name, sadmin=base user Id, pwd=Password

After successful login now we need to provide the admin role to newly created responsibility along with the actual  "Siebel Administrator" responsibility by using following command.

change param AdminRoles="Siebel Administrator,Admin-ServerManagement" for compdef ServerMgr

cmd_srvmgr

Stop the Siebel Application services.

Now move the next step. Go to the gate way sever and stop the gaetway services and take backup of "gateway.cfg". Open the "gateway.cfg" in notepad (cfg file can be found on "C:\Siebel\15.0.0.0.0\ses\gtwysrvr\BIN\gateway.cfg" path) and add below line under "InfraNameServer" section:

NSAdminRole = Siebel Administrator,Admin-ServerManagement

NSAdminRole

Last step is to start the gateway services and than Siebel app server service and login with the user and navigate to "Administrator - Server Management" screen. It is accessible now.


Source:

https://docs.oracle.com/cd/E63029_01/books/Secur/secur_accesscontrol007.htm#i1254990

Labels:

Comments

Post a Comment

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.
Post a Comment
Read more

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...
Post a Comment
Read more

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...
Post a Comment
Read more