How does the Siebel Remote 8 feature for Local Database Password Encryption affect Siebel Tools Developers? How to give Support the Files Required to use the Customer Local Database File.
Last updated on MARCH 02, 2017
Applies to:Siebel Tools - Version 8.0  to 8.1.1  [Release V8]
Information in this document applies to any platform.
Reviewed for relevance 29-OCT-2014.
The purpose of this document is to discuss how the new to Siebel 8 behavior of encrypting the local Siebel Remote database password and database itself affects Siebel Tools Developers.
The local tools database will contain enterprise data and user data that are specific to the remote user’s positions. Usually Siebel Tools Developer's will have multiple test positions so they can test the specific views for different users. The test positions typically don't have access to a lot of user data. The local Tools Developers get the repository data into their local database by doing a full GET for specific repositories.
Siebel Remote versions prior to Siebel 8 did not have Local Password Encryption or Local Database Encryption enabled by default. So, if the Local Developer SADMIN was extracted with the username and password of SADMIN/SADMIN, he could also use SADMIN/SADMIN for connecting to the database with dbisql.
This made it straightforward to share a local tools database and use it for Siebel web client testing. The developer would just copy the sse_local.dbf to the dedicated web client /local directory. If a developer wanted to upload a local tools dbf to Oracle Support, the only files required were the local database file sse_data.dbf and the exact username and password.
Typically if Oracle Siebel Support required a local tools database to review a custom configuration the following files were provided.
Zip of the sse_local.dbf
Zip of the webtempl directory.
These files would allow a support engineer to plug the customer’s database into their Siebel Tools installation and connect to the customer’s tools database.
The advantage to this scenario is that anyone who knew the local db username/pwd could easily move the local sse_data.dbf file to another Siebel installation and log in successfully. They could also easily log into the SQL*Anywhere database with dbisql. But this advantage could also be a security disadvantage
The local password and DBF encryption that started with Siebel 8.0 was intended for production Siebel Remote Mobile users whose databases have production data. These users could easily lose or have their laptops stolen.
So whenever it's possible, it is preferable to extract the Developers' Local DBF should be extracted without any encryption.
Encrypt client Db password = False
Client Database encryption method = NONE
srvrmgr> start task for comp DbXtract with Client=[UserName], EncryptLocalDbPwd=FALSE, EncryptLocalDbMethod=NONE
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms