Skip Headers
Oracle® Enterprise Manager Application Configuration Console Installation Guide
Release 5.3.2

E14652-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Upgrade to Version 5.3.2

Follow these steps to upgrade your Core Server installation from version 5.x.x to version 5.3.2. If you are on a version earlier than 5.x.x, you must first upgrade to a 5.x.x version before you can upgrade to 5.3.2. Note that you do not need to upgrade Application Configuration Console Clients because they do not store any data. After upgrading the Core Server, uninstall the existing Client software and install the version 5.3.2 Client.

Note:

All instructions, paths, and so forth, say 5.x.x. Substitute the specific 5.x.x version you are upgrading from.

Instructions in this appendix observe the following convention: $OACC_INSTALL refers to the Core Server installed location, for example, opt/oracle/oacc/server.

A.1 Shut Down Application Configuration Console

Make a list of installed automation modules. Log in to the Client as an administrator and select Admin > Uninstall Extension to see a list of installed automation modules.

The Application Configuration Console Server and the Clients must be shut down to upgrade. Close any running Clients, and then stop the Server. Check the server log file to verify that it has shut down. The log is located at the following path:

$OACC_INSTALL/appserver/tomcat/logs/mvServer.log

A.2 Backup and Preparation

Address the following prerequisites before running the upgrade program:

Password Unencrypted?

If you use an unencrypted password for the bind user (JNDI authentication), you must encrypt it before running the upgrade procedure. Use the encryption program appropriate to your platform (MVEncryption.bat or MVEncryption.sh) to encrypt the password. You can find them in the $OACC_INSTALL/appserver/tomcat/shared/scripts directory.

When you execute the script, it prompts you for the string to encrypt. After you run the script, edit the server_modules_registry.xml file to set the bind.user.password.encrypted value to true.

A.3 Perform Upgrade Input Validation

You must run a script to perform upgrade input validation. This script must be run on the Oracle server; it cannot be run remotely.

Before proceeding, ensure that your environment complies with the following requirements:

  1. From the command line on the Oracle server, change directory to the unzipped db/oracle/scripts directory, for example:

    cd /tmp/OaccInstall/db/oracle/scripts
    
  2. Run the script appropriate to your platform:

    validate_oracle_w32.bat (Windows) 
    validate_oracle_lin.sh (Linux) 
    validate_oracle_sol.sh (UNIX) 
    

    To accept a default value for those prompts that display a default, press Enter.

  3. Type u to perform preupgrade validation (i is for preinstallation validation, which is described in Chapter 3).

    Validation test scope? (i/u): u
    
  4. Type the name of the Oracle Service that you want to use with Application Configuration Console. If you are using the Application Configuration Console-supplied database, take the default.

    Oracle Service (default=OACCUSER): servicename
    
  5. Type the Oracle System username and password at the prompts.

    System Username (default=SYSTEM)            : username
    System Password (no default)                : password
    
  6. Type an Oracle username and password for the Application Configuration Console user. This username must be entered in all uppercase letters.

    Application Configuration Console Username (default=OACCUSER): oaccusername
    Application Configuration Console Password (no default)      : oaccpassword
    
  7. Type the full path to the lib directory under the unzipped directory. The path must not contain lib, spaces, or a trailing (back)slash.

    Path to the "lib" directory (no default): unzip_dir/v5xx_v532
    
  8. In the directory from which you ran the script (the current directory), open the validate_oracle_settings.out log file and look for the following entry at the end of the file:

    SUCCESS.  You are ready to run the upgrade_db.sql script.
    

    If the log reports errors, do not continue with database upgrade. Notify your system administrator and contact Oracle Support.

A.4 Upgrade the Database

You must run a script to upgrade the schema and stored procedures in the Oracle database used by Application Configuration Console. This script must be run on the Oracle server; it cannot be run remotely. As you run the script, specify values for the prompts based on what you entered during validation. You can find these values, excluding passwords, in the validate_oracle_settings.out log file. If the file contains multiple entries, use the values at the end, as they are the most recent. Here is a sample output from the log file:

...
Oracle Service                                         : OACCSERV 
System username                                        : SYSTEM 
System password                                        : ****** 
Application Configuration Console username             : OACCUSER 
Application Configuration Console password             : ****** 
...
Validating stored procedures directory: /tmp/OaccdbUpgrade/db/oracle
...

Perform database upgrade as follows:

  1. From the 5.3.2 Application Configuration Console installation CD, extract oacc_upg_v5xx_v532_db_setup.zip to a temporary directory on the Oracle server, such as /tmp/OaccdbUpgrade. The path to the unzip directory cannot contain spaces.

  2. From the command line on the unzipped /tmp/OaccdbUpgrade/v5xx_v532/scripts directory, run the upgrade script appropriate to your platform:

    upgrade_db.bat (Windows) upgrade_db.sh (Linux or UNIX)) 
    
  3. Type the full path to the lib directory under the unzipped directory. The path must not contain lib, spaces, or a trailing (back)slash.

    Path to the "lib" directory (no default): unzip_dir/v5xx_v532
    
  4. Type the name of the Oracle Service that you want to use with Application Configuration Console. If you are using the Application Configuration Console-supplied database, take the default.

    Oracle Service (default=OACCSERV): servicename
    
  5. Type the Oracle System username and password at the prompts.

    System Username (default=SYSTEM): username
    System Password (no default)    : password
    
  6. Type an Oracle username and password for the Application Configuration Console user. This username must be entered in all uppercase letters.

    Application Configuration Console Username (default=OACCUSER): oaccusername
    Application Configuration Console Password (no default)      : oaccpassword
    

    You should see Connected followed by a long sequence of SQL configuration commands and their results. You can safely ignore any error messages about tables or views that don't exist. At completion you should see the following message:

    *** Update of schema and stored procedures completed. ***
    

Note the existence of the setup_db.out file in the unzipped scripts directory (/tmp/OaccdbUpgrade/v5xx_v532/scripts). This file contains information that can be useful to Oracle technical support in troubleshooting situations.

A.5 Upgrade the Application Configuration Console Server

Use the Upgrade option in the Core Server installation program to upgrade your 5.x.x Server to version 5.3.2.

Note:

Do not run the installation program as root on Linux or UNIX systems. Log in as a non-root user to run the installation program.
  1. Double-click the installation file on the CD to launch the automated installation program. Optionally, you can run the program from the command line to receive console output.

    • For Windows servers: server\ApplicationConfigurationConsoleServer.exe

    • For Linux and UNIX servers: ./server/ApplicationConfigurationConsole.bin

    Click Next on the Welcome panel to proceed with the upgrade.

  2. On the Installation Type panel, select Upgrade and then click Next to proceed with the upgrade.

  3. On the Directory panel, verify the location of your existing Core Server installation and then click Next to proceed with the upgrade.

  4. On the Upgrade Server panel, verify that the Data retrieval status is Successful for the three items listed.

    If data retrieval was not successful, stop at this point and contact Oracle technical support; otherwise, click Next to proceed with the upgrade.

  5. Verify that Tomcat is not running and then click Next to proceed with the upgrade.

  6. The Core Server requires a JDK. If it is already installed on this system, you can select the second option on this panel and then specify the JDK installation directory on the follow-on panel. If the JDK is not already installed, or if it is not the required version, select the first option and it will be installed with the Core Server.

    Click Next to proceed with the upgrade.

  7. Specify the time zone in which the Core Server is being upgraded. Select a value appropriate to your geographic region from the drop-down menu. If your time zone is not listed, specify your location as a displacement from GMT/UTC in the format of '[+-}hh:mm'.

    Click Next to proceed with the upgrade.

  8. Review the summary installation and click Next to begin the upgrade.

  9. When the upgrade completes, click Finish to exit the wizard.

You have now completed the first part of the Core Server upgrade.

A.6 Run the Upgrade Script on the Application Configuration Console Server

