Attachmate Management & Control Services Version 3.0

Release Notes

April 2005

Introduction

Management & Control Services (MCS) is a Web-based server console that you can use to centrally manage and configure compatible Attachmate products and components.

Back to top


Known Issues

Clustering

Enabling the Replication Timer

If you install MCS in a clustered environment, the server's replication timer is not enabled by default. This service is used for ensuring that data is replicated across servers in a cluster. It checks to make sure that a server has not gone offline when replication takes longer than it should.

If a server does go offline during replication, the replication timer removes it from the queue and begins replication to the next server in the cluster. If you do not enable the replication timer and a server goes offline during data replication, the replication process is suspended at that server.

To enable the replication timer, you'll need to edit the scm.properties file for the primary server in your cluster, located in the /mcs/WEB-INF/data/mcs/scm directory, and then restart all secondary servers.

To enable the replication timer
  1. On the primary server, open the file scm.properties in a text editor.

  2. Locate the line ending =ReplicationTimer, and change InitialState=down to InitialState=up two lines below.

  3. Save your changes.

  4. Restart all secondary servers in the cluster.


Modifying Connection Information for Servers in a Clustered Environment

If, after installation, the IP address, host name, or port number of a secondary server in your cluster changes, you need to manually reconfigure values at the primary server, and then restart all servers in the cluster so that they are updated with the changes.

If the IP address, host name, or port number of your primary server changes, you need to manually reconfigure values for the primary server on all servers in the cluster.

Note This procedure is necessary only if you work in a clustered environment. If you work in a single MCS server environment, a change in its address can be automatically detected.

The following procedure assumes that your Web server has also been updated with the new values.

To manually update connection information for a secondary server
  1. On your primary MCS server, change the following values:

    In
    Change
    mcs/WEB-INF/data/servermgt/server/1000n.xml

    where n is the server number of the affected server. For example, 10001.xml is the XML file for the primary server.
    The following attributes to the <server> element:

    address,
    name, and/or
    port.

  2. Restart all other servers in the cluster so that they are updated with the change.

To manually update connection information for your primary server
  • On all servers in the cluster, change the following values:

    In
    Change
    mcs/WEB-INF/data/servermgt/server/10001.xml The following attributes to the <server> element:

    address,
    name, and/or
    port.


Back to top

Directory Services


OS/390 LDAP Interface to RACF Requires OMVS Segments

If MCS is installed under OS/390 USS and using the LDAP interface to RACF for the directory service, each user that requires MCS access must have an OMVS Segment in their userid (in RACF) in order to be properly authenticated.


Directory List Displays "Unable to load this node" Message

If you attempt to view the directory list and instead are presented with a repeating message, "Unable to load this node," check to make sure that the directory service has been correctly configured.


Back to top

Events

Using HTTP Transport for Event Messages

When modifying a message in the event system, if you use the HTTP transport, you cannot change the content from Field Selector to Entire Event after selecting fields. If you want to include the entire event, you'll need to select all fields or create a new message.


Adding Users to Views

If after assigning a user to a view, you click Check Names, the Next button becomes unavailable, which means that you cannot add hardware restrictions. To make the Next button available, delete the user and then assign the user again and do not click the Check Names button.


Using Events in a WebLogic 7.0 Environment with JVM 1.3.x

These issues can be resolved by upgrading to JVM v. 1.4.2_02.


When Searching for Events, Message Incorrectly Displayed

Under certain conditions, the following message is displayed even when events that match the search criteria have actually been found on the current page:

Event found on page not currently in view.

If there are matching events on the current page, when you dismiss the message the Find Previous and/or Find Next buttons on the toolbar will be enabled.


Back to top

Installing and Upgrading

MCS Upgrade Intermittently Fails When the Windows Services Window is Open

You can avoid this problem by making sure that the Services window (available through Administrative Tools or the Microsoft Management Console) is closed before you begin the upgrade.


Stopping and Restarting the Application Server when Upgrading

As part of the upgrade process, the application server is automatically stopped and restarted. If the server is busy and does not respond to the stop request, a message is displayed. The application server must be stopped before MCS can be upgraded. If the automatic restart fails, you can safely continue the upgrade but you must restart the application server manually when the upgrade is complete.


Web Server Must be Configured to Allow Both Secured and Unsecured Connections

Before installing MCS, make sure that your Web server's secure only option is cleared. This ensures that you can successfully install MCS, and provide access using either a secured or an unsecured connection, as necessary.


Installing MCS with Windows XP SP2

