The following technical considerations or new features apply to the March 2014 Patch Release for Operations Center version 5.0:
When upgrading from Patch Release September 2013 or earlier, you must clear the Java Web Start cache, due to updates implemented for the tightened security model introduced by Oracle Java 7 Update 45.
For instructions, see Java’s Web page on clearing the Java cache.
An updated version of Sybase JDBC drivers are included in the Operations Center 5.0 March 2014 patch release. If the database was created with an earlier version of the JDBC drivers (pre 7.0.7), then it may be necessary to update the metadata accessor scripts using the scripts provided with your Sybase installation.
If receiving an Out-of-date metadata accessor information was found on this database error in the formula.trc logs, your scripts need to be updated. To determine if the scripts need to be updated, run sp_version. If a version earlier than 7.0.7 is reported, you must update your scripts. For additional information, see TID 7014672
If you have problems starting the client, you may receive an error message similar to JAR resources in JNLP file are not signed by the same certificate. Because of the tightened security model introduced by Oracle Java 7 Update 45, all .jar components, including those from third-parties, must be signed by Operations Center.
Contact Support to have your content signed.
The AgentMsglong alarm field value is now converted to HTML in order to show correctly in Operations Center historical alarm properties. If you have existing scripts that are reading this property in the original XML, you may need to change your script in order to extract the raw data without the HTML code. For more information and a script example, see Technical Information Document 701604.
The WSAPI authentication scheme can only be used for local Operations Center user accounts, and not LDAP users.
Hypertext links between documentation guides only function correctly if PDF files are viewed in Adobe Acrobat/Reader, or when using Firefox or Internet Explorer with the Acrobat Reader plug-in.
If PDF files are downloaded from the documentation Web site and viewed locally, links require and expect each PDF file to be saved in a subdirectory with the same name as the guide’s file name. For example,
/adapter_ingtegration/adapter_integration.pdf /getting_started/getting_started.pdf