Siebel Tools is an integrated environment used by developers for configuring Siebel Business Applications.NOTE: This topic includes instructions for installing Siebel Tools as a new installation or as a migration installation.
For an existing installation, you perform a migration installation instead of a new installation. Youll still, for some infuriating reason, find 8.1.1.x under 32-bit Windows and 8.2.2.x under 64-bit Windows. Siebel Client Ation And Administration Guide Download The 5Very odd 3.Download the 5 ZIP file components of the installation and unzip them all to a common folder 4.Open up a command prompt, as administrator, and CD to the unzip folder 5.Set the JAVAHOME variable, if required. For example: set JAVAHOMEE:Javajre6 6.Run snic.bat 7.Create a new image, patch set 8.Go through the usual process of selecting desitnation, platform and components and pick one or more languages 9.Though it looks like the JAVA process has frozen crashed, its now unzipping the JAR files into appropriate installers. This, I suspect, is because the installer recognises its own instability and does a backup (i.e. OS level folder copy) of the entire SIA SEA folder before it does anything. I still think Oracle have taken a huge step backwards with the clunky and unreliable installer 4.Once youve installed Enterprise, Web Server, Web Client and Tools (very important) youre ready for the next step. Instead, refer to MOS article 1499842.1 for a Deployment Guide for Open UI 2.Unzip OpenUIBase8119.zip from within the Siebel Tools REPPATCH folder. Here youll find instructions on what projects to lock and a.BAT file to import all the appropriate SIFs to enable OpenUI 3.Lock the projects, create the new Reports project then edit the preferences file appropriately its all documented in the instructions 4.Run the import batch file and check the result in the NotifactionsLog folder. Siebel Client Ation And Administration Guide Update An ExistingThis seemed to work perfectly first time though it took forever as each SIF is imported individually, using a new Siebel Tools process 5.Perform a full compile of the SRF and deploy to your server environment 6.Now you have two choices clone an existing OM (recommended) or update an existing one to use OpenUI in place of HI. I went for cloning as, though its more involved, it allows me to access and compare my existing HI OM 7.Personally, I used the server manager scripts that were generated from the mergecfg.exe tool to create the OM. I first created a new OM component then used the scripts to update the partameters to match those of the existing Sales (SSE) OM component 8.In the parameters for the new OM, set the new EnableOpenUI parameter to True 9.In IIS, create a new Virtual Directory for your new OM and create appropriate entries in eapps.cfg to point to it. I called my OM SSEOUIObjMgrenu and the Virtual Directory and eapps entry salesopenuienu. You can use the editmetabase.exe tool in the SWE bin folder to do this (metabaseedit.exe salesopenuienu E:sba81SWEAppBINENUeapps.mtb) 10.Restart everything, just to be sure. Upgrades to a release compatible with Open UI. Implement Siebel 8.1.1.9 or 8.2.2.2 or above. Apply QFs applicable to the release 4. This can be tested in parallel when running the environment because it runs on a separate object manager). Perform user-acceptance testing for all the deployed client UI options. SIF files for import are provided to enable Open UI and Siebel Mobile features. Please bounce your server (or restart your mobile web client) after completion of the import 6. Add or clone an object manager depending on use of Siebel Mobile or Open UI 7. ![]() Set the image files based on deployment requirements 9. Use EnableOpenUI TRUE (or FALSE) to change between HI and Open UI mode. Set this parameter in the c client CFG file or in the object manager parameter as needed. Tune Web Server performance for your environment and web server type. To import the Sif file, compile and deploy the SRF with the components in the applicable SIF file (named openUI.zip) based on the instructions in the readme.txt file contained within it. Stop Siebel Server. Stop Gateway Server and make backup of siebns.dat file. Restart Gateway Server. Set SIEBELHOME environment variable to SESHOMEsiebsrvr directory. Start Siebel Server and make sure that components are online (assumption: Srf used by Siebel Server is the resulting SRF after SIF import).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |