File:   4.6.0-TIV-TIM-FP0008.README             
Date:   December 16, 2005 Revised README (01/27/06)
                                     
Fixpack 4.6.0-TIV-TIM-FP0008 for APARs IY75064, IY75663, IY77051, IY77070, IY77195, IY77505, 
IY77579, IY77706, IY77718, IY77960, IY78078, IY78146, IY78383, IY78667, IY78670, IY78740, 
IY78741, IY78743, IY78754, IY78755, IY78846, IY78847, IY78848, IY78849, IY78851, IY78852, 
IY79193, IY79588, IY79589, IY79591, IY79592, IY79692, IY79693, IY79694, IY79695, IY79696, 
IY79697, IY79699, IY79700, IY79701, IY79702, IY79703, IY79704, IY79707, IY79711, IY79712, 
IY79713, IY79715, IY79776, and IY79772.

Components:  As needed for IBM WebSphere.

General Description:

This Fixpack provides fixes for APARs IY75064, IY75663, IY77051, IY77070, IY77195, IY77505, 
IY77579, IY77706, IY77718, IY77960, IY78078, IY78146, IY78383, IY78667, IY78670, IY78740, 
IY78741, IY78743, IY78754, IY78755, IY78846, IY78847, IY78848, IY78849, IY78851, IY78852, 
IY79193, IY79588, IY79589, IY79591, IY79592, IY79692, IY79693, IY79694, IY79695, IY79696, 
IY79697, IY79699, IY79700, IY79701, IY79702, IY79703, IY79704, IY79707, IY79711, IY79712, 
IY79713, IY79715, IY79776, and IY79772.

  New Problems Fixed:

    APAR:    IY79776    17048
    Symptom: Enhancement: 
             New property introduced in enRole.properties to control ITIMs behaviour encoding 
             a Challenge Response. ITIM by default converts responses to lower case before storing 
             them. Enhancement provides for administrators to chose encoding case for customization
             None implies case-sensitive challenge response enforcement.  Valid options are:
             enrole.challengeresponse.responseConvertCase=(lower|none|upper)

    APAR:    IY75064    16768
    Symptom: Various reports don't show information related to custom-defined persons.
             Note - To view information related to all custom-defined persons,
             adhoc synchronization has to be run again.
   
    APAR:    IY75663    16811
    Symptom: If configured values are differing in case, and if attribute is read only, 
             it is not displayed properly.
   
    APAR:    IY77051    16971
    Symptom: Specific script value of null in an entitlement causes Policy Enforcement to fail.
             NOTE: The following documentation change should be made in the section 
             "Account Validation Logic" of the ITIM 4.6 documentation:
             
             The existing paragraph:
             A null default or optional parameter value means that all values on the corresponding 
             attribute of a new or existing account are disallowed, except those allowed by any 
             other allowing values, but currently set values will not be removed.
             
             should be changed to:
             A null default or optional parameter value means that all values on the corresponding 
             attribute of a new or existing account are disallowed, except those allowed by any 
             other allowing values.   
             
    APAR:    IY77070    16982
    Symptom: The scheduler for Recon & Data Synchronization is broken.
   
    APAR:    IY77195    16986
    Symptom: In the field description of the formdesigner, the $ (dollar sign) gets lost, when
             you reenter the formdesigner for the gui-type dropdownbox. 
   
    APAR:    IY77505    16997
    Symptom: If a user has an extra whitespace after a property value, the parser does not work
             properly.  The parser should remove all whitespaces after a value. 
   
    APAR:    IY77579    16999
    Symptom: When viewing accounts from -> Provisioning -> Manage service -> service -> Accounts,
             then viewing the values for a non-compliant account, (orange triangle), the value for 
             'non-compliant value' is empty.  But, the value can be confirmed and does contain 
             data when viewing the full account from the service and managed account screens.  
   
    APAR:    IY77706    17004
    Symptom: When an OU name contains "&" character this results in XSL parsing error when viewing 
             details of Org Role in the OU.  
   
    APAR:    IY78078    17033
    Symptom: Null pointer exception when trying to submit a password change for an ITIM account.
   
    APAR:    IY78146    17039
    Symptom: Unable to run ldapClean.sh/bat script.
   
    APAR:    IY78383    17051
    Symptom: Update requests on DSML feed removes any attribute values not included  in the feed.
   
    APAR:    IY78667    17065
    Symptom: Logviewer gets SAX parse errors when it encounters trace entries with XML 
             data in the entry.
             Please note that input.xml should not contain xml header i.e. <?xml?>.
             The 'Wrapper Script' section in Readme.html in the following directory
                 <ITIM_HOME>\bin\logviewer 
             has been updated with this note.
   
    APAR:    IY78670    17066
    Symptom: Auditing of Provisioning Policy Drafts is lacking
   
    APAR:    IY78740    17008
    Symptom: Cannot configure certain extension nodes for entity type operations for business 
             partner entity types.
   
    APAR:    IY78741    17026
    Symptom: The ITIM userPassword values get truncated when fed to ITIM from IDI.
             NOTE: Binary attributes should be encoded to a Base 64 string in any request 
             from IDI to TIM or vice-versa. At receiver's end, these attributes should be 
             decoded from Base 64 string to get the binary value. In ITIM, only the binary 
             attributes with syntax listed in  $ITIM_HOME/data/Dsml2Schema.properties are 
             encoded or decoded, while communicating with IDI.In some cases, the syntax of 
             a particular binary attribute may not be present in Dsml2Schema.properties.
                             
             Steps to add a new attribute syntax in Dsml2Schema.properties:
             1. Open Dsml2Schema.properties file in a text editor.
             2. Add an entry for the desired binary attribute, to the file in the following 
                format:-
                syntax.binary.<ATTRIBUTE_SYNTAX_NAME>=<OID_OF_SYNTAX>
                For example, the attribute syntax of 'OctetString' is used for  some binary
                attributes in SunOne Directory Server. So to add attribute syntax of 
                octetstring, add the following entry to the file:
                 syntax.binary.octetstring=1.3.6.1.4.1.1466.115.121.1.40
             3. Save the file.
             4. Restart ITIM for the changes to take effect.    
             
   
    APAR:    IY78743    17035
    Symptom: Request remains in "View Pending Request" with "Running" status.
             NNOTE:  To clean entries from "ou=recyclebin" in ldap, use the ldapClean 
             utility provided with ITIM.
             After applying this patch follow the steps as given below:
             1. Copy itim_api.jar, itim_server.jar and api_ejb.jar from:
                $WAS_HOME/installedApps/$MACHINE_NAME/enrole.ear directory, to
                $ITIM_HOME/lib  directory.
                             
             2. For operating system other than windows:
                Edit ldapClean.sh in $ITIM_HOME/bin/unix directory, to
                include path of database driver and additional jars in classpath.
                Example - If you are using DB2 as the database, add the following line:
                          CLASSPATH=$CLASSPATH:<Path of db2java.zip>
                If your database is Oracle, add the following line:
                          CLASSPATH=$CLASSPATH:$ITIM_HOME/lib/ojdbc14.jar
                If your database is MS SQL Server, add the following line:
                          CLASSPATH=$CLASSPATH:$ITIM_HOME/lib/JSQLConnect.jar
                
                For all database types add following lines:
                          CLASSPATH=$CLASSPATH:$ITIM_HOME/lib/aspectjrt.jar
                          CLASSPATH=$CLASSPATH:$ITIM_HOME/lib/jlog.jar
                
             3. For Microsoft Windows operating system:
                Edit ldapClean.cmd in %ITIM_HOME%\bin\win directory, to
                include path of database driver and additional jars in classpath. 
                Example - If you are using DB2 as the database, add the following line:
                          set CLASSPATH=%CLASSPATH%;<Path of db2java.zip>
                If your database is Oracle, add the following line:
                          set CLASSPATH=%CLASSPATH%;%ITIM_HOME%\lib\ojdbc14.jar
                If your database is MS SQL Server, add the following line:
                          set CLASSPATH=%CLASSPATH%;%ITIM_HOME%\lib\JSQLConnect.jar

                For all database types add following lines:
                          set CLASSPATH=%CLASSPATH%;%ITIM_HOME%\lib\aspectjrt.jar
                          set CLASSPATH=%CLASSPATH%;%ITIM_HOME%\lib\jlog.jar
                             
             4. In a UNIX environment, source the DB2 environment before executing 
                ldapClean.sh.
                E.G. . /home/db2inst1/sqllib/db2profile 
   
    APAR:    IY78754    17030
    Symptom: ITIM makes too many searches with a search clause of (!(erisdeleted=y)).
   
    APAR:    IY78755    17025
    Symptom: ITIM loops while trying to search orphan accounts.
   
    APAR:    IY78846    16166
    Symptom: After submitting provisioning policy change (priority 1 was changed to priority 2).
             the Replace section of Data tab under "View Completed Requests" was showing a 
             value of 1 for priority. 
   
    APAR:    IY78847    16994
    Symptom: ACI filter expression only considers the first value of multi-valued attributes.
   
    APAR:    IY78848    17031
    Symptom: Custom report execution fails after upgrade from ITIM 4.5.1 to 4.6.
               
    APAR:    IY78849    17029
    Symptom: Get ClassNotFound exceptions when attempting to run Provisioning Policy Applications
             from ITIM 4.5.1.  Corrected API packaging in itim_api.jar in TIM 4.6.
   
    APAR:    IY78851    17037
    Symptom: Root Password of HP-UX 11i box is visible in trace.log.  ITDI adapter issue.
   
    APAR:    IY78852    17038
    Symptom: Suspending an LDAP account fails.  ITDI adapter issue
   
    APAR:    IY77960    17023
    Symptom: Fail to send notification E-mail by Work Order when multiple E-mail addresses are 
             registered in Person object.
   
    APAR:    IY77718    17006
    Symptom: The completion notfication fails witha NullPointerException whenever a Manual 
             operation, such as WorkOrder or Approval, is added to the changePassword 
             lifecycle operation.
   
    APAR:    IY79193    16943
    Symptom: The file, itim_server.jar, should not be required for the remote API 
             PersonMO.getData(..) to work.

    APAR:    IY79588    17089
    Symptom: Documentation on defining identity policies does not note that identity policies 
             are based on service definitions and not organizational containers.  For the 
             identity policies to be evaluated, they must be placed in the organization tree 
             at the same level or above the service they intend to govern.  The Infocenter
             will be updated to reflect this in a FUTURE Release of ITIM.
   
    APAR:    IY79589    17040
    Symptom: Documentation added in $ITIM_HOME/extensions for additional information that may be 
             used when working with the condition described by APAR IY78741, working with BINARY 
             attributes for user password values.
   
    APAR:    IY79591    17072
    Symptom: Provide Purge utility to purge audit and process database tables.
             We are shipping a utility that will delete old data from process and audit 
             related tables. This utility can be found in the directory -
             <ITIM_HOME>/bin/<platform>/DBPurge 
             The utility takes an integer argument and will purge all data related 
             to completed processes which are older than the specified number of days. 
             It will also delete all the data from other audit related tables that are 
             related to the deleted process. 

             For example, executing the following command will delete all completed 
             processes older then 2 days, for ITIM installed on Windows platform -
             <ITIM_HOME>\bin\win>DBPurge.bat 2
   
    APAR:    IY79592    17076
    Symptom: ClassNotFoundException thrown while trying to remove a service profile from database.
   
    APAR:    IY79692    16163
    Symptom: The user should not be allowed to import 2 identity policies with the same 
             specifications.  Prior to this fix, importing was successful and this was incorrect. 
             There should not be 2 identity policies with the same user class/services. If the 
             user manually creates 2 identity policies with the same specification, an error 
             message is given.  Import/export also needs to follow these rules.
   
    APAR:    IY79693    16843
    Symptom: Mapping and Unmapping of Account Profiles attributes not working properly for Ad-hoc 
             reporting.
   
    APAR:    IY79694    16854
    Symptom: Incremental schema synchronization not working properly for implicitly-mapped 
             attributes.
   
    APAR:    IY79695    16869
    Symptom: Problems with shell scripts for crystal reports.
   
    APAR:    IY79696    16871
    Symptom: Dormant Report not showing data in Oracle.
   
    APAR:    IY79697    16895
    Symptom: Crystal Configuration Script failing to map attributes for out-of-box reports, if they 
             are not present.
   
    APAR:    IY79699    16903
    Symptom: Unmapping "cn" attribute of Person entry causes data sync trouble.
   
    APAR:    IY79700    16948  
    Symptom: Certain Crystal Reports not showing PersonDN as the default user input (in Non-Admin).
   
    APAR:    IY79701    16949
    Symptom: Crystal version of suspended individual report not showing correct data.
   
    APAR:    IY79702    16981
    Symptom: Custom report using DN attribute of an entity, does not show correct data 
             after upgrading ITIM from 4.5.1 to 4.6.
             Documentation update:
             The only supported route of upgrade is 4.5.1 + FP50 + IF53 to 4.6. So , 

                1) If you have designed reports before applying IF 53, 
                   re-design them after applying IF 53. And then upgrade to 4.6.
                   Locate the custom reports which have used the "DN" attribute
                   in the filter section of the report.
                   For each such report do the following:
                        a. remove the filter from the custom report and save the
                           report.
                        b. Now open the same report and add the filter again and
                           save the report.
                2) Whatever new templates are designed after applying IF53 can 
                   be straightway upgraded to 4.6 .
                3) Any new templates designed at 4.6 will always work. 
                4) Report templates using policy tables can not be upgraded from 
                   4.5.1 setup to 4.6. Since there is substantial DB schema 
                   change for these reports. These updates will be updated in the 
                   ITIM 4.6 InfoCenter.
   
    APAR:    IY79703    17070
    Symptom: Exception when generating a report in BiDirectional Language function.
   
    APAR:    IY79704    17077
    Symptom: This is a performance enhancement.
             Request never completes when adding a service to an existing provisioning policy due 
             to CNTR0051E: WAS transaction timeout error.  This problem occurs when more than 200
             services already exist.
             
             In addition to installing this Interim fix, you must also change the 
             policy.message.size=25 in enrolepolicies.properties to policy.message.size=1.  
             It is also recommended to set the DB2_APP_CTL_HEAP_SZ to 2048 and to set the JVM 
             Maximum Heap Size to 1536, provided you have sufficient real memory to accommodate 
             these settings.
   
    APAR:    IY79707    17085
    Symptom: Unable to generate compliance alert, gets NullPointerException.
   
    APAR:    IY79772    17088
    Symptom: ITDI DSMLv2 Event Handler throws an exception if ITIM passes or is passed an 
             attribute name with an underscore via ITDI.
   
  Fixes in enroleagent.jar and ERMA libs.
   
    APAR:    IY79711    17014
    Symptom: When the password saved on the service form is not correct a reconciliation of the 
             service does not fail. The recon either remains in pending state or completes with 
             success.  The recon should complete with a status of failed.
   
    APAR:    IY79712    17015
    Symptom: Passwords appear in the cleartext in itim logs.
   
    APAR:    IY79713    17016
    Symptom: When user is suspended and restored the first time, the restore operation is successful. 
             If the user account is suspended again and a second restore is attempted, the operation 
             fails. 
   
    APAR:    IY79715    17017
    Symptom: FTP based agents periodically encounter process hangs or core dumps.

   Old Fixes included from previous Interim Fixes   
   
    APAR:    IY75246    16712
    Symptom: Under some conditions, LDAP upgrade fails during ITIM 4.5.1 TO ITIM 4.6 UPGRADE.
   
    APAR:    IY75251    16713
    Symptom: Under some conditions, DataBase upgrade fails during ITIM 4.5.1 TO ITIM 4.6 UPGRADE.   
   
    APAR:    IY76425    16913
    Symptom: Adding an ACI in the section, MyOrganization>ACI of the type SAP Account and 
             inserting the following filter (suggested from ITIM 4.6 documentation) : 

                (${service.erservicename}=SAP Service Test Name) 

             and specifying an itim group that should be impacted from this aci, the filter 
             does not work.
   
    APAR:    IY76868    16950
    Symptom: JavaDoc for SearchResults.size() method needs additional explanation.
    
             The following JavaDoc published for SearchResults.size() states:
               * Returns: 
               *      Total number of results returned.  If this cannot be determined
               *      then the result will be -1.
               * 
                         
             The above description is technically correct, although most common searches
             will return only 0 or -1 due to the underlying EnumeratedSearchResults 
             implementation used for SearchResults.   
             A "-1" return value means the result can not be determined.  The workaround 
             is to call toCollection() to determine the actual size.  However, this is a 
             significant performance consideration.
               This is true of the classes:
                 -- AccountSearch
                 -- PersonSearch 
                 -- ServiceSearch
                 -- DirectoryObjectSearch
                 -- RoleSearch
                 -- PrivilegeRuleSearch
                 -- SystemRoleSearch

             
             The following Search classes return the correct number of results since they use  
             the LDAPSearchResults implementation of SearchResults:
                -- AdminDomainSearch
                -- BusinessPartnerOrgSearch
                -- BusinessUnitSearch
                -- DynamicRoleSearch
                -- OrganizationalContainerSearch
                -- HostSelectionPolicySearch
                -- IdentityPolicySearch
                -- PasswordPolicySearch
                -- ProvisioningPolicySearch
                -- SystemUserSearch 
                -- CustomProcessSearch 
                -- AccountTable
                -- OrganizationSearch
                -- ServiceModel
                -- AdoptionPolicySearch
                -- JoinDirectiveSearch

    APAR:    IY77883    16819
    Symptom: SingleSignOn example uses wrong web.xml file.   
             While installing the SiteMinder singlesignon example from 
             \itim46\extensions\examples\singlesignon 
             you get a 404 error when you try to access the servlet.
   
    APAR:    IY77884    16904
    Symptom: No warning email sent to a user when using reverse password sync agent and 
             password sync fails on one resource. 
             The workflow examples have been changed to provide direction on how to use 
             password sync and return meaningful information to a user when a failure occurs.
 
    APAR:    IY77887    16956
    Symptom: When a Remote ITIM Application is secured by a WebSphere role, an exception 
             is encountered "javax.naming.NoPermissionException: NO_PERMISSION" 
             when attempting to make ITIM API calls. 
   
    APAR:    IY77888    16977
    Symptom: When creating a person, the date field is not displayed as expected.  After 
             entering required fields in the form and submitting, the following error is 
             displayed: "You are not authorized to perform this operation".  After clicking 
             'OK' to the error, the user is taken back to managed people and the person is 
             not created. Note that this fix is for Default-Date.
   
    APAR:    IY77889    16991
    Symptom: When a Remote ITIM Application is secured by a WebSphere role, an exception is 
             encountered 
                "javax.naming.NoPermissionException: 
                NO_PERMISSION" when attempting to make ITIM API calls. 
   
    APAR:    IY77899    16992
    Symptom: If one or more ACIs for same target are defined at an Organization or BU level, 
             with some target filter, only one of the ACIs will evaluate and the other ACIs 
             will be completely ignored.
   
    APAR:    IY77901    16993
    Symptom: Documentation for the self_care sample application needs to be added to the 
             examples documentation directory.
   
    APAR:    IY78065    16928
    Symptom: Remote ITIM Applications can not supply a proper LTPA authentication token when 
             WebSphere authentication realms are dissimilar between the remote application 
             server and the ITIM server. 
   
    APAR:    IY78395    16957
    Symptom: Remote ITIM Applications do not recover whenever ITIM is restarted and the web 
             applications must be manually restarted. 
    
    APAR:    IY74391    16688
    Symptom: Cannot use custom profiles after installing.
             Note - After applying this patch follow the steps as given below -
             1. Make sure to copy itim_api.jar, itim_server.jar and api_ejb.jar from:$WAS_HOME/
                installedApps/$MACHINE_NAME/enrole.ear directory, to $ITIM_HOME/lib  directory.
   
    APAR:    IY75058    16781
    Symptom: During an IDI data feed (with ITIM acting as DSMLv2 server) some "modify person" 
             requests hang (and show up in the "pending requests" list).
   
    APAR:    IY76000    16866
    Symptom: The presence of both MANDATORY and EXCLUDED enforcement on the same multivalued 
             attribute (coming from different provisioning policies) reduce the set of allowed 
             values to the MANDATORY ones only.
   
    APAR:    IY76116    16887
    Symptom: If you configure SSL between ITIM and IDS (LDAP), service profiles cannot be imported.
             Note: Please refer Readme.txt in IY76116.zip for more information.
   
    APAR:    IY77445    16838
    Symptom: Cannot run Crystal reports using Non-admin user. 
   
    APAR:    IY77446    16855
    Symptom: When using the IDI DSMLv2 handler to load data into ITIM and placing a person record 
             into a specific OU with over 5,000 sub-OUs, ITIM eventually crashes with "OutOfMemory"
             and "Unable to create thread" errors.
   
    APAR:    IY77447    16902
    Symptom: The "Disallow User Name (case insensitive)" will parse the CN attribute and 
             derive single character from attribute value that it will check in the password. 
   
    APAR:    IY77479    16802
    Symptom: The compliance alert detail screen displays the raw data instead of the resolved 
             display label.
   
    APAR:    IY77480    16794
    Symptom: If the "enforcement" on the original service (referred by the hosted service) is 
             changed to "correct", the accounts on hosted service gets deleted.

   
    APAR:    IY77481    16979
    Symptom: Under some conditions the ITIM server does not update MANDATORY attributes with the 
             new values, instead, it uses the old values.
             Note - Spaces and hyphens are ignored during comparison of attribute values with the
             Telephone Number syntax i.e. with OID as 1.3.6.1.4.1.1466.115.121.1.50.
   
    APAR:    IY77483    16967
    Symptom: The saproleservlet is not able to handle SAP role names containing characters 
             outside the US-ASCII character set (but included in the ISO 8859-1 one, such 
             as accented vowels).
   
    APAR:    IY77484    16968
    Symptom: OBJECT_NOT_FOUND exception during Person transfer with Select Business Unit 
             set to Root Organization.
   
    APAR:    IY77485    16978
    Symptom: ITIM Server logs show password in clear text for Password Synch.
   
    APAR:    IY77486    16980
    Symptom: The examples.api.ChangePassword returns a NullPointerException when attempting to 
             change the password of an orphaned account.
             Note - After applying this patch follow the steps as given below -
             1. Make sure to copy itim_api.jar, itim_server.jar and api_ejb.jar from:$WAS_HOME/
                installedApps/$CELL_NAME/enrole.ear directory, to $ITIM_HOME/lib  directory.
             
             
    APAR:    IY77487    16952
    Symptom: When trying to reset a user password on a config that has a "Password Rule" with 
             Required Characters value set to '(' or ')' or both and Disallow In Dictionary? set to true. An 
             invalid password exception is thrown.
   
    APAR:    IY77488    16808
    Symptom: New option provided in serviceability.sh tool to suppress information from LDAP.
                 Running "serviceability.sh no" will prevent the tool from retrieving any 
                 information from the directory server. Thi option applies to both the 
                 serviceability.sh and serviceability.cmd scripts.
    
    APAR:    IY77491    16924
    Symptom: Correct problems with the Adapter interface.
   
    APAR:    IY77169    16983
    Symptom: New Function: Bi-Directional Language Enablement. 
   
    APAR:    IY74180    16658
    Symptom: LDAP error code 32 during AD adapter 4.6 reconciliation. 
   
    APAR:    IY74325    16682
    Symptom: Need to be able to delete/remove service profiles that were imported and are no 
             longer needed.
             Note - After applying this patch follow the steps as given below -
             1. Copy itim_api.jar, itim_server.jar and api_ejb.jar from:
                $WAS_HOME/installedApps/$MACHINE_NAME/enrole.ear directory, to
                $ITIM_HOME/lib  directory.

             2. For operating system other than windows -
                Edit remove_service_profiles.sh in $ITIM_HOME/bin/unix directory, to
                include path of database driver in classpath.
                Example - If you are using DB2 as the database, add the following line -
                          CLASSPATH=$CLASSPATH:<Path of db2java.zip>

             3. For windows operating system -
                Edit remove_service_profiles.cmd in %ITIM_HOME%/bin/win directory, to
                include path of database driver in classpath. 
                Example - If you are using DB2 as the database, add the following line -
                          set CLASSPATH=%CLASSPATH%;<Path of db2java.zip>

             4. In a UNIX environment, source the DB2 environment before executing 
                remove_service_profiles.sh.
                E.G. . /home/db2inst1/sqllib/db2profile 
   
    APAR:    IY74455    16699
    Symptom: Valid ldap filters throw "invalid filter" errors in ITIM UI.
   
    APAR:    IY75100    16773
    Symptom: WAS Security enablement instructions in ITIM Installation Guide page 41 should 
             contain a reference to:
             'Creating J2C authentication data entries' action requirements.
             The ITIM Installation Guide will be updated to add an entry after the line:
             3. Configure the local OS user registry with these steps.
             The following will be added:
             4. Update J2C Authentication Data for alias itim_jms with a valid User Id and 
             password (see Appendix D - Creating J2C authentication data entries).
   
    APAR:    IY75576    16832
    Symptom: Incorrect workaround in ITIM 4.6 Release notes for LDAP version 3 filter example.
             The ITIM 4.6 Release notes page 36 shows the workaround using the same incorrect
             V3 search Filter.  The ITIM 4.6 Release notes page 36 will be corrected to show:
             
                ====================================================================      
                Problem: Using LDAP Version 3 filters causes inconsistent results 
                from an adapter, or may not be accepted by the adapter as input. 
                Using more than two operands for '&' and '|' operators in a 
                reconciliation filter might cause an error, unless they are modified 
                to have no more than two operands. For example, the following filter 
                causes a FilterException error:                                           
                                                                          
                (&(eruid=a*)(ersql2000defdatabase=i*)(ersql2000deflanguage-E*))           
                                                                          
                Workaround: Use filters such that '&' and '|' operators have no 
                more than two operands.     
                For example, the above filter can be modified as follows to get 
                the same results:
                (&(&(eruid=a*)(ersql2000defdatabase=i*))(ersql2000deflanguage-E*))  
                ====================================================================
   
    APAR:    IY75653    16548
    Symptom: Transaction timeouts during Report generation.
   
    APAR:    IY75654    16687
    Symptom: Get "java.lang.OutOfMemoryError" failure during large multi account password change. 
   
    APAR:    IY75655    16701
    Symptom: Account creation email notification should also be sent on success with warnings, 
             not just 100% success.

             Note - To resolve this issue, a new ITIM extension 'notifyNewAccount' has been 
             introduced. This extension takes owner, service and account entities as input 
             parameters and notifies the owner, with information related to the new account.
             This extension may be used when account creation is to be notified to the owner 
             even when the operation completes with warnings.

             Note that if property "enrole.workflow.notifynewaccount" is set to 'false' in
             enRole.properties, this extension will not send notification email to the owner.

             You will have to register this extension with ITIM as follows -
             1. Open workflowextensions.xml located in $ITIM_HOME\data directory using a 
                suitable text editor.
             2. Add the following entry in the file, before the closing </WORKFLOWEXTENSIONS>
                tag in the file:-
                 <ACTIVITY ACTIVITYID="notifyNewAccount" LIMIT="600000">
                 <IMPLEMENTATION_TYPE>
                   <APPLICATION CLASS_NAME="com.ibm.itim.workflowextensions.AccountExtensions" METHOD_NAME="notifyNewAccount"/>
                 </IMPLEMENTATION_TYPE>
                 <PARAMETERS>
                  <IN_PARAMETERS PARAM_ID="owner" TYPE="Person"/>
                  <IN_PARAMETERS PARAM_ID="service" TYPE="Service"/>
                  <IN_PARAMETERS PARAM_ID="account" TYPE="Account"/>
                 </PARAMETERS>
                 <TRANSITION_RESTRICTION JOIN="XOR"/>
                 <SCRIPT EVENT="onComplete"><![CDATA[
                  WorkflowRuntimeContext.setProcessResult(WorkflowRuntimeContext.getActivityResult());
                  WorkflowRuntimeContext.setProcessResultDetail(WorkflowRuntimeContext.getActivityResultDetail());
                  ]]></SCRIPT>
                 </ACTIVITY>
             3. Save the file.

             ITIM will have to be restarted for the changes in this file, to get reflected.
             Please refer IY75655.pdf for more details.
   
    APAR:    IY75656    16702
    Symptom: Attribute selection in a search popup has a fixed width for the attribute labels.
             These need to have a variable width.
             Note - The fix has been provided for the default english language pack.

             Before applying this patch,take a backup of folder named <language code>
             located in directory : $WAS_HOME/installedApps/$MACHINE_NAME/enrole.ear/app_web.war.
             The <language code> is generally two letter word representing the language. 
             For example for English, the language code is 'en'.

             After applying the patch, restore the folder back to the same directory and
             perform the following steps - 
             1. Locate Styles.css in directory :-
                $WAS_HOME/installedApps/$MACHINE_NAME/enrole.ear/app_web.war/<language code>
             2. Open Styles.css using a suitable text editor.
             3. Locate string "narrowPicklist" in this file.
             4. Change width attribute of this class to "auto" as follows -
                .narrowPicklist {
                   width: auto;
                }
             5. Save the file.
   
    APAR:    IY75658    16799
    Symptom: README DOC update.
             Account modification throws Authorization Exception even when 'write' permission is 
             granted to the ITIM user for the attributes that were actually modified.

             Solution:
             1. Navigate to User Interface Customization, through ITIM.
             2. Open the corresponding Account form template.
             3. For all attributes in the Account form defined of the type 'DropDown Box' or 
                'ListBox' control with custom values, check the option 'Use Blank Row', to 
                allow these attributes to have an empty value.
             4. Next, for all attributes in the Account form defined as a 'CheckBox' control, 
                change the form control to a 'DropDown Box' control with two custom values set 
                to "TRUE" and "FALSE" (Values should be in upper case) and also check the 
                option 'Use Blank Row', to allow these attributes to have an empty value.
             5. Save the form template and exit the form designer.

             Note - This workaround is applicable in case the Account form has some attributes 
             which are defined to have a default value in the form template, (For example dropdown 
             box controls with custom values, with 'Use Blank Row' unchecked) but are not present 
             in LDAP because the remote agent was unable to set a value of this attribute, during 
             account provisioning or modification, due to some reason. 
   
    APAR:    IY75659    16721
    Symptom: ITDI location field should be displayed as mandatory ( * ) 
   
    APAR:    IY75660    16751
    Symptom: Bulk loading ( ~ 60000) of POSIX Solaris Accounts gives error in ibmdi.log of 
             "ALNotFoundExceptioncom"
   
    APAR:    IY75661    16810
    Symptom: Get error 500 on UI when doing a manual provision a person on a Win Local Account with 
             User and Guests for local attr -- forcing a compliant alert screen on Guests value.
   
    APAR:    IY75731    16835
    Symptom: The examples file:
             $ITIM_HOME\extensions\examples\idi_integration\LDAPAccountManagement\AccountManagement.html
             is not accurate for UNIX systems.  
             Need to ensure people executing config_remote_servcies to first source the 
             DB2 environment in a UNIX environment.
             E.G. . /home/db2inst1/sqllib/db2profile 
   
    APAR:    IY75965    16820
    Symptom: Clicking the Submit button on "View|Modify Entitlement Detail" a second time during 
             processing results in "out of memory" error. 
   
    APAR:    IY73980    16641
    Symptom: Entering a double quote in Java script  for Entitlement causes standard view to 
             fail with 'JS Error'.
   
    APAR:    IY74422    16049
    Symptom: Identity Policy disregards owner when 'CHECK ALL SERVICES' and 'DON'T CHECK RECYCLE 
             BIN Selected.  This is a README Documentation update.  We are providing
             IY74422.zip to show users how to code a Fesiextension to allow this.  IY74422.zip 
             may be unzipped using the same procedure you use to unzip the Interim fix package.  
             See Applying the Patch: described below.
   
    APAR:    IY74428    16567
    Symptom: You may encounter slow performance or transaction timeouts during 
             report generation for certain reports against large data sets.
   
    APAR:    IY74443    16600
    Symptom: BeanNotReentrantException thrown when running on WAS 5.1.1.4 or 5.1.1.5.
   
    APAR:    IY74444    16549
    Symptom: After Search, viewing the adoption rule for a particular service produces 
             Illegal Argument Exception".
   
    APAR:    IY74502    16587
    Symptom: Improved email notification performance.
   
    APAR:    IY74503    16586
    Symptom: Out of Memory while doing a Report Synchronize.
   
    APAR:    IY74504    16653
    Symptom: AccountMO.selfClaim() was incorrectly left in the API javadoc.  It is now 
             removed.
   
    APAR:    IY74512    16044
    Symptom: Error message is not displayed in expected language.
   
    APAR:    IY74515    16224
    Symptom: Windows2000 Group Names not shown correctly in the account form when Filter 
             is removed.
   
    APAR:    IY74517    16496
    Symptom: One attribute fails to get included in the attributes list for RACFacct in the 
             ITIM Search interface: "Installation Data" (erracuinstdata).
             To address this issue, binary attributes are also included in the attributes list
             in the ITIM Search interface. The binary attributes are suffixed by an asterisk 
             mark '*', while displaying them in the attribute list. Only 'Contains' and 
             'Not contains' options are supported for searching with binary attributes.
             The 'Not contains' option for binary attributes is known to degrade search 
             performance and hence is not recommended.
   
    APAR:    IY74519    16497
    Symptom: DN is diaplayed in ListBox instead of 'cn'.
   
    APAR:    IY74525    16501
    Symptom: Users would like to have a way to disable the check box "create password".
    
             Edit the enRole.properties file to set the value you wish.    
             ############################################################# 
             ## Enable/Disable CreatePassword checkbox                     
             ## CreatePassword=true Checkbox will remain enabled           
             ## CreatePassword=false Checkbox will be disabled             
             #############################################################  
             enrole.CreatePassword=true                                     
             The value of true is the default and will allow the use of the 
             checkbox.
   
    APAR:    IY74526    16570
    Symptom: Wrong Attribute Mapping of entities when doing the following:
             1. Go to Configuration->entity->person(Org,BP Org,BP Person)->define mapping                                               
             2. select an attribute from Identity Manager attribute. Do not select any attribute 
             in Custom Ldap Attributes.                
             3. Click on the Map and then Unmap buttons.

   
    APAR:    IY74527    16579
    Symptom: ITIM uses an invalid search filter against a binary attribute, resulting 
             in an LDAP Error 92.
   
    APAR:    IY74528    16584
    Symptom: Read only fields not working properly on a customized person entry form.
   
    APAR:    IY74530    16405
    Symptom: Warning messges are not logged if the value of property policy.message.size, in 
             enrolepolicies.properties is 0 or negative.
   
    APAR:    IY74531    16610
    Symptom: Exception thrown in log when setting value to empty, for an attribute that does 
             not have entry in xforms and resource.def has the flag TRANSFORM_NAMES_AND_VALUES.
   
    APAR:    IY74532    16609
    Symptom: Performance issue with "User interface customization" and a high number of 
             service profiles.
   
    APAR:    IY74533    16631
    Symptom: 'RoleChangeNotAllowed' exception is not thrown if the logged-in ITIM user does not 
             have 'MODIFY' permission on ORG role entry and he tries to remove all roles from 
             a person.
   
    APAR:    IY74534    16643
    Symptom: Hide on Modify attribute becomes visible on 'View Data Screen' navigated from 
             Approve-Reject tab while switching tabs.
   
    APAR:    IY74535    16651
    Symptom: Missing CN attribute results in NullPointerException
   
    APAR:    IY74536    16620
    Symptom: Data feed of people with status set is always get overriden by ITIM 
             with ACTIVE status.
   
    APAR:    IY74537    16634
    Symptom: ITIM does not allow for automatic entitlement of "service type" target.
   
    APAR:    IY74538    16680
    Symptom: Viewing 3000+ orphan accounts on the services fails with CORBA_NO_MEMORY error.
   
    APAR:    IY74539    16665
    Symptom: An attribute label that contains "&" breaks display of ACI attribute permissions 
             page.
   
    APAR:    IY74540    16684
    Symptom: Duplicate accounts in RACF Recon. 
   
    APAR:    IY74542    16679
    Symptom: Data with "&" in single-valued Search Widget in Read-only mode causes xsl error.

Dependencies: ITIM 4.6 (This Fixpack cannot be applied to earlier releases)

Fixes superseded by this Fixpack: 4.6.0-TIV-TIM-FP0001, 4.6.0-TIV-TIM-IF0002, 4.6.0-TIV-TIM-IF0004, 
4.6.0-TIV-TIM-FP0005, and Interim fix 4.6.0-TIV-TIM-IF0007.

Database Changes: NONE

JMS (Java Messaging Service) Changes: NONE

LDAP Changes: NONE
              
OSDB Certification updates, ITIM Server now supports the following Operating systems and middleware:

Solaris 10

Oracle 10g (certified running on Solaris 10)

Red Hat Enterprise 4.0 for Intel

Red Hat Enterprise 4.0 Update 1 Linux AS for PowerPC

SUSE Linux Enterprise Server 8.0 for Intel  
SUSE Linux Enterprise Server 9.0 for Intel
NOTE *** You may need to contact the WebSphere Support Center for installation assistance to 
       install WebSphere AppServer on the SUSE platforms.


Patch Contents:
  - This README file
  - 4.6.0-TIV-TIM-AIX-WAS-FP0008.zip
  - 4.6.0-TIV-TIM-LNX-WAS-FP0008.zip
  - 4.6.0-TIV-TIM-SOL-WAS-FP0008.zip
  - 4.6.0-TIV-TIM-WIN-WAS-FP0008.zip
  - IY74422.zip
  - IY75655.pdf
  - IY76116.zip

