Known issues, limitations, and workarounds

Workaround If you do not want to upgrade the UCMDB server to version 10.33, move the UCMDB Browser embedded to UCMDB Browser Standalone.

Workaround To fix the issue, follow these steps:

• Single tenant environment

  1. Go to JMX Console > UCMDB:service=Settings Services > getInternalSetting.
  2. In the key field, enter mam.common.secure.communication.
  3. Click Invoke.
  4. Set the value of the mam.common.secure.communication setting to False.
  5. Go to JMX Console > UCMDB:service=Settings Services > getInternalSettings.
  6. Click Invoke.
  7. Go to the mam.common.secure.communication setting, and make sure that the value is False.
  8. Restart the UCMDB server.

• Multi tenant environment

  1. Go to JMX Console > UCMDB:service=Settings Services > getInternalSetting.
  2. In the key field, enter mam.common.secure.communication.
  3. Click Invoke.
  4. Set the value of the mam.common.secure.communication setting to False.
  5. Go to JMX Console > UCMDB:service=Settings Services > getInternalSettings.
  6. Click Invoke.
  7. Go to the mam.common.secure.communication setting, and make sure that the value is False.

  8. Go to JMX Console > UCMDB:service=Packaging Services >undeployPackages.

  9. In the packagesNames field, enter dynamicSettings.zip.
  10. Click Invoke.
  11. Restart the UCMDB server.

Workaround To fix the issue, follow these steps:

1. Open the ucmdb-browser.war > WEB-INF > web.xml file in a text editor.

2. In the following lines, identify the sections similar with the ones that are highlighted in red, and replace each of them with four spaces (press the Spacebar four times).

           <init-param>
               <param-name>mode</param-name>
               <param-value>SAMEORIGIN</param-value>
           </init-param>
       </filter>
       <filter-mapping>
               <filter-name>ClickjackingFilterSameOrigin</filter-name>
               <url-pattern>/*</url-pattern>
       </filter-mapping>

3. Save the file.

4. Connect to the UCMDB server using HTTP protocol.

5. Start the JBOSS server.

Workaround If you do not want to upgrade the UCMDB server to version 10.33, move the UCMDB Browser embedded to UCMDB Browser Standalone.

Workaround Upgrade the UCMDB Browser embedded to version 4.14.

Workaround If you do not want to upgrade the UCMDB server to version 10.32, move the UCMDB Browser embedded to UCMDB Browser Standalone.

Workaround Upgrade the UCMDB Browser embedded to version 4.13.

Workaround To change the language of the system categories:

1. Stop the Tomcat.
2. Change the locale.

3. Restart the Tomcat.

Workaround If you deploy UCMDB Browser in your own Tomcat, for Tomcat 8 the following line should be added to the <Tomcat_installation_folder>/conf/context.xml file:

<CookieProcessor className="org.apache.tomcat.
util.http.LegacyCookieProcessor" />

Workaround Check the address bar and if it is marked with Pop-ups blocked, allow the pop-ups for this site.

Workaround Restart the UCMDB Browser Tomcat in order for the Browser's packages to be redeployed on the new schema.

Workaround Follow these steps to resolve the issue:

• If Tomcat is started by invoking .\ucmdbbrowser\bin\startup.bat:

  1. Create the setenv.bat file (if one has not already been created).

  2. Add the set CATALINA_OPTS="–Dcom.sun.net.ssl.enableECC=false" line to the setenv.bat file.

     Note If the variable CATALINA_OPTS already exists, just append the –Dcom.sun.net.ssl.enableECC=false value to the variable.

  3. Restart the Tomcat server.

• If Tomcat is started as a service:

  1. Run the CMS-Browserw.exe file (or the tomcat7w.exe file).

  2. In the dialog box that opens, go to the Java tab, and add –Dcom.sun.net.ssl.enableECC=false in the Java Options container.

  3. Restart the Tomcat server.

Workaround Move the UCMDB Browser embedded to UCMDB Browser Standalone.

Workaround Move the UCMDB Browser embedded to UCMDB Browser Standalone.

Workaround Restart Internet Explorer.

Workaround After Configuration Manager is installed, make sure you change the port number of UCMDB Browser URL from 8143 back to 8443 (go to UCMDB UI > Administration > Infrastructure Settings Manager, locate the UCMDB Browser URL setting by searching Name with a keyword Browser, and then change the port number from 8143 to 8443 and save the change.

Workaround Restart the UCMDB Browser server.

Workaround Follow these steps to open in the Internet Explorer the widgets that can be directly embedded into Service Manager:

1. Assign the UCMDB Browser and the Service Manager to the same domain.
2. Add the UCMDB Browser and the Service Manager in the hosts file.
3. Configure the UCMDB Browser URL with a fully qualified domain name (FQDN ).

Workaround In case you use Internet Explorer 9 or 10, set Check for newer versions of stored pages to Automatically. To do that, in the Internet Explorer window, go to Tools > Internet Options > General, and then in the Browsing history section, go to Settings.

Workaround To decrease the load on the web server, do one of the following:

• Increase the maximum heap memory size on the web server.
• Decrease the session timeout specified in the web.xml file.
• Set up high availability to spread the load over multiple UCMDB Browser instances. For more information, see "Configure High Availability Mode" in the (missing or bad snippet).
• Instruct users to log out after finishing to work with the UCMDB Browser.

Workaround Follow these steps to resolve the issue:

1. Open the <UCMDB installation folder>\conf\esapi\ESAPI.properties file.

2. Add the % character to the following validators:

   Validator.HTTPCookieValue

   Validator.HTTPHeaderValue  

3. Restart the UCMDB server.

Workaround Follow these steps to resolve the issue:

1. Go to Internet Explorer, click the Tools button on the right side of the Address bar, and choose Compatibility View Settings.
2. Disable the Display intranet sites in Compatibility View option, then click Close.

Workaround Ensure that the URL is similar to the following: <https>://<server_name>:<port_number>/ucmdb-browser/ui/index.html?wp&ucmdbURL=<ucmdb_server_protocol>%3A%2F%2F<ucmdb_server_name>%3A<server_port_number>&username=..., and then follow the steps in How to Configure Access to UCMDB Home to resolve the issue.