Running Profiles administrative commands

Scripts are used to administer the Profiles application. These scripts use the AdminConfig object available in IBM® WebSphere® Application Server wsadmin client to interact with the Profiles server.

Before you begin

To run administrative commands, you must use the wsadmin client. See Starting the wsadmin client for information about how to start the wsadmin command-line tool.

About this task

Note: You cannot use administrative tools to add or remove a profile from your LDAP directory system. You must use that directory's native tools to create and delete profiles.
The scripts used to administer Profiles give an administrator (who otherwise would not have access to edit a user's profile data), the ability to edit various fields in a user's profile. For example, one use of the capability is to remove unwanted or inappropriate content.

Unlike with configuration properties, when you use administrative commands to change server administration properties, you do not have to check out any files nor restart the server. Your changes take effect immediately.

Procedure

To run administrative commands, complete the following steps.
  1. Start the wsadmin client from the following directory of the system on which you installed the Deployment Manager: 
    app_server_root\profiles\dm_profile_root\bin
    where app_server_root is the WebSphere® Application Server installation directory and dm_profile_root is the Deployment Manager profile directory, typically dmgr01.

    You must start the client from this directory or subsequent commands that you enter do not execute correctly. For more information, see Starting the wsadmin client.

  2. Start the Profiles Jython script interpreter.
    1. Use the following command to access the Profiles configuration files:
      execfile("profilesAdmin.py")
      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, you must pick the node where the file is stored.
  3. See Profiles administrative commands for a complete list of administrative commands for the Profiles application.