MD5 Checksums:      
   
5d8528ca25a64b0372783b838af8f65e  4.6.0-TIV-TIM-AIX-WAS-FP0008.zip
48079bccc21bd531740298455855c395  4.6.0-TIV-TIM-LNX-WAS-FP0008.zip
16282aba679bd5067520e02e7b2a21af  4.6.0-TIV-TIM-SOL-WAS-FP0008.zip
ad8abe4c4eb047ef7784eeddadaeb6c4  4.6.0-TIV-TIM-WIN-WAS-FP0008.zip

5457ea0572eb1728930829efedaabe9e  IY74422.zip
145b949bba08b349c496deba74d1d3d9  IY75655.pdf
2dcef36148fdec40a5236137369b193f  IY76116.zip

0383d9044ed8037c8dacf28029e2f902  instaix_was_ITIM_5751.bin 
1d68e559a2b6fc776c25a79623711e10  instlinux_was_ITIM_5751.bin
36853cc07a4a606172c08ec41720f126  instsolaris_was_ITIM_5751.bin
3a96e7d4079e559798b7cd0e95dc7db9  instwin_was_ITIM_5751.exe

 
Applying the Patch:  

NOTE: *************************************************************************       
    Please backup any configuration files you modified after installation such as xml or 
    properties files.  It is recommended that you save all files in the $ITIM_HOME/data 
    directory if you have made modifications/customizations.  These files may be replaced 
    during the UPGRADE process.
