Compatibility Issues

• Incompatibility between Java ES 2004Q2 servers and IM on Java ES 2005Q4 (6309082)

• Incompatibilities exist in core authentication module for legacy mode (6305840)

• Agent cannot login because “Profile not in the organization” (6295074)

• Delegated Administrator commadmin utility does not create a user (6294603)

• Delegated Administrator commadmin utility does not create an organization (6292104)

Incompatibility between Java ES 2004Q2 servers and IM on Java ES 2005Q4 (6309082)

The following deployment scenario caused this problem:

• server-1: Java ES 2004Q2: Directory Server

• server-2: Java ES 2004Q2: Application Server, Access Manager, and Portal Server

• server-3: Java ES 2004Q2: Calendar Server and Messaging Server

• server-4: Java ES 2005Q4: Application Server, Instant Messaging, and Access Manager SDK

When running the imconfig utility to configure Instant Messaging on server-4, the configuration was not successful. The Access Manager 7 2005Q4 SDK, which is used by Instant Messaging (IM) on server-4, is not compatible with the Java ES 2004Q2 release.

Workaround: Ideally, the Access Manager server and Access Manager SDK should be the same release. For more information, see the Sun Java Enterprise System 2005Q4 Upgrade Guide.

Incompatibilities exist in core authentication module for legacy mode (6305840)

Access Manager 7 2005Q4 legacy mode has the following incompatibilities in the core authentication module from Access Manager 6 2005Q1:

• Organization Authentication Modules are removed in legacy mode.

• The presentation of the “Administrator Authentication Configuration” and “Organization Authentication Configuration” has changed. In the Access Manager 7 2005Q4 Console, the drop-down list has ldapService selected by default. In the Access Manager 6 2005Q1 Console, the Edit button was provided, and the LDAP module was not selected by default.

Workaround: None.

Agent cannot login because “Profile not in the organization” (6295074)

In the Access Manager Console, create an agent in Realm Mode. If you log out and then login again using the agent name, Access Manager returns an error because the agent does not have the privileges to access the realm.

Workaround: Modify the permissions to allow read/write access for the agent.

Delegated Administrator commadmin utility does not create a user (6294603)

The Delegated Administrator commadmin utility with the -S mail,cal option does not create a user in the default domain.

Workaround: This problem occurs if you upgrade Access Manager to version 7 2005Q4 but you do not upgrade Delegated Administrator. For information about upgrading Delegated Administrator, see the Sun Java Enterprise System 2005Q4 Upgrade Guide.

If you do not plan to upgrade Delegated Administrator, follow these steps:

1. In the UserCalendarService.xml file, mark the mail, icssubcribed, and icsfirstday attributes as optional instead of required. This file is located by default in the /opt/SUNWcomm/lib/services/ directory on Solaris systems.

2. In Access Manager, remove the existing XML file by running the amadmin command, as follows:

   # ./amadmin -u amadmin -w password -r UserCalendarService

3. In Access Manager, add the updated XML file, as follows:

   # ./amadmin -u amadmin -w password 
   -s /opt/SUNWcomm/lib/services/UserCalendarService.xml

4. Restart the Access Manager web container.

Delegated Administrator commadmin utility does not create an organization (6292104)

The Delegated Administrator commadmin utility with the -S mail,cal option does not create an organization.

Workaround: See the workaround for the previous problem.