Documentation Changes

Read about updates, corrections, and clarifications to the documentation released with Sybase Control Center.

Online help version

The Sybase Control Center help on the web is newer than the version in the product.

New help topics

These are the new topics added to the Sybase Control Center help version on the web:
  • Mapping Sybase Control Center Roles to OS Groups

    To grant Sybase Control Center privileges to users authenticated through the operating system, associate roles used in Sybase Control Center with groups in the operating system.

    Sybase Control Center includes Windows and UNIX authentication modules that you can configure so that users with login accounts in the local operating system can log in to Sybase Control Center. Sybase Control Center roles must be mapped to groups in the operating system or in the login module. By default, Sybase Control Center maps the 'sybase' group to Sybase Control Center roles to provide basic privileges.

    Login module OS group Sybase Control Center roles
    UNIX Proxy root uaAnonymous, uaAgentAdmin, uaOSAdmin
    sybase uaAnonymous, uaPluginAdmin, sccUserRole
    user uaAnonymous, uaUser
    guest uaAnonymous, uaGuest
    NT Proxy Administrators uaAnonymous, uaAgentAdmin, uaOSAdmin
    sybase uaAnonymous, uaPluginAdmin, sccUserRole
    Users uaAnonymous, uaUser
    Guests uaAnonymous, uaGuest
    There are two ways to accomplish the mapping:
    • (Recommended) Add a sybase group to the operating system Sybase Control Center is using to authenticate users, and add all users who need to access Sybase Control Center to the sybase group.
    • Configure Sybase Control Center to use an existing group in the operating system by editing the roles-map.xml file. This option is described here.

    1. If Sybase Control Center is running, shut it down.
    2. In a text editor, open this file:

      Windows: %SYBASE_UA%\conf\roles-map.xml

      UNIX: $SYBASE_UA/conf/roles-map.xml

    3. Locate the appropriate login module (Unix or NT (for Windows)).
    4. Copy the line that maps the sybase group and paste it into the module just above the original sybase line.
    5. Change "sybase" to the name of the group in your operating system to which Sybase Control Center users belong.

      For example, if the group is SCCusers, the new line should look like this:

      <role-mapping modRole="SCCusers" uafRole="uaAnonymous,uaPluginAdmin,sccUserRole" />

    6. Save the file and exit.
    7. Start Sybase Control Center.
  • Starting and Stopping Sybase Control Center in Windows and Starting and Stopping Sybase Control Center in UNIX

    These two topics are added under Get Started | Launching Sybase Control Center section.

Updated help topics