During installation, you may see a Windows security alert one or more times. This message is displayed only if you use Windows XP with the Windows XP firewall enabled (as it is by default). The message asks you if you want to keep blocking the program java or javaw. To continue with the installation, when you see this message, click Unblock.

After you click Unblock, these programs are logged in the Windows Firewall Exceptions page. Although not evident on this page, the entire path to the program has been saved. Running either program from the logged location will not display the security alert; however, running them from a different location will display the alert.


Installing with WebSphere 5.1

When installing with WebSphere 5.1, if you specify a Wsadmin user ID but no password, the installation fails. If you specify neither or both, MCS is successfully installed.


Localhost Setup in UNIX and USS Environments

In order to install and run successfully in UNIX and USS environments, you must set the following values in your /etc/hosts or hosts file.

loopback
127.0.0.1
localhost

Back to top

Miscellaneous

Default Security Option in Windows XP SP2 Restricts JavaScript in Help

The MCS help uses JavaScript. Windows XP SP2 includes the security option Local Machine Zone Lockdown, which by default restricts JavaScript from running in Internet Explorer. If you use Internet Explorer, by default, when you attempt to display the help, a message is displayed in the Information bar stating that Internet Explorer has restricted the help from showing active content.

To display the help, click the Information bar, and then click Yes to allow active content. You must do this each time you view the help.

Alternatively, you can lower your security settings to avoid seeing this message. However, this change will apply to all files that include active content, and Microsoft does not recommend this approach. For more information about Local Machine Zone Lockdown, see the Microsoft Web site.


Using MCS with Windows XP

If you use MCS with Windows XP, you may experience some irregularities in the user interface. MCS functionality is not affected.


Internet Explorer Security Settings

If your Internet Explorer (IE) security settings are set to High, you will not be able to run some of the Java applets necessary to display various property pages in the MCS console window. Various IE error messages will be displayed regarding security and script errors.


Null Pointer Exception when Configuring Tasks with Synapta Services Builder

If you experience an Null Pointer Exception after clicking Apply All Changes on the Task Configurations page when attempting to configure tasks in one of the Attachmate Synapta Services Builder products, make the following changes to your Runtimes.jsp and ClientTasks.jsp files. By default, these files are located in the C:\Program Files\Attachmate\HTTPEngine\webapps\mcs\resources\clientconfig directory on your MCS server.

In the file Runtimes.jsp, do the following:

  1. Locate the following lines near the top of the file:
    <%@ page import="java.util.Set" %>
    <%@ page import="java.util.Iterator" %>
    <%@ page import="com.attachmate.common.clientconfig.services.Messages" %>
    <%@ page import="com.attachmate.common.clientconfig.services.TaskConfigurationDatabase" %>
    <%@ page import="com.attachmate.common.clientconfig.services.Runtime" %>
    <%@ include file="utils.jsp" %>
    

    After the line <%@ include file="utils.jsp" %>, insert the following:

    <%@ page import="com.attachmate.mcs.system.serviceutils.TlsServiceUtil" %>
    <%@ page import="java.util.Hashtable"%>
    <%@ page import="java.util.Map"%>
    
  2. Locate the following lines (at approximately line 80):
    else if (action.equals("apply"))
    {
        tcdb.commit();
        session.setAttribute("lastRuntimeSelected", selectedRuntime);
    }
    

    and replace them with the following:

    else if (action.equals("apply"))
    {
        Map tls = new Hashtable();
        tls.put("Req", request);
        tlsServiceUtil.setTLS(tls);
        tcdb.commit();        
        TlsServiceUtil.setTLS(null);
        session.setAttribute("lastRuntimeSelected", selectedRuntime);
    }
    

In the file ClientTasks.jsp, do the following:

  1. Locate the following lines near the top of the file:
    <%@ page import="java.util.Set"%><%@ page import="java.util.Iterator" %>
    <%@ page import="com.attachmate.common.clientconfig.services.Messages" %>
    <%@ page import="com.attachmate.common.clientconfig.services.TaskConfigurationDatabase" %>
    <%@ page import="com.attachmate.common.clientconfig.services.Runtime" %>
    <%@ page import="com.attachmate.common.clientconfig.services.ClientTask" %>
    <%@ include file="utils.jsp" %>
    

    After the line <%@ include file="utils.jsp" %>, insert the following:

    <%@ page import="com.attachmate.mcs.system.serviceutils.TlsServiceUtil" %>
    <%@ page import="java.util.Hashtable"%>
    <%@ page import="java.util.Map"%>
    
  2. Locate the following lines (at approximately line 80):
    else if (action.equals("apply"))
    {
        tcdb.commit();
    }
    

    and replace them with the following:

    else if (action.equals("apply"))
    {
        Map tls = new Hashtable();
        tls.put("Req", request);
        tlsServiceUtil.setTLS(tls);
        tcdb.commit();        
        TlsServiceUtil.setTLS(null);
    }
    