NOTE: *************************************************************************       
    IF YOU ARE USING JAVA 2 SECURITY:
    Backup up your was.policy file to a temporary holding directory.  During 
    the fix application you will be re-deploying enrole.ear, which removes the
    $WAS_HOME/AppServer/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
    directory and its contents. During the deployment, the was.policy is not 
    replaced and will need to be copied back during the COMMON TASKS section 
    of this document.  On a Cluster this needs to be done on the NDM as well.
    $WAS_HOME/DeploymentManager/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
NOTE: *************************************************************************       
    IF YOU HAVE INSTALLED A CUSTOM LOGO:
    The logo is copied to:
    $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war/images
    The Fixpack Install/Upgrade removes the enRole.ear and all subdirectories.  To make it
    easier to restore the custom logo, copy it to a backup directory of your choosing to 
    facilitate copying it back at the proper time.
    The ui.properties is preserved during a Fixpack install so this will not need to be updated
    again.  There are 2 choices to restoring the custom logo file.
    1. During the Fixpack Install/Upgrade, a utility called runConfig will execute and present 
       a small panel with several items that you may modify, including the custom logo.  This 
       panel has a TAB called UI and you can select this and see that your custom logo name
       should be present.  At this time, you may copy the custom logo from the backup 
       directory where you saved it to:
       $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war/images
       Then continue with the Install/Upgrade by selecting the OK button.
    2. If you wish, you may wait until the Install/Upgrade completes and then copy the
       custom logo to:
       $WAS_HOME/installedApps/<machine_name>/enRole.ear/app_web.war/images
       You may then manually execute runConfig from $ITIM_HOME/bin .  Select the UI tab to 
       verify the custom logo name and then select the OK button.
