The migrateEAR utility migrates changes made to
console users and groups in the admin-authz.xml and naming-authz.xml files
into the Tivoli® Access Manager object space.
Syntax
migrateEAR -profile_name default
-j fully_qualified_filename
-a Tivoli_Access_Manager_administrator_ID
-p Tivoli_Access_Manager_administrator_password
-w WebSphere_Application_Server_administrator_user_name
-d user_registry_domain_suffix
-c PdPerm.properties_file_location
[-z role_mapping_location]
Attention: - The -j parameter defaults to the file: profile_root/config/cells/cell_name/admin-authz.html
- The -c parameter defaults to: file:profile_root/etc/pd/PdPerm.properties.
The output of the utility is logged in the pdwas_migrate.log file.
The pdwas_migrate.log file is created in the profile_root/logs directory.
- The -profile_name parameter is optional and defaults
to the default profile name.
Parameters
- -aTivoli_Access_Manager_administrator_ID
- The administrative user identifier. The administrative user must
have the privileges required to create users, objects, and access
control lists (ACLs). For example, -a sec_master.
This
parameter is optional. When the parameter is not specified, you are
prompted to supply it at run time.
- -c PdPerm.properties_file_location
- The Uniform Resource Indicator (URI) location of the PdPerm.properties file
that is configured by the pdwascfg utility. When WebSphere Application
Server is installed in the default location, the URI is:
- -d user_registry_domain_suffix
- The domain suffix for the user registry to use. For example, for
Lightweight Directory Access Protocol (LDAP) user registries, this
value is the domain suffix, such as: "o=ibm,c=us"
You can use the pdadmin
user show command to display the distinguished name (DN) for a
user.
- -j fully_qualified_pathname
- The fully qualified path and file name of the Java 2
Platform, Enterprise Edition application archive file ,admin-authz.xml or
the roles definitions file naming-authz.xml that is used
for a naming operation authorization. Optionally, this path can also
be a directory of an expanded enterprise application. For example,
when WebSphere Application Server is installed
in the default location, the path to the data files to migrate includes:
- -p Tivoli_Access_Manager_administrator_password
- The password for the Tivoli Access Manager administrative
user. The administrative user must have the privileges that are required
to create users, objects, and access control lists (ACLs). For example,
you can specify the password for the -a sec_master administrative
user as -p myPassword.
When this parameter is not specified,
the user is prompted to supply the password for the administrative
user name.
- -w WebSphere_Application_Server_administrator_user_name
- The user name that is configured in the WebSphere Application
Server security user registry field as the administrator. This value
matches the account that you created or imported in Creating the security administrative user for Tivoli Access Manager. Access permission
for this user is needed to create or update the Tivoli Access
Manager protected object space.
When the WebSphere Application
Server administrative user does not already exist in the protected
object space, it is created or imported. In this case, a random password
is generated for the user and the account is set to not valid.
Change this password to a known value and set the account to valid.
A
protected object and access control list (ACL) are created. The administrative
user is added to the pdwas-admin group with the following ACL attributes:
- T
- Traverse permission
- i
- Invoke permission
- WebAppServer
- You can overwrite the action group name. The default name is WebAppServer.
This action group name and the matching root object space can be overwritten
when the migration utility is run with the -r option.
- -z role_mapping_location
- The location where the role mapping is to be stored when migrating
administration applications. The default location is to place the
role mapping in the current directory structure, such as:
/WebAppServer/deployedResouces
Specifying
the -z option adds another directory level in which to store the role
mapping. For example, if you specify
-z Roles in
the migrateEAR utility, the role mapping is stored in the directory
structure as follows:
/WebAppServer/deployedResouces/Roles
Avoid trouble: If the -z option is
specified, you must manually update the value of the com.tivoli.pd.as.rbpf.RoleContainerName
property in the amwas.
node_name.amjacc.properties,
and amwas.
node_name.authztable.properties files
such that this value matches the value specified for the -z option.
You do not have to restart WebSphere Application Server
after updating the value of the com.tivoli.pd.as.rbpf.RoleContainerName
property
gotcha
Comments
This utility migrates security
policy information from deployment descriptors or enterprise archive
files to Tivoli Access Manager for WebSphere Application
Server. The script calls com.tivoli.pdwas.migrate.Migrate the Java class.
Before you invoke
the script, you must run the setupCmdLine script from the Qshell
command line. You can find this file in the profile_root/bin directory,
where profile_root is your installation path. In a default
installation, profile_root is app_server_rootND.
The script is dependent on finding the
correct environment variables for the location of prerequisite software.
To enable a new user access to the administrative group
in WebSphere Application Server, it is recommended
that the user be added to the pdwas-admin group after JACC has been
enabled. You can enter the administrative primary ID (adminID) in
the group. This is required when the serverID is not the same as the
adminID.
The following is an example of this command:
pdadmin> group modify pdwas-admin add adminID
Return codes
The utility can return the
following exit status codes:
- 0
- The command completed successfully.
- 1
- The command failed.