

Installation Guide › Upgrade from Previous Versions › Post-Installation Activities (from Upgrade)
Post-Installation Activities (from Upgrade)
This section explains the activities you must perform after upgrading in order to complete the upgrade and restart CA Business Service Insight.
Follow these steps:
- Start the website.
- (Optional step) To change from a public to a private synonym, invoke one of the following procedures on the database:
begin
prc_recreate_all_synonyms ('YES');
end
-OR-
exec prc_recreate_all_synonyms ('YES');
- (Optional step) Lock the OBLIDBADMIN account in the database, run the following while connected to the database as sysdba:
alter user oblidbadmin account lock
- (Optional step) Change the OBLIDBADMIN password, run the following while connected to the database as sysdba
alter user oblidbadmin identified by ‘<new_password>’
- Verify that the hour offset (hours from GMT) that you select for the time zone matches the definition of the hours offset from the time zone name you select. When defining the start and end dates for the daylight savings periods, verify that you set the accurate dates as they are defined in the country of the time zone you select. Failure to enter accurate information in either one of these fields leads to system malfunctions and can delay metric calculations.
- At the location where you installed ACE2 or Content Transfer, go to %OG_HOME%\log and open the file ace2_wrapper.log, or oblisync_wrapper.log. If a message regarding the Metric Registration Information formatter appears in the log, go to %OG_HOME%\bin and run MigrateClusterMetrics.exe. Once the execution is completed, the service resumes start up.
- (Optional step) Support requests forwarded by a reverse proxy to the website, place the prefix string into the value of the ProxyPrefix, key in the AppSettings section of the web.config file. This prefix string is configured to route the request to the website in the proxy configuration.
- Verify that the website is routed correctly to the reverse proxy; verify that the proxy value is spelled correctly and is entered between the two slashes ("/prefix/").
For example, if the prefix mapped to the website is “ca”, then the web.config file is updated as follows:
<appSettings>
<add key="ProxyPrefix" value="/ca/" />
</appSettings>
If the ProxyPrefix key does not exist, or if its value is an empty string, the website functions in normal mode.
- Add a header to the proxy configuration. The header key must be as follows: "X-Forwarded-CA-Oblicore-Proxy".
For example, if the Oblicore web application proxy access URL is http://proxy/ca/ (ca is the prefix), then the web.config file is updated as follows:
<appSettings>
<add key="ProxyPrefix" value="/ca/" />
</appSettings>
In addition to this update, a new header is added in the proxy web application configuration with the following key name: "X-Forwarded-CA-Oblicore-Proxy".
- Update the API interface in order to take into account the changes done to the current version (for detailed information, see API Backwards Compatibility in the CA Business Service Insight SDK Guide). This is mandatory if you want to use the API code from versions before version 8.1.
Update the API to version 8.x
- Use the WSDL from [assign the version number for your book] to create the Proxy classes for the Contract Service, Portfolio Service and Repository Service. If you are upgrading from a version earlier than 8.0, use the WDSL from the last installation.
- Recompile your API code.
If there are compilation errors:
- Locate the code that requires manual changes and update it according to the changes made to the new API (field order, type, and so on.).
- Recompile your API code again after making these changes.
Upgrade Log Files
When you upgrade from previous versions, CA Business Service Insight generates two log files:
|
OG8.xMigration.log
|
- The OG8.xMigration.log file is always present and always contains the entries of the last run only.
- For the first upgrade (or when no log files from a previous upgrade exist) all upgrade log entries are written here. No other log file is present upon completing the first upgrade.
- Starting at upgrade #2 (or whenever the log file OG8.xMigration.log already exists) the contents of this file are moved and appended to the OG8.xMigrationHist.log file before the upgrade begins.
|
|
OG8.xMigrationHist.log (upgrade history)
|
- The file OG8.xMigrationHist.log is a historical upgrade file; it is created at the second upgrade and contains the entries of all upgrades previous to the current upgrade.
- At the beginning of each subsequent upgrade, the contents of OG8.xMigration.log (the previous upgrade) are moved and appended to this file.
|
Update Password Utility
The Update Password utility modifies passwords in the CA Business Service Insight services, the CA Business Service Insight COM+ engine and Oracle DB. The utility works with CA Business Service Insight versions 8.x and higher.
Run the Update Password utility after you change any of the following passwords:
|
Windows password
|
After you change the Windows password, run the Update Password Utility and enter the new password. The utility modifies services account, passwords, and COM+ engine credentials according to the password you enter. Only CA Business Service Insight services which using the user account credentials and not ‘Local system’ account are changed.
|
|
Oracle credentials
|
The Update Password utility enables you to change the Oracle DB password for each of the various database users that CA Business Service Insight uses:
- Sla, Mtn, Csl, Edr, Psl, Rpt 'Obl'
|
Note: When you change the Obl (oblicore) password, the utility modifies the registry.xml and these two files:
- oblisync-ds.xml
- ace2-ds.xml.
Note: The 'insight' user DBSource.properties also changes.
On clean installations, the path to the utility is
C:\Program Files\CA\Cloud Insight\Utilities\PassUpdate\PassUpdate.exe.
For upgraded installations, the path to the utility is
C:\Program Files\Oblicore\Utilities\PassUpdate\PassUpdate.exe.
Copyright © 2012 CA.
All rights reserved.
 
|
|