NOTE: *************************************************************************       
    IF YOU HAVE INSTALLED A LANGUAGE PACK:
    1. The FPxx number shown will not be updated to the current FPxx number
    due to current limitations in the build and install process.  Please 
    check the Build number for verification of an upgrade to the fixpack.
    The build number is the suffix number of the install binary 
    eg. instaix_was_ITIM_519n.bin
    The 519n is the build number and will be seen in many ITIM UI panels.
    2. Symptom - Fixpacks partially overwrite Language Pack installation.
       Note - Before Fixpack installation, take a back-up of the following
       files/folder related to the language pack, located in the directory:
              $WAS_HOME\installedApps\$MACHINE_NAME\enRole.ear\app_web.war
                - AppletErrorMessages_<language code>.properties
                - AppletLabels_<language code>.properties
                - AppletMessages_<language code>.properties
                - The folder along with it's contents by the name as <language code>.
                        
    The <language code> is generally a two letter word representing the language. 
    For example for English, the language code is 'en'.
        
    After Fixpack installation, restore all the language pack related files and folder, 
    that were backed up, to their respective locations in the directory: 
    $WAS_HOME\installedApps\$MACHINE_NAME\enRole.ear\app_web.war
        
    Note that for WAS Cluster installation, the same steps will have to be followed on 
    each of the nodes. This procedure is needed only on the cluster member, not on the 
    Deployment Manager node.
