Create databases and users for SQL Server

 

+
Search Tips   |   Advanced Search

 

Before you begin

You should have completed installing SQL Server.

If WebSphere Portal V5.1 and an earlier version of WebSphere Portal coexist, the database user IDs for WebSphere Portal V5.1 must be different than earlier versions to avoid conflicts during installation.

Database names and user information will be required when configuring WebSphere Portal to work with SQL Server.

 

Create databases

Use the SQL Server Enterprise Manager to create the databases.

  1. Expand the nodes to see Databases.

  2. Right-click on Databases to see New database.

  3. For database name, use WPSDB.

    You can store all data in the WebSphere Portal database (WPSDB). However, if you decide to use separate databases, create the following databases as well:

    JCRDB Document Manager and Personalization
    FDBKDB Feedback
    LMDB Likeminds

  4. Set the Collation Name according to your environment, for example on an English system:

    1. Make sure that LMDB is set to a case-insensitive collation by using:

      SQL_Latin1_General_CP1_CI_AS

    2. If you are using WPSDB, JCRDB or FDBKDB, set collation to case-sensitive by using:

      SQL_Latin1_General_CP1_CS_AS

  5. Click OK to save the database changes.

 

Create database users

After creating the databases, create the recommended database users with the SQL Server Enterprise Manager.

  1. Connect to your SQL Server instance.

  2. Expand the tree view beneath the SQL Server instance.

  3. Expand Security and right-click on Logins.

  4. In the opening context menu, select New Login....

  5. Enter the database user name. The following values are variables and should be replaced with the values for your environment. The recommended architecture suggests the following users be created:

    • WPSDBUSR

    • WMMDBUSR

    • ICMADMIN, if a separate database is used for user content data.

    • FEEDBACK, if a separate database is used for Feedback data.

    • LMDBUSR, if a separate database is used for Likeminds data.

    User names must be uppercase. These values must be entered uppercase when configuring WebSphere Portal.

  6. Select SQL Server Authentication.

  7. Set a password for the selected user.

  8. In the "Database Access" pane, select the database the user must connect to at runtime. The following mappings are recommended:

    Database User
    WPSDB WPSDBUSR

    WMMDBUSR

    JCRDB ICMADMIN
    FDBKDB FEEDBACK
    LMDB LMDBUSR
    set the correct default database for WMMDBUSR. For example, if WebSphere Portal and Member Manager share a database, the default database for WMMDBUSR should be set to wpsdb. It is also recommended that the other database users have their defaults set to the correct database.

  9. Be sure that no Server Role is selected.

  10. Set Database Access as follows:

    Database User Database Role
    WPSDB WPSDBUSR

    WMMDBUSR

    		public

    db_owner

    JCRDB ICMADMIN

    		public

    db_owner

    FDBKDB FEEDBACK public

    db_owner

    LMDB LMDBUSR public

    db_owner

  11. Click OK to save the user changes.

 

Set SQL Server properties Authentication

After creating the databases and users, set the SQL Server Enterprise Manager Authentication setting to SqlServer and Windows . This will eliminate the need for run-time authentication of SQL Server requests.

  1. Open the SQL Server Enterprise Manager by selecting Start menu > Programs > Microsoft SQL Server > Enterprise Manager.

  2. Expand the tree control until you can see your server.

  3. Right click on the server name and select Properties. The "SQL Server Properties (Configure)" window will open.

  4. Select the Security tab.

  5. For Authentication, select SQL Server and Windows.

  6. Restart the SQL Server to apply your update.

 

Next steps

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.