Editing Service Accounts

  1. If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
  2. Locate the service account, as described in Locating Service Accounts.
  3. Click the service account name. The View Service Account Details page displays the information shown in Table 14-3.
  4. Table 14-3 Service Account Details  
    Property
    Description
    Last Modified By
    The user who created this service account or imported it into the configuration.
    Last Modified On
    The date and time that the user created this service account or imported it into the configuration. Click the date and time link to view the change history of this resource. See View Change History page.
    References
    The number of objects that this service account references. If such references exist, click the numeric link to view a list of the objects. See Viewing References to Resources.
    Referenced by
    The number of objects that reference this service account. If such references exist, click the numeric link to view a list of the objects. For example, if you selected this service account as the JMS service account in a proxy service with a JMS transport protocol, the proxy service is listed as a reference when you click the link. See Viewing References to Resources.
    Description
    A description of this service account, if one exists.

  5. To make a change to the fields, click Edit. See Adding Service Accounts for descriptions of the fields.
  6. You cannot change the Resource Name field.

  7. Click Save to commit the updates in the current session.
  8. To end the session and deploy the configuration to the run time, click Activate under Change Center.
Note: If the service account that you modified is used to authenticate with a WebLogic JMS server, the JMS server might not recognize your modification for up to 60 seconds. By default, WebLogic Server JMS checks permissions for each destination every 60 seconds. To change this behavior, modify the WebLogic Server startup command so that it sets the following system property to the frequency (in seconds) that you want WebLogic Server JMS to check permissions: weblogic.jms.securityCheckInterval
A value of 0 (zero) for this property ensures that a permissions check is performed for every send, receive, and getEnumeration action on a JMS resource.

Related Topics

See Ensuring the Security of Your Production Environment in Securing a Production Environment, which is available at the following URL: http://e-docs.bea.com/wls/docs92/lockdown/practices.html