When attempting to install or update an instance of WebSphere Application Server (WAS) on a 64-bit operating system, the following messages can be encountered:

• Failed : Your operating system failed the prerequisites check.
  A supported operating system was not detected. Support for your operating system might have been added after the release of the product. You can continue with the installation, but the installation might not succeed.
• Install, com.ibm.ws.install.ni.ismp.actions.PopulateMultipleMaintenanceSelectionPanelAction, msg1, 6.1.0-WS-WAS-LinuxX64-FP0000023.pak. A supported platform, operating system, related operating system architecture, and bit architecture were not detected. For example, a 32-bit product for a specific operating system and operating system architecture must be installed onto a 32-bit installation with the same operating system and operating system architecture. Similarly, a 64-bit product for a specific operating system and operating system architecture must be installed onto a 64-bit installation with the same operating system and operating system architecture. Install a product that has the platform, operating system, related operating system architecture, and bit architecture which is supported by the existing installation

To resolve this issue, it is required that the target WAS instance is uninstalled completely, and then reinstalled with an updated/fixed 'maintenance.xml' file. The file must be placed into the directory 'WAS/was.primary.pak' within the WAS installation image directory.

The file can be downloaded from this IBM page: http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21268993. Detailed instructions can also be found on this page.

Pre ITIM 5.0 the recycle bin is enabled by default, which means that when an object is deleted in ITIM this object goes into the recycle bin. 

The recycle bin is disabled by default in ITIM 5, because it can reduce ITIM performance.

You can disable the ITIM recycle bin manually. To disable the recycle bin, edit the enrole.properties file and update enrole.recyclebin.enable to false.

ITIM allows a user to set how long an object should be in the recycle bin before it can be deleted using clean up scripts. enrole.ldapserver.agelimit can be set to n number of days, in the enrole.properties file.

You can manually run the script below, when necessary, to delete the aged objects in the recycle bin. It may be better to insert it in the cron table.

Windows: <ITIM_HOME>\bin\win\ldapClean.cmd
UNIX: <ITIM_HOME>/bin/Unix/ldapClean.sh

At times it may be easier to create a service-type based adoption rule with separate functions to be called for separate services than creating 2 service based adoption rules.

JavaScript "if expressions" can be used to determine which service is in process and then call the associated function for the service. The code should be something similar to this:

var serviceName= service.getProperty("erservicename")[0];
if(serviceName == <service1>){
...//function call

}

else if(serviceName == <service2>) {
...//function call
}

With TAMeb, you may have accidentally unconfigured the TAM Policy Server before you unconfigured the authorisation server or WebSEAL instances.

This creates a problem, as now there is no way to unconfigure WebSEAL once the Policy Server has been unconfigured.

The way to solve this is to just delete the flags that TAM uses to tell if a component has been configured.

For UNIX:

The flags are in the directory “/opt/PolicyDirector/.configure”, as shown below

# ls -la /opt/PolicyDirector/.configure

drwxrwxr-x  2 ivmgr ivmgr 4096 Jan  9 14:06 .

drwxrwxr-x 12 ivmgr ivmgr 4096 Feb 24 11:20 ..

-rw-r--r--  1 root  root     0 Jan  9 14:06 PDAcld-PD

-rw-r--r--  1 ivmgr ivmgr   47 Feb 18  2008 PDlic.txt

-rw-r--r--  1 root  root     0 Jan  9 13:51 PDMgr-PD

-rw-r--r--  1 root  root     0 Jan  9 13:50 PDRTE-PD

So this shows that the Authorisation server (PDAcld), the Policy Server (PDMgr) and the Runtime Environment (PDRTE) are configured. If we deleted, say, the PDAcld-PD file, then in pdconfig the Authorisation server will show as not being configured.  We can then configure the Authorisation server as normal.

For Windows:

The flags are in the registry “HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\<component>\<version>”

If you change the value of ‘Configured’ to ‘No’ - then this component will show up as not being configured. We can then configure it as normal.

Note:

As of TAMeb 6.1, WebSEAL uses the existence of the configuration file and the "status" key in the webseal-config stanza to determine which WebSEAL instances exist and their configuration state

Provisioning policies can be written to do a substring match on account attributes, using the wildcard character. Select the Regular Expression menu option in the Expression Type field, and the regular expression can be written in this form: .*<value>.*

When using regular expressions special characters must be escaped using a backslash (\), and the a wildcard is escaped using a dot. The table below details the special characters and how to escape them.