Download
1.Go to Oracle Delivery Cloud and sign in
2.Select ‘Siebel CRM’ as the Product Pack and an appropriate platform. You’ll still, for some infuriating reason, find 8.1.1.x under 32-bit Windows and 8.2.2.x under 64-bit Windows. Very 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 JAVA_HOME variable, if required. For example: set JAVA_HOME=”E:\Java\jre6?
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, it’s now unzipping the JAR files into appropriate installers
Install
1.Installation is the same as you would expect, if you have installed 8.1.1.8 or 8.2.2. Check out my earlier article for some gotchas on the new installation process
2.You’ll still get the stupid “you’re about to install into a non-empty directory” message. For a patch? Really?
3.The patch process also takes ages. This, I suspect, is because the installer recognises it’s 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 you’ve installed Enterprise, Web Server, Web Client and Tools (very important!) you’re ready for the next step
Enable Open UI
1.First up, you won’t find the instructions for enabling OpenUI in the patch documentation. Instead, refer to MOS article 1499842.1 for a Deployment Guide for Open UI
2.Unzip ‘OpenUI_Base_8119.zip’ from within the Siebel Tools REPPATCH folder. Here you’ll 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 – it’s all documented in the instructions
4.Run the import batch file and check the result in the Notifactions\Log folder. I chose ‘Import All Packages’ to save time. This 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 it’s 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 ‘SSEOUIObjMgr_enu’ and the Virtual Directory and eapps entry ‘sales_openui_enu’. You can use the editmetabase.exe tool in the SWE bin folder to do this (metabaseedit.exe sales_openui_enu E:\sba81\SWEApp\BIN\ENU\eapps.mtb)
10.Restart everything, just to be sure
The advised high-level roadmap for customers follows:
1. Upgrades to a release compatible with Open UI.
2. Implement Siebel 8.1.1.9 or 8.2.2.2 or above.
3. Apply QF’s applicable to the release
4. Migrate from SEA to SIA if on a SEA release.
5. Import Open UI related SIF files.
6. Read FAQs and other release documentation provided for the migration.
7. Add an object manager for the UI, and set it to Open UI using the Open UI enablement settings.
8. Test the upgraded deployment on HI and SI.
9. Test the Open UI client rich internet application (RIA) deployment. This can be tested in parallel when running the environment because it runs on a separate object manager).
10. Perform user-acceptance testing for all the deployed client UI options.
Configuration
Overview: High level configuration steps
To deploy Siebel Open UI, several steps must be followed.
1.Download the Innovation pack 2012 release.
2. Import your seed data using the provided batch files
3. SIF files for import are provided to enable Open UI and Siebel Mobile features. These must be imported.
4. Compile & deploy the new SRF
5. 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. Add Virtual directories as needed.
8. 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.
10. Tune Web Server performance for your environment and web server type.
Siebel Tools contains the following zip files in the REPPATCH folder.
1. OpenUI_Base_8119.zip or OpenUI_Base_8222.zip
2. OpenUI_Mobile_8119.zip or OpenUI_Mobile_8222.zip
Note: If you have run previous versions of Seed or SIF data import run the steps below to update the information.
Note: Siebel Tools requires use with Internet explorer 8.
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.
1. Back up your target database.
2. Create an ODBC entry for the database where you plan to import the seed data into.
3. Open your tools.cfg file and change SymStrPrefix=X to SymStrPrefix=SBL.
4. Create new projects as specified in the beginning of projects_and_objects.txt.
5. Check out or lock the projects specified in the "Projects to Lock/Check Out" section in projects_and_objects.txt.
6. Ensure language.txt contains the language codes of the languages you need with each code in a separate line.
7. This step is optional, but recommended. Specify environment information in preference.txt.
8. You will be prompted for the information for entries that are left blank.
- REPOTOOLSBIN=<path, where to find siebdev.exe, e.g. C:\siebel\tools\bin>
- REPODATASOURCE=<DataSrc entry from tools.cfg, where to import the objects into>
- REPOUSERNAME=<User Name>
- REPOPASSWORD=<Password>
- DBTYPE=<ORACLE|MSSQL|DB2UDB> (i.e. the data base vendor)
- DDLPATH=<path that contains ddldict.exe and ddlimp.exe, usually <Siebsrvr>\bin>
- SIEBUSER=<Siebel Username>
- SIEBPW=<Siebel Password>
- ODBCDATASOURCE=<ODBC DataSource Name> (i.e. the name of the ODBC data source reated in step 2)
- TBLO=<Table Owner>
- TBLOUSER=<Table Owner User> (only needed for MSSQL)
- TBLOPW=<Table Owner Password>
- Run import.bat.
9. Verify the import logs in <package>\Log for all imported packages.
10. Compile the repository to create a new srf with the new and modified objects, which are listed in projects_and_objects.txt.
11. Open your tools.cfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X.
12. Verify the import logs for the seed data in <package>\Seed\<DBTYPE>.
13. Please bounce your server (or restart your mobile web client) after completion of deployment of the new SRF file.
14. Perform configurations according to the “Additional Instructions” documents in the subfolders, if such documents exist.
Adding Siebel Open UI Object Managers To set configuration for Siebel Web Client via server object managers, set the parameters in Application Server Configuration> Component Parameters as follows:
To render as High Interactivity client:
1. EnableOpenUI=FALSE
2. HighInteractivity=TRUE
To render as Open UI client:
1. EnableOpenUI=TRUE
2. HighInteractivity=TRUE
Enabling and Disabling Open UI on clients To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration, set the client parameter, in uagent.cfg in the [InfraUIFramework] section as follows:
To render as High Interactivity client:
1. EnableOpenUI=FALSE
2.HighInteractivity=TRUE
To render as Open UI client:
1. EnableOpenUI=TRUE
2. HighInteractivity=TRUE
Backing up configuration and setting Environment variables
1. Stop Siebel Server.
2. Stop Gateway Server and make backup of siebns.dat file.
3. Restart Gateway Server.
4. Set SIEBEL_HOME environment variable to SES_HOME/siebsrvr directory.
5. Start Siebel Server and make sure that components are online (assumption: Srf used by Siebel Server is the resulting SRF after SIF import)
1.Go to Oracle Delivery Cloud and sign in
2.Select ‘Siebel CRM’ as the Product Pack and an appropriate platform. You’ll still, for some infuriating reason, find 8.1.1.x under 32-bit Windows and 8.2.2.x under 64-bit Windows. Very 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 JAVA_HOME variable, if required. For example: set JAVA_HOME=”E:\Java\jre6?
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, it’s now unzipping the JAR files into appropriate installers
Install
1.Installation is the same as you would expect, if you have installed 8.1.1.8 or 8.2.2. Check out my earlier article for some gotchas on the new installation process
2.You’ll still get the stupid “you’re about to install into a non-empty directory” message. For a patch? Really?
3.The patch process also takes ages. This, I suspect, is because the installer recognises it’s 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 you’ve installed Enterprise, Web Server, Web Client and Tools (very important!) you’re ready for the next step
Enable Open UI
1.First up, you won’t find the instructions for enabling OpenUI in the patch documentation. Instead, refer to MOS article 1499842.1 for a Deployment Guide for Open UI
2.Unzip ‘OpenUI_Base_8119.zip’ from within the Siebel Tools REPPATCH folder. Here you’ll 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 – it’s all documented in the instructions
4.Run the import batch file and check the result in the Notifactions\Log folder. I chose ‘Import All Packages’ to save time. This 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 it’s 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 ‘SSEOUIObjMgr_enu’ and the Virtual Directory and eapps entry ‘sales_openui_enu’. You can use the editmetabase.exe tool in the SWE bin folder to do this (metabaseedit.exe sales_openui_enu E:\sba81\SWEApp\BIN\ENU\eapps.mtb)
10.Restart everything, just to be sure
The advised high-level roadmap for customers follows:
1. Upgrades to a release compatible with Open UI.
2. Implement Siebel 8.1.1.9 or 8.2.2.2 or above.
3. Apply QF’s applicable to the release
4. Migrate from SEA to SIA if on a SEA release.
5. Import Open UI related SIF files.
6. Read FAQs and other release documentation provided for the migration.
7. Add an object manager for the UI, and set it to Open UI using the Open UI enablement settings.
8. Test the upgraded deployment on HI and SI.
9. Test the Open UI client rich internet application (RIA) deployment. This can be tested in parallel when running the environment because it runs on a separate object manager).
10. Perform user-acceptance testing for all the deployed client UI options.
Configuration
Overview: High level configuration steps
To deploy Siebel Open UI, several steps must be followed.
1.Download the Innovation pack 2012 release.
2. Import your seed data using the provided batch files
3. SIF files for import are provided to enable Open UI and Siebel Mobile features. These must be imported.
4. Compile & deploy the new SRF
5. 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. Add Virtual directories as needed.
8. 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.
10. Tune Web Server performance for your environment and web server type.
Siebel Tools contains the following zip files in the REPPATCH folder.
1. OpenUI_Base_8119.zip or OpenUI_Base_8222.zip
2. OpenUI_Mobile_8119.zip or OpenUI_Mobile_8222.zip
Note: If you have run previous versions of Seed or SIF data import run the steps below to update the information.
Note: Siebel Tools requires use with Internet explorer 8.
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.
1. Back up your target database.
2. Create an ODBC entry for the database where you plan to import the seed data into.
3. Open your tools.cfg file and change SymStrPrefix=X to SymStrPrefix=SBL.
4. Create new projects as specified in the beginning of projects_and_objects.txt.
5. Check out or lock the projects specified in the "Projects to Lock/Check Out" section in projects_and_objects.txt.
6. Ensure language.txt contains the language codes of the languages you need with each code in a separate line.
7. This step is optional, but recommended. Specify environment information in preference.txt.
8. You will be prompted for the information for entries that are left blank.
- REPOTOOLSBIN=<path, where to find siebdev.exe, e.g. C:\siebel\tools\bin>
- REPODATASOURCE=<DataSrc entry from tools.cfg, where to import the objects into>
- REPOUSERNAME=<User Name>
- REPOPASSWORD=<Password>
- DBTYPE=<ORACLE|MSSQL|DB2UDB> (i.e. the data base vendor)
- DDLPATH=<path that contains ddldict.exe and ddlimp.exe, usually <Siebsrvr>\bin>
- SIEBUSER=<Siebel Username>
- SIEBPW=<Siebel Password>
- ODBCDATASOURCE=<ODBC DataSource Name> (i.e. the name of the ODBC data source reated in step 2)
- TBLO=<Table Owner>
- TBLOUSER=<Table Owner User> (only needed for MSSQL)
- TBLOPW=<Table Owner Password>
- Run import.bat.
9. Verify the import logs in <package>\Log for all imported packages.
10. Compile the repository to create a new srf with the new and modified objects, which are listed in projects_and_objects.txt.
11. Open your tools.cfg file and change SymStrPrefix=SBL_ back to SymStrPrefix=X.
12. Verify the import logs for the seed data in <package>\Seed\<DBTYPE>.
13. Please bounce your server (or restart your mobile web client) after completion of deployment of the new SRF file.
14. Perform configurations according to the “Additional Instructions” documents in the subfolders, if such documents exist.
Adding Siebel Open UI Object Managers To set configuration for Siebel Web Client via server object managers, set the parameters in Application Server Configuration> Component Parameters as follows:
To render as High Interactivity client:
1. EnableOpenUI=FALSE
2. HighInteractivity=TRUE
To render as Open UI client:
1. EnableOpenUI=TRUE
2. HighInteractivity=TRUE
Enabling and Disabling Open UI on clients To set configuration for Siebel Dedicated and Mobile Web Clients via client configuration, set the client parameter, in uagent.cfg in the [InfraUIFramework] section as follows:
To render as High Interactivity client:
1. EnableOpenUI=FALSE
2.HighInteractivity=TRUE
To render as Open UI client:
1. EnableOpenUI=TRUE
2. HighInteractivity=TRUE
Backing up configuration and setting Environment variables
1. Stop Siebel Server.
2. Stop Gateway Server and make backup of siebns.dat file.
3. Restart Gateway Server.
4. Set SIEBEL_HOME environment variable to SES_HOME/siebsrvr directory.
5. Start Siebel Server and make sure that components are online (assumption: Srf used by Siebel Server is the resulting SRF after SIF import)
No comments:
Post a Comment