NOTE: *************************************************************************       
        End of notes.
        
    1) Copy the appropriate Platform Fixpack zip file to a temporary staging directory
       and use the following command as an example to unzip it.
    
        For any version
          # jar xvf 4.5.1-TIV-TIM-nnnn-aaa-FP0008.zip  (where nnnn is the platform code and
                                                  aaa is the AppServer type (WAS or WL)

       NOTE:  You may also use any unzip equivalent to unpack the zip file.
              Back-level versions of jar or FastJar as well as some versions
              of Pkzip may report errors. Use the jar executable at version 1.3.1 
              or another zip utility to uncompress the file.
       
    2) Upgrade Installations
    For Single Server deployments, you do not need to stop the WebSphere AppServer.
    For Cluster deployments, ensure the cluster is completely up and functional.
    Run the appropriate binary from the staging location.
    For example:
         instwin_ITIM_5185.exe 
    When prompted, select the UPGRADE option and follow the directions on the panels.
    
NOTE ***    
              
    5) Initial Installations
    Initial installation using this package can only be performed on WebSphere platforms. 
    If you are planning on doing new installations on WebSphere using this package, then 
    you may wish to review the Installation Guide.  This Fixpack provides Installation 
    support for IBM WebSphere.  However, ITIM will NOT install the IBM WebSphere product 
    with this Fixpack.  
    