These are the topics that have been updated in the Sybase Control Center help version on the web:
  • About Sybase Control Center

    This is the new short description:

    "Sybase Control Center is a server application that uses a Web-browser-based client to deliver an integrated solution for monitoring and managing Sybase products."

    The number of supported users logged in at the same time has changed to four from eight.

  • Configuring Security Providers

    This is the new information for this topic:

    "Configure Sybase Control Center security providers to authenticate user logins through the operating system."

  • Configuring an NT Proxy Loging Authentication for Windows

    The topic title has changed to "Configuring Authentication for Windows" and has this additional information:

    4. (Optional) If you want Sybase Control Center to import user account information when a Windows or UNIX user logs in to Sybase Control Center, execute these steps. If you choose not to import account information, you must enter it manually. Sybase Control Center requires account information for purposes of setting authorization (privileges) for user accounts.
    1. Log in to Sybase Control Center using an account with administrative privileges.
    2. Select Application > Administration > Security .
    3. Check the box labeled Automatically add SCC login records for authenticated logins.
    4. Click OK to close the Security dialog.

    Postrequisite:

    There are two next steps:
    • If you opted not to automatically import login account information from the operating system, follow the steps in Adding a Login to the System to enter each account into Sybase Control Center manually.
    • Whether you add accounts automatically or manually, you must also grant privileges to the login accounts. You can grant privileges by assigning Sybase Control Center roles directly to the login accounts, or by assigning the login accounts to groups and mapping Sybase Control Center roles to the groups. The group approach is generally more efficient.
  • Configuring a Pluggable Authentication Module (PAM) for UNIX

    This is the updated information:

    Set up the security provider to support username and password login using accounts on the UNIX operating system. Optionally, have Sybase Control Center create an account when a UNIX user logs in to Sybase Control Center.
    1. Using a login account with root privileges, configure the pluggable authentication module for your platform:
      Platform Action
      Solaris Append the contents of the $SYBASE_UA/utility/sunos/pam.conf file, provided with Sybase Control Center, to the /etc/pam.conf file on your Solaris platform.
      Linux Copy the $SYBASE_UA/utility/linux/sybase-ua file, provided with Sybase Control Center, to the /etc/pam.d directory on your Linux platform.
      HP-UX Append the contents of the $SYBASE_UA/utility/hpux/ pam.conf file, provided with Sybase Control Center, to the /etc/pam.conf file on your HP-UX platform.
      Note: In the table above, the portion of the path that indicates the operating system might differ slightly from what is shown.
    2. (Skip if you configured a PAM before starting Sybase Control Center) Reboot Sybase Control Center.
    3. (Optional) If you want Sybase Control Center to create an account when a UNIX user logs in to Sybase Control Center, execute these steps. If you choose not to create Sybase Control Center accounts automatically, you must enter them manually. Sybase Control Center needs the accounts for purposes of setting authorization (user privileges).
      1. Log in to Sybase Control Center using an account with administrative privileges (sccAdminRole).
      2. Select Application > Administration > Security.
      3. Check the box labeled Automatically add SCC login records for authenticated logins.
      4. Click OK to close the Security dialog.

    Postrequisite:

    There are two next steps:
    • If you opted not to automatically create Sybase Control Center login accounts, follow the steps in Adding a Login to the System to enter each account into Sybase Control Center manually.
    • Whether you add accounts automatically or manually, you must also grant privileges to the login accounts. You can grant privileges by assigning Sybase Control Center roles directly to the login accounts, or by assigning the login accounts to groups and mapping Sybase Control Center roles to the groups. The group approach is generally more efficient.
  • Adding a Login to the System
    Another prerequisite and a postrequisite information are added:
    1. Prerequisite:
      • If you intend to use Windows or UNIX to authenticate users, configure the appropriate authentication module.
    2. Postrequisite:

      Grant privileges to the new login account. You can grant privileges by assigning Sybase Control Center roles directly to the login accounts, or by assigning the login accounts to groups and mapping Sybase Control Center roles to the groups. The group approach is generally more efficient.

  • Assigning a Role to a Login
    The topic title has changed to "Assigning a Role to a Login or a Group" and the steps are updated:
    1. From the menu bar, select Application > Administration .
    2. In the Sybase Control Center Properties dialog, expand the Security folder.
    3. Click Logins or Groups.
    4. In the table, select the login account or group to which you want to assign a role.
    5. Click the Roles tab.
    6. In the Available roles for resource list, select the role, then click Add. For example, to grant administrative privileges, add the SCC Service:sccAdminRole. To grant monitoring privileges, add the MonitorRole for the desired server and server type.

      If a role appears in the Has following roles list, this account or group has already been configured with that role.

    7. Click OK.
  • Removing a Role from a Login
    The topic title has changed to "Removing a Role from a Login or a Group" and the steps are updated:
    1. From the menu bar, select Application > Administration .
    2. In the Sybase Control Center Properties dialog, expand the Security folder.
    3. Click Logins or Groups.
    4. Select the login account or group from which you want to remove a role.
    5. Click the Roles tab.
    6. Select the role, then click Remove.
    7. Click OK.

Alert help topics

The alert topics in the Sybase Control Center help need additional information.
  • Creating an Alert Instance from an Alert Template
    1. Add this prerequisite info:

      Prerequisites: Verify that you have the sccAdminRole to perform this task.

    2. Include the other option to create an alert:

      From the resource context menu, select Properties > Alerts, then click Add.

    3. Insert a note after step 2 "Select the alert type template and click Next":
      Note: The list of alert type is unique to the type of the resource.
    4. Add more information and example in step 5 about "Storm Suppression".
    5. Add this information at the end of the steps:

      "When an alert is created, it automatically goes to the Java Message Service (JMS) queue. If the e-mail server has not been specified in Sybase Control Center or you have not specified an e-mail address in your profile, the e-mail options is disabled."

  • Deleting an Alert Instance

    Add this prerequisite info:

    Prerequisites: Verify that you have the sccAdminRole to perform this task.

  • Modifying an Alert Instance

    Add this prerequisite info:

    Prerequisites: Verify that you have the sccAdminRole to perform this task.

  • Subscribing to an Alert
    Add this note at the end of the steps:
    Note: Two subscriptions for the same alert that have the same email address are considered to be one subscription, even if different users created them.
  • Viewing an Alert Instance
    1. Add information about the available tabs at the end of the steps: Threshold, Subscriptions, History.
    2. Include a note:
      Note: JMS subscriptions are not displayed in the list of subscriptions.
  • Displaying Alert Notifications
    1. Add step 2:

      2. (Optional) To delete an alert from the table, select an alert, and click Remove .

    2. Add this information at the end of the step:

      "The Alert Monitor view appears, displaying the alerts created for all managed resources.

  • Displaying Alert History
    1. Add this information at the end of the steps:

      "The History tab displays the alerts that have been created"

    2. Add a new topic "Responding to an Alert":

      From the History tab of the resource Properties > Alerts window, select an alert and click Resolve.

  • Alert Subscriptions

    Add this information:

    "Java Message Service (JMS) and e-mail are the types of alert subscriptions that Sybase Control Center supports. JMS is where a notification is sent to a JMS topic for future processing, and an e-mail is sent to a group indicating that an event has occured. When an alert instance is created, a JMS subscription is created."

Created April 16, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com