After you complete the installation part of the upgrade, you have to run an upgrade script on the Core Server to temporarily disable the Web Reports and tracking services. Run the upgrade script appropriate to your platform.

  1. Navigate to the following directory:

    $OACC_INSTALL/appserver/tomcat/shared/scripts
    
  2. (Linux/UNIX) Before you can run scripts on Linux or UNIX, you have to change the mode. Execute the following command:

    chmod +x *
    
  3. Run the dos2unix command on all .xml and .sh files in the current directory:

    dos2unix *xmldos2unix *sh
    
  4. Run the upgrade script appropriate to your platform, as follows:

    Pre_MVUpgrade.shPre_MVUpgrade.bat
    
  5. You should see the following (or similar) confirmation messages:

    Utility to upgrade mValent server from 5.x.x to 5.3.2.
    Disabling mvwebreports.
    Disabling mvwebreports context file.
    Disabling mvtrack.
    Disabling mvtrack context file.
    

A.7 Start the Application Configuration Console Server

Following successful completion of the upgrade script, start the Core Server to verify certain log file entries.

  1. Navigate to the following directory:

    $OACC_INSTALL/appserver/tomcat/bin
    
  2. (Linux/UNIX) Before you can run scripts on Linux or UNIX, you have to change the mode. Execute the following command:

    chmod +x *
    
  3. Execute the startup script appropriate to your platform as follows:

    startup.shstartup.bat
    

    (Linux/UNIX) If you receive messages of the form "bad interpreter: No such file or directory" when trying to run the script on Linux or UNIX, it typically means that invalid characters are present as a result of copying files from Windows. Use the dos2unix command to resolve the problem, as follows:

    dos2unix startup.sh
    

    Then, run the corrected script again.

  4. Navigate to the following directory:

    $OACC_INSTALL/appserver/tomcat/logs/mv
    
  5. Check the mvServer.log file for an entry that contains the following message:

    Reload of MV_CONFIG asset completed successfully
    
  6. If you see the message, return to the following directory:

    $OACC_INSTALL/appserver/tomcat/bin
    
  7. Execute the shutdown script appropriate to your platform as follows:

    shutdown.shshutdown.bat
    

    You are stopping the Server at this point to ensure that the mvserver and mvwebreports services have the same database context the next time you start the Server.

A.8 Run the Post-Upgrade Script on the Application Configuration Console Server

Now run the post-upgrade script on the Core Server to remove the upgrade service from service_registry.xml and to enable the Web Reports and tracking services. To do so, follow these instructions:

  1. Navigate to the following directory:

    $OACC_INSTALL/appserver/tomcat/shared/scripts
    
  2. Run the post-upgrade script appropriate to your platform, as follows:

    Post_MVUpgrade.shPost_MVUpgrade.bat
    
  3. You should see the following (or similar) confirmation messages:

    Utility to upgrade mValent server from 5.x.x to 5.3.2.
    Removing the version upgrade service from service_registry.xml.
    Done removing the version upgrade service.
    Enabling mvwebreports.
    Enabling mvwebreports context file.
    Enabling mvtrack.
    Enabling mvtrack context file.
    

A.9 Upgrade Redeployed Secondary Servers

This step is necessary only if either or both of the secondary servers (tracking and Web Reports) were redeployed on the system being upgraded. For information on server redeployment, see Appendix D.

If the upgrade process detects that secondary servers have been redeployed, it creates a directory, secondaryApps, under the $OACC_INSTALL directory. If both tracking and Web Reports servers were redeployed, secondaryApps contains the following files:

mvtrack
mvtrack.xml
mvwebreports
mvwebreports.xml

To upgrade redeployed secondary servers:

  1. Ensure that all Application Configuration Console primary and secondary servers are shut down.

  2. On the Web Reports server (if applicable), back up the original files:

    1. Copy $OACC_INSTALL/appserver/tomcat/conf/Catalina/localhost/mvwebreports.xml to mvwebreports.xml.bak.

    2. Copy $OACC_INSTALL/appserver/tomcat/webapps/mvwebreports to $OACC_INSTALL/appserver/tomcat.

  3. On the tracking server (if applicable), back up the original files:

    1. Copy $OACC_INSTALL/appserver/tomcat/conf/Catalina/localhost/mvtrack.xml to mvtrack.xml.bak.

    2. Copy $OACC_INSTALL/appserver/tomcat/webapps/mvtrack to $OACC_INSTALL/appserver/tomcat.

  4. Move the Web Reports upgrade files (if applicable), from $OACC_INSTALL/secondaryApps on the primary server to the following locations on the Web Reports secondary server:

    $OACC_INSTALL/appserver/tomcat/webapps/mvwebreports
    $OACC_INSTALL/appserver/tomcat/conf/Catalina/localhost/mvwebreports.xml
    
  5. Move the tracking upgrade files (if applicable), from $OACC_INSTALL/secondaryApps on the primary server to the following locations on the tracking secondary server:

    $OACC_INSTALL/appserver/tomcat/webapps/mvtrack
    $OACC_INSTALL/appserver/tomcat/conf/Catalina/localhost/mvtrack.xml
    