NOTE ***  
    If you stop the INSTALL/UPGRADE process and then restart it, Default config data 
    is inserted.
    If the fix pack installation is aborted before system configuration (runConfig) is complete, 
    your system property settings are restored to default values - your pre-fix-pack-installation 
    settings are lost - when you run the fix pack installer again.  This is usually ONLY a concern
    when you are doing an UPGRADE.  To correct the system property settings, restore the 
    <ITIM_HOME>/data directory with the pre-fix-pack-installation backup (per above instructions)
    before you run the Fixpack installer again.
    
NOTE ***  
    Additional NOTE:
    If you are using the JAVA 2 Security, replace the was.policy file you saved
    earlier.  Copy it back to:
    $WAS_HOME/AppServer/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
    For Cluster in the NDM:
    $WAS_HOME/DeploymentManager/config/cells/$CELL_NAME/applications/enRole.ear/deployments/enRole/META-INF
    Where $CELL_NAME is either the $MACHINE_NAME or $CLUSTER_NAME.
    For additional information on using JAVA 2 Security with ITIM, please review the ITIM
    Installation Guide, Appendix C.
    
NOTE ***  
End of Server Upgrade instructions.

ERMA Library instructions:

No additional steps are need for Windows systems.  However, you may wish to review the log file:
    <ITIM_HOME>\install_logs\itim_installer_debug.txt 
    To make sure the files were copied, without errors, from:
    <ITIM_HOME>\lib\nt to 
    <SYSTEM_ROOT>\system32\ 
        
