Securing Information Used by the Siebel EIM Configuration Files [ARCHIVED]
(Doc ID 480948.1)
Last updated on APRIL 18, 2023
Applies to:Siebel Enterprise Integration Manager - Version 7.0.4 SIS  and later
z*OBSOLETE: Microsoft Windows 2000
Version: 7.0.3 
Database: Oracle 184.108.40.206
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3
This document was previously published as Siebel SR 38-903878051.
The existing processing uses a file called config.bat that contains the password for sadmin, we feel having an unencrypted password, in a text file, is an unacceptable security risk. I will provide a summary of the steps current used in our EIM processing to better describe our problem. Is there a way to keep the automated processing and secure the password of sadmin.
1) Using our desk-top computers we use Terminal Services to log on to the machine where the Siebel server is located.
2) Within Terminal Services, we navigate to a shared folder and execute a file called processing.bat. First the file executes a file called config.bat which sets session variables most importantly the following:
set SiebelStr=/g <server> /e Siebel_test /s <server> /u sadmin /p <password>
3) Processing.bat then launches several sql files to which populates the EIM tables.
4) Next processing.bat executes the follows command:
%SHomeStr%\siebsrvr\bin\srvrmgr %SiebelStr% /c "run task for component EIM server %EIMStr% with Config=%HomeStr%\DC\ifb\contacts.ifb, batch= 110000-110999, Errorflags=1, sqlflags=8, Traceflags=8" /o ..\logs\run_eim_contacts.log
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document