Wednesday, June 9, 2010

Local Database - For Multiple Users

We had to show a demo to the Client, our server got some issues and was getting restarted every now and then. We had only one environment set up at that time. We needed something if Server will not be up then how can we show demo to the client. The option was Local Database. We needed something like what we can do with the sample database where multiple users can login into the application using same database.

In our application, we were using Position and Organization based visibility for the Cases. Call Center user creates a record and assign it to an Organization and Position. Then the users who have that position has to work on that case. We needed to show the functionality where multiple users can login into the application.

How we can create multiple users login into Local Database. One of co-author of this blog and my friend Nikhil found something. On behalf of him, I am writing down steps to run some sql commands and multiple users can login into Local databases.
  1. Open the dbisqlc with User ID Siebel and password of the user with whose Id local was extracted.
  2. Then in dbisqlc, Grant permissions for users to use the Siebel application.
  3. Run SQL 'grant connect to SSE_ROLE'.
  4. Run SQL 'grant connect to identified by '.
  5. Run SQL 'grant group to SSE_ROLE'.
  6. Run SQL 'grant membership in group SSE_ROLE to '.
  • The must already exist in the database and the must be SSE_ROLE.
  • The and in the grant command must be in UPPERCASE
Now you can grant multiple users the access to the Database. 

Sharing is the power.

Tuesday, June 1, 2010

Incremental Compile - Popup Visibility Auto All Issue

I have heard many times that there could be problem with the Incremental Compile Issue of the SRF.
I have also seen some times that there are some inconsistent issues because of Incremental Compile. Today , I saw it having issues with Incremental Compile and it has also been documented on Oracle Support aka metalink.

As we know that on BC level, there are two of the properties like Popup Visibility Auto All and Popup Visibility Type. 
Ideally, It should work like if Popup Visibility Auto All is TRUE and the Login User has responsibility to see All Across Organization View, then "Popup Visibility Auto All" will override the Popup Visibility Type value.

For eg. Let's say User ANWALIA(myself) has responsibility to see All Contact Across Organization View. The Contact BusComp has Popup Visibility Auto All as TRUE and Popup Visibility Type as Organization.
Now because I have All Contact Across Organization View, in any popup applet used by Siebel like Associate Applet, Pick Applet etc. I should be able to see all contacts across organizations.

Here is a catch of Incremental Compile, If any buscomp has the above kind of configurations and you lets say recompilation of the Contact Screen is done, hen Popup Visibility Auto All would not work as expected. It will work based on Popup Visibility type.

This can be avoided if you compile the whole project or do a full compile.

Sharing is the power.