For AIX & Solaris refer to the 	AIX & SOLARIS DEPLOYMENT INSTRUCTIONS below.

    Verify that the itim.sh startup script PROTOCOL_DIR environment variable is set to 
    <ITIM_HOME>/lib/<platform>.  
    Add this environment variable if not present. (See the Sample example below)
    
Sample LD_LIBRARY_PATH and PROTOCOL_DIR settings

    The following is a display of a portion of the itim.sh startup script on Solaris
    opened in the editor. (vi $ITIM_HOME/itim.sh)  This is an example of how to set the
    LD_LIBRARY_PATH and PROTOCOL_DIR paths.

    <...SEVERAL lines omitted...>
    SunOS)

    if [ -n "${LD_LIBRARY_PATH}" ]; then
        LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${WL_HOME}/server/lib/solaris:${WL_HOME}/server/lib/solaris/oci817_8"         
    else
        LD_LIBRARY_PATH="${WL_HOME}/server/lib/solaris:${WL_HOME}/server/lib/solaris/oci817_8"
    fi

    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ITIM_HOME/lib/sun

    if [ -n "$ORACLE_HOME" ]; then
        LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
    fi

    export LD_LIBRARY_PATH
    # echo "LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
    JAVA_VM=-server

    # Required for agent communication
    PROTOCOL_DIR=$ITIM_HOME/lib/sun
    export PROTOCOL_DIR

      <...remainder of script omitted...>      

    AIX and SOLARIS DEPLOYMENT INSTRUCTIONS:
    Please use the following instructions to deploy the ERMA Libraries on all supported 
    AIX and Solaris systems :-
      1. Stop The ITIM Server (See instructions in the ITIM Installation Guide).
      2. Run the createlinks.sh script
      3. Set the shared library environment variable (see note) to specify the path of 
         shared libraries.The environment variable should point to the directory where 
         all the above files exist and it should also include /usr/lib directory.

         e.g. type following command on command line for Solaris:
         export LD_LIBRARY_PATH=<ITIM_HOME>/lib/sun:/usr/lib:$LD_LIBRARY_PATH 
         LD_LIBRARY_PATH is name of the shared library environment variable
         for Solaris and 'sun' is the directory name which contains ERMA 
         libraries for Solaris. 
         See note below, for environment variable names on other operating system, 
         and also the name of the directories containing the ERMA libraries.

      4. Verify that the shared library environment variable value contains all 
         required files by executing the ldd command on both libErmApi.so and 
         libErmJni.so.
              e.g. type following command on command line
              ldd libErmApi.so
              ldd ErmApiFtp.so
              ldd ErmApiDaml.so
              If any files are listed as "not found", add the path to those 
              files in the LD_LIBRARY_PATH.

      5. Once all the shared libraries are in path, update the ITIM Start Script
         to include this new LD_LIBRARY_PATH.
      6. Start the ITIM server (See instructions in the ITIM Installation Guide).

      NOTE: The shared library environment variable on AIX is LIBPATH instead of 
            LD_LIBRARY_PATH.  LD_LIBRARY_PATH is the shared library environment 
            variable name for Solaris and Linux.
            The name of the directory in the folder <ITIM_HOME>/lib, containing
            the ERMA libraries are as follows -
            'aix'    for ITIM installed on AIX , 
            'sun'    for ITIM on Solaris, 
            'linux'  for ITIM on Linux operating system.

    *** NOTE ***
    In a cluster deployment, these steps must be done for each node of the cluster.  

    ERMA Library Files Replaced or Added:

    Replaced files:
     <ITIM_HOME>/lib/libErmApi.so
     <ITIM_HOME>/lib/ErmApiFtp.so
     <ITIM_HOME>/lib/libErmJni.so

    New files:
     <ITIM_HOME>/lib/libicudata26.1.so
     <ITIM_HOME>/lib/libicui18n26.1.so
     <ITIM_HOME>/lib/libicuuc26.1.so
     <ITIM_HOME>/lib/libstdc++.so.2.10.0
     
Instructions for Linux for ERMA library update:

    1. Ensure the Linux FTP libraries are copied to:
    <ITIM_HOME>/lib/linux directory
    
    2. run link commands from createlinks.sh (also located in at L3_itim_451\public\lib\linux) 
    on command line one at a time for all shared library files.
    
    3. Change the permission of ALL these files appropriately, so that the user has execute 
    permissions (e.g. chmod 775 <filename>)

Instructions for runtime (preferably in itim startup script)

    4. set environment variable LD_LIBRARY_PATH to include <ITIM_HOME>/lib/linux folder.
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<ITIM_HOME>/lib/linux

    5. set environment variable PROTOCOL_DIR to <ITIM_HOME>/lib/linux folder.
    export PROTOCOL_DIR=<ITIM_HOME>/lib/linux

    ERMA Library Files Replaced or Added:
     
    New files:
     <ITIM_HOME>/lib/linux/createlinks.sh          
     <ITIM_HOME>/lib/linux/libErmJni.so            
     <ITIM_HOME>/lib/linux/libicuuc.so.26.1        
     <ITIM_HOME>/lib/linux/ErmApiFtp.so            
     <ITIM_HOME>/lib/linux/libgcc_s.so.1           
     <ITIM_HOME>/lib/linux/libstdc++-libc6.2-2.so.3
     <ITIM_HOME>/lib/linux/libicudata.so.26.1      
     <ITIM_HOME>/lib/linux/libstdc++.so.5          
     <ITIM_HOME>/lib/linux/libErmApi.so            
     <ITIM_HOME>/lib/linux/libicui18n.so.26.1 
     
    Here is a sample script to make the ERMA LIBS work for the FTP based agents.
    You may add this to the WebSphere startServer.sh if you wish or use this example
    to start WebSphere, just uncomment the areas needed:
    
    #!/bin/sh

    export LD_LIBRARY_PATH=/home2/itim46/lib/linux:${LD_LIBRARY_PATH}
    export PROTOCOL_DIR=/home2/itim46/lib/linux
    #/opt/WebSphere/AppServer/bin/startServer.sh server1
    #/opt/IBMHttpServer/bin/apachectl start
    
    For WAS Cluster.

    Example:
    Application Servers > server1 > Process Definition

    Then choose Environment Entries from the Additional Properties.  
    Then add LD_LIBRARY_PATH and PROTOCOL_DIR environment entries here with the correct values.
    Then restart the cluster.
    
    End of WAS Cluster info.
    End of Linux ERMA Library Update information.
           
End of ERMA Library instructions.
End of Readme