Minimum File Handles

In order to successfully run MCS in an environment that limits file handles per process, maximum file handles for the MCS process should be set to a minimum of 1000.


Sluggish Performance with WebLogic v. 7.0

If you use MCS with WebLogic v. 7.0 and JDK v. 1.3.1_08, MCS may perform sluggishly. This issue can be resolved by upgrading to JDK v. 1.3.1_12 or newer.


Using MCS Version 3.0 with Presentation Builder Version 4.0


Cannot use the Licensing Feature in Linux Environments

In Linux environments, if you attempt to install a new license certificate, an error is displayed and the attempt fails.


MCS Error Page Doesn't Display Properly in USS

If MCS is installed in a USS environment and an error page does not display correctly, for example when an access denied message should be displayed, you may need to remove a section of the file ../mcs/WEB-INF/web.xml, so that the default error page is used instead.

  1. Stop the HTTP engine.

  2. In a text editor that supports ASCII text, open the file ../mcs/WEB-INF/web.xml.

  3. Find and delete the following section, which should be located at the end of the file:
    	<error-page>
    		<error-code>403</error-code>
    		<location>/resources/403.html</location>
    	</error-page>
    
  4. Restart the HTTP engine.


Back to top

Security

Unable to Connect Using TLS Only

If you select the option Use TLS Only on the Security Services Configuration page, you will not be able to access the MCS console using a secure connection because of incompatibilities between Internet Explorer and the Java plug-in. You will still be able to access the MCS console with an unsecured connection unless you also selected Force 128-bit Encryption.

If you cannot access the MCS console because both of these options are selected, you'll need to edit the SecurityGateway.properties file directly to change their values. The SecurityGateway.properties file is located in the ../mcs/WEB-INF/data/securitygateway/settings directory. However, if Secure the Integrity of Critical MCS Files is selected, you cannot edit the SecurityGateway.properties file directly. You will need to reinstall MCS.


Implementing RSA SecurID Authentication

If you select RSA SecurID authentication, you must ensure that the RSA server and client have been set up before you will be allowed to log in to the MCS server again. If RSA SecurID authentication is selected in error, you may need to reinstall MCS before you can log in to select a new authentication option. MCS currently supports RSA SecurID only with Windows.


Failure Using Client Certificates with Java Plug-in

If you attempt to use client certificate authentication with the Java plug-in as your default VM, a communication failure may occur. This can result in MCS menus not displaying, or not displaying properly.

This is because the Java plug-in does not use client certificates from the browser's certificate store for HTTPS client authentication. Instead, it uses a certificate store specific to the JRE. At the time of writing, information about configuring the Java plug-in for client certificate authentication could be found in the following article:

http://java.sun.com/j2se/1.4.2/docs/guide/deployment/deployment-guide/upgrade-guide/article-16.html

Exception Generated When Making a Secure Connection to MCS With Java Plug-in Cache Enabled

If caching is enabled in the Java plug-in and you attempt to make a secure connection to MCS, an exception will be logged to the Java plug-in console. This is a known bug in the Java plug-in version 1.4.2, documented on the Sun Web site in the following article:

http://developer.java.sun.com/developer/bugParade/bugs/4845728.html

Enabling the Save Button on the Security Services Configuration Page

If you have previously selected the option Secure the Integrity of Critical MCS Files on the Security Services Configuration page and you clear it, the Save button is not enabled. That is, you cannot immediately save your change.

After clearing the Secure the Integrity of Critical MCS Files check box, you can select and then clear another check box on the page to enable the Save button so that you can save your change.


Using Client Certificates That Contain Unicode Strings

If you are running MCS on either of the platforms listed below, you cannot use client certificates that contain Unicode strings in the subject distinguished name (DN) field of the certificate:

You can, however, use client certificates that do not contain Unicode strings. On Sun Solaris, you can also use Sun Java 2 SDK 1.3.x, which works with either.


Authentication Type and Rights Management

If you do not require user authentication for accessing the MCS console (Authentication Type = None), all users will have all MCS rights, regardless of your selections under Rights Management.


Back to top

  Attachmate