Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Planning for SQL Server 2005

When planning to transfer data to SQL Server 2005, you should consider the databases and user information, such as database names, what data is stored, and the database space needed.

• Review the "Database considerations" topic.
• Ensure the database that you plan to use is supported by this version of WebSphere Portal Express. Refer to Supported hardware and software for the list of supported databases.

The database names and users in this topic are suggested values and provide consistency throughout the documentation. Replace these values with values in your environment.

• The Feedback function is not configured by default. It must first be turned on by following the steps in Enable logging, otherwise the Feedback tables will not be created in the new database.

1. Review the different databases shown in the following table and replace these values with the values in your environment; schema names must be different when the database is shared. While configuring WebSphere Portal Express to use one database is technically possible, using separate databases can improve scalability and performance.

   Application	Database name	Space required
   WebSphere Portal Express Used for the portal (at a minimum) or to hold all data. Stores information about user customization, such as pages, and user profile and login information.	release comm cust	Depends on the number of users and portal objects, such as pages and portlets.
   Document Manager, Personalization,Web Content Management Contains documents, personalization rules, personalization campaigns, and document library configuration information.	jcrdb	Depends on the size and number of documents created and uploaded by the Document Manager , the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Management.
   Feedback Contains the information that is logged by your Web site for analysis of site activity and generating reports.	fdbkdb	Depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
   LikeMinds Contains the recommendations to be displayed to users when their interactions with your Web site have been analyzed and predictions generated.	lmdb	Depends on the amount of traffic to the site.

2. Connect at least one user to the SQL Server 2005 instance. A user can be granted permission to use several schema names, so a single user for each instance is sufficient.
3. Review the tables and types of objects owned by each schema. The WebSphere Portal Express architecture allows each of the following schemata to exist in the same database. All table spaces will be approximately 2.8 GB by default. The size will increase with the use of the Java Content Repository function.

   Application	Database schema placeholder	Recommended name	Function
   WebSphere Portal Express	releaseusr communityusr customizationusr	<none>	Core schemata. Will own approximately 130 tables for each domain. Owns WebSphere Portal Express core objects, which includes tables that store the user customizations made to Pages.
   Java Content Repository	icmadmin	<none>	Java Content Repository schema. Will own at least 1130 tables; the number could be higher depending on usage.
   Feedback	feedback	<none>	Feedback schema. Will own approximately 50 tables used for logging site and personalization usage.
   Likeminds	lmdbusr	<none>	LikeMinds schema. Will own approximately 15 tables used to hold the web site usage analysis routines and recommendation text.