Remove a WebSphere Application Server Profile on AIX

WebSphere Application ServerThere may be times when you need to remove a WebSphere deployment manager, node, or application server profile. I have successfully used the following steps in versions 7 and 8 of WebSphere.

  • Stop the deployment managers, nodes, or application servers that are associated with the profile that you want to remove
  • List all profiles on a server:
    [was_install_dir]/bin/manageprofiles.sh –listProfiles
  • Remove a WebSphere Application Server profile:
    [was_install_dir]/bin/manageprofiles.sh –delete –profileName profile
  • Ensure that references to the deleted profile are removed from the profile registry:
    [was_install_dir]/bin/manageprofiles.sh –validateAndUpdateRegistry
  • Delete the profile directory tree (if it was not deleted by the previous action):
    [was_install_dir]/profiles/rm -r profile
Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

Using chpasswd to Set User Passwords in AIX

chpasswdI have had to create a lot of users in AIX environments lately. After users are created, their initial passwords need to be set. The chpasswd command is handy because it can used used for a single password or used in batch. The following description and examples are published at the IBM Knowledge Center:


chpasswd [ -R load_module ] [ -e ] [ -f flags | -c ]


The chpasswd command administers users’ passwords. The root user can supply or change users’ passwords specified through standard input. Each line of input must be of the following format:


Only root users can set passwords with this command.

By default, the chpasswd command sets the ADMCHG flag for the users. The -f option may be used with other valid flags to override the default. The -c option clears all password flags.

The password field can be cleartext or a value encrypted with the crypt algorithm. The -e option indicates that passwords are of encrypted format. Please note that all passwords in a batch must conform to the same format.


-c Clears all password flags
-e Specifies that the passwords are of encrypted format
-f flags  Specifies the comma separated list of password flags to set. Valid flag values are: ADMIN, ADMCHG, and/or NOCHECK
-R load_module  Specifies the loadable I&A module used to change users’ passwords


Only root users should have execute (x) access to this command. The command should have the trusted computing base attribute.


  • To set passwords for users from the command line, type:


Followed by entering username:password pairs, one pair per line. Enter CTRL+D when finished.


  • To set passwords for users contained in a file named mypwdfile, type the following:

cat mypwdfile | chpasswd

Note that mypwdfile must contain username:password pairs; one pair per line. For example:


Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

Disable the Option to Store Credentials in SAS Enterprise Guide Profiles

from SAS® 9.2 Intelligence Platform Desktop Application Administration Guide at support.sas.com:

When you create a connection profile, the Connection Profile Wizard provides, by default, a check box named Save user ID and password in this profile. If a user selects this check box, then the user’s ID and password are stored in the user’s connection profile on the local file system. Saving the ID and password in the profile allows users to reconnect in the future without entering these values again.

Follow these steps to remove the Save user ID and password in this profile check box from the Connection Profile Wizard and require the manual entry of credentials:

  1. On the host of the SAS Metadata Server, open in a text editor the file omaconfig.xml.
  2. Change the value of the option SASSEC_LOCAL_PW_SAVE from 1 (or Y or T) to 0 (or N or F).
  3. Save and close the file.
  4. Restart the SAS Metadata Server as directed in the SAS Intelligence Platform: System Administration Guide.

After you change the setting for this option and restart the metadata server, each client uses the previous setting for its first connection. The client then discovers the revised setting and conforms to that revised setting for subsequent connections.

If you change the setting to disallow saved credentials, and credentials are already present in a user’s connection profile, those credentials must be manually removed.

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

© 2017 Technoleros

Theme by Anders NorénUp ↑