A.10 If You Use UNC

If you used UNC, or Uniform (Universal) Naming Convention, in an earlier release, or if you want to use it going forward, you must takes the steps below to acquire and install third-party software, and configure Application Configuration Console to use it.

Note:

If you previouslydefined UNC endpoints, they will no longer work, unless you follow the instructions below.

To get the required JCIFS software:

  1. Point your browser at the following URL:

    http://jcifs.samba.org/src/
    
  2. Download jcifs-1.3.12.jar to a temporary directory. If this version is not available, download a later version. If the later version proves problematic, contact Support.

    Copy the .jar file to the following three locations in the Core Server installation directory:

    $OACC_INSTALL/appserver/tomcat/webapps/mvserver/WEB-INF/lib
    $OACC_INSTALL/appserver/tomcat/webapps/mvtrack/WEB-INF/lib
    $OACC_INSTALL/appserver/tomcat/webapps/mvwebreports/WEB-INF/lib
    

Note:

If you are upgrading an environment with server redeployments, you will have to copy the .jar file to the appropriate place in the installation directory on the redeployed server's host machine.

To configure Application Configuration Console for UNC support:

  1. Navigate to the following location in the installation directory:

    $OACC_INSTALL/appserver/tomcat/shared/classes
    
  2. Open authpack_specification.xml in a text or XML editor and add UNC to the first Type authpack element so that it appears as follows:

    <Type authpack="Username Password" worksWithEnpoint="FTP, SSH, JDBC, UNC" />
    
  3. Save the file.

  4. In the same directory, open endpoint_specification.xml in a text or XML editor and uncomment the <EndpointSpec type="UNC">...</EndpointSpec> element.

  5. Save the file.

A UNC option will now be available in the Application Configuration Console Client user interface.

A.11 Start the Application Configuration Console Server Again

Start the Core Server. Even if you have configured it to start as a service in Windows, you should start it using the icon or the command line so that you can see the console log messages. Also start the secondary servers, if applicable.

A.11.1 Preserve Your Certificates

If you use company-specific SSL certificates (server or root certificates) to communicate with LDAP, you will need to export them from the old JDK into the new (upgrade version) JDK. Certificates are typically stored in the JDK's cacerts file, which, following the upgrade, can be found in the following directory:

$OACC_INSTALL/mv_backup/Java/jre/lib/security

Install the exported cacerts file in the following directory of the new JDK:

$OACC_INSTALL/Java/jre/lib/security
Typically, you install certificates using the JDK's keytool binary ($OACC_INSTALL/Java/bin).

Typically, you install certificates using the JDK's keytool binary ($OACC_INSTALL/Java/bin).

A.12 Uninstall and Reinstall the Application Configuration Console Clients

There is no upgrade option for Clients because they do not store any data that needs to be upgraded. Instead, uninstall the 5.x.x Clients and then reinstall the 5.3.2 Clients. You can use the Uninstall command from the Windows Start menu, or execute the following:

$OACC_INSTALL\uninstaller\UninstallClient.exe

Before uninstalling, ensure that there are no active Client instances and that there are no .lock files in the following directory:

$OACC_INSTALL\runtime\workspace\metadata

If there are no active clients and you do see a .lock file, a client terminated abnormally. Delete any such .lock files before uninstalling. Also, don't uninstall if you want to preserve your preference settings (see the next section).

You must install at least one version 5.3.2 Client so that you can install automation modules, but you do not need to install all 5.3.2 Clients at this time.

A.12.1 Do You Want to Preserve Preferences?

