IBM WebSphere V5.0 Security - CGISecurity

– pdacld_port: the port number of the Access Manager authorizationserver can be specified if it has been configured as different from thestandard port. Note that pdmgrd_port must also be specified if this optionis used.– rspfile is the fully qualified name of the response file to use during silentinstallation. This is an optional option.For more information about the parameters and using the PDWAScfg utility,refer to the original product documentation.12.6.2 Migration of applicationsIn order for the Access Manager module to perform the authorization functionsfor J2EE applications deployment descriptors, security information needs to bemigrated into Access Manager’s object space. The migrateear.jar tool shipswith Access Manager functions as did the PDWAScfg tool - a standalone Javaapplication using Access Manager Java Admin APIs. It creates a tree of roles (asshown in Figure 12-25 on page 433) and ACLs of users and groups and mapsthe invoke permission from the WebAppServer object to these ACLs.Important:Because Tivoli Access Manager V3.9 is not fully prepared to work withWebSphere Application Server V5, there are some additional steps andtweaking required to make it work.The version of xerces.jar shipped with WebSphere Application Server Version4 was copied to the %PDWAS_HOME%\lib directory.The application_1_2.dtd and application_1_3.dtd were copied from%WAS5_HOME%\deploytool\itp\plugins\com.ibm.etools.j2ee\dtds to the%PDWAS_HOME%\etc directory.1. Start the pdadmin administration application.2. Log on to pdadmin as sec_master and create an Access Manager action andaction group as follows.action group create WebAppServeraction create i invoke “Invoke WebAppServer”3. Then exit from pdadmin but remain in the Windows command prompt andchange the directory to %PDWAS_HOME%/bin.Note: When performing the following step, WebSphere Application Servershould not be running.436 IBM WebSphere V5.0 Security Handbook