You can set preferences in the Client to tailor system behavior in a variety of ways. For example, you can change display columns in tracking and comparison alerts, and make tags mandatory on provision and update operations. For descriptions of all preference settings, see the Application Configuration Console Client Online Help.

To preserve the preference settings from the previous version:

  1. Before uninstalling the old Client version, navigate to the following location:

    %USERPROFILE%\Application Data\ApplicationConfigurationConsole
    

    Where %USERPROFILE% defaults to C:\Documents and Settings\username.

  2. Save copies of the following files:

    mvApp.properties
    mvAppTrack.properties
    mvAppComparison.properties
    

    If neither of the last two files exists, it simply means that you hadn't set those particular preferences.

  3. After installing the new Client version, copy the files you saved to the following location:

    %USERPROFILE%\Application Data\ApplicationConfigurationConsole
    

The settings from the old Client version will be in effect when you start up the new Client version.

A.13 Install 5.3.2 Extensions

If you use WebSphere Automation Module or WebLogic Automation Module, start the Application Configuration Console Client and log in as an administrator, then follow the instructions that appear in Chapter 7.

If you use Windows Resource Extensions, note that OpenSSH is no longer bundled with the product. See Chapter 8 for details.

A.14 Verify Data

Log in as an administrator. Expand the My Workspace and Public Workspace folders and verify that your configuration data is there.

A.15 Mapping Considerations

Before resuming operations, consider the following issues related to file mapping in Application Configuration Console:

A.15.1 5.2.1 to 5.3.2 Upgrades and Mapping

If you are upgrading from 5.2.1 to 5.3.2, you have to update class references in mapping_registry.xml as follows:

  1. In the Navigator view, expand System Configuration > Common Configuration > MV_CORE > Resource View.

  2. Right-click mapping_registry.xml and select Open in the popup menu.

  3. In the Editor area, enable editing and then right-click and select Find and Replace.

  4. Replace all occurrences of this string:

    "com.mvalent.ext.columnar.mapping.ColumnarParser"
    

    With this string:

    "com.mvalent.ext.regexcolumnar.mapping.RegexColumnarParser"
    
  5. Replace all occurrences of this string:

    "com.mvalent.ext.columnar.mapping.ColumnarTransform"
    

    With this string:

    "com.mvalent.ext.regexcolumnar.mapping.RegexColumnarTransform"
    
  6. Replace all occurrences of this string:

    "com.mvalent.ext.properties.mapping.PropertiesParser"
    

    With this string:

    "com.mvalent.ext.regexproperties.mapping.RegexPropertiesParser"
    
  7. Replace all occurrences of this string:

    "com.mvalent.ext.properties.mapping.PropertiesTransform"
    

    With this string:

    "com.mvalent.ext.regexproperties.mapping.RegexPropertiesTransform"
    
  8. Save your edits.

  9. In the Navigator view, right-click System Configuration and select Make Configuration Changes Live.

A.15.2 Update the Mapping Registry

The upgrade process does not automatically update the mapping registry, so as not to overwrite any customized mappings that may exist in the previous version. In recent releases, new mappings have been introduced. Thus, at this point in the upgrade process, the database copy of the mapping registry typically is different from the file system copy shipped on the distribution media.

If you want to make use of the new mappings or continue to use your customized mappings, you have to update the mapping registry.

Note:

Updating the mapping registry may impact existing resource specifications and assets already loaded, depending on the mappings they use. If you intend on updating the mapping registry, Oracle recommends that you contact technical support for guidance.

To update the mappings registry, do the following:

  1. Open the existing mapping_registry.xml file and cut and paste into a text file any customized mappings you want to preserve.

  2. In the Navigator view, expand System Configuration > Common Configuration > MV_CORE > Resource View.

  3. Right-click mapping_registry.xml and select Synchronize > Update from Resource in the popup menu. This makes the Application Configuration Console database and the file system versions in synch.

  4. Merge any customizations you saved in Step 1 into mapping_registry.xml.

  5. In the Navigator view, right-click System Configuration and select Make Configuration Changes Live.

Verify that the updated list of mappings appears in the Advanced Resource Definition Parameter Configuration dialog in the Client.