Portal Configuration Wizard

 

+
Search Tips   |   Advanced Search

 

Overview

The tasks that you can run using the Configuration Wizard include...

  1. Transfer data to a different database
  2. Connect to a database
  3. Enable and disable LDAP security.

If you do not use the configuration wizard, you can perform configuration using WPSconfig.sh.

Before you start the configuration wizard:

  • If you plan to transfer or connect to a different database, that database software must be installed and the appropriate databases and users created before you can use the configuration wizard.

  • If you plan to enable or disable LDAP security, the LDAP software must be installed and configured appropriately before you can use the configuration wizard. For more information, see the section on LDAP.

The configuration wizard will not run properly if the prerequisite for your task has not been met.

 

Starting the wizard

To start the configuration wizard command at a command line.

cd wp_root/config/wizard
./configwizard.sh

To run the wizard in console mode, type -console after the command. For example:

configwizard0s400.bat -console

Launching the program in console mode runs the configuration without the graphical user interface.

 

What to know after you launch the wizard

The initial panel of the configuration wizard provides you with a list of configuration tasks that you can perform. complete one configuration task at a time. To perform more than one task with the configuration wizard, choose a task from the initial panel and complete it; at the end of the task, a panel displays to enable you to return to the initial panel to choose another task.

When you click on the Help button, you may see a message logged to the command line indicating that a Javax function was created. This is an information-only message and can be safely ignored.

When transferring to a database, you may see a message similar to the following logged to configwizardlog.txt. This message can be safely ignored.

Unexpected file error: ServiceException: (error code = 305; message = "setFileAttributes requires native support. "; severity = 0)

When running in a Solaris environment and you click the Browse button, you may see the message logged to the command line indicating that the system could not find an input context. This is an information-only message and can be safely ignored.

 

Steps for this task

  1. Go to the machine on which you installed WebSphere Portal.

  2. Make sure that you are logged in to the system with administrative privileges.

  3. Start WAS.

  4. Stop WebSphere Portal.

  5. Perform the following steps to run the configuration wizard:

    1. Start a command prompt.

    2. cd wp_root/config/wizard

    3. Run...

      ./configwizard.sh

    4. Enter the values that are appropriate for your environment, and click Next to continue.

 

Usage tips

  • Refer to the help panels to view documentation about each field that requires input.

  • For some fields that require input, you might have to enter a value that represents a new entity, such as a new database or new node. For other fields, you might have to enter a value that represents an existing entity, such as a node that already exists or a user ID and password that you have already created. Consult the help panels for additional information.

  • The configuration wizard generates log files each time you run it. The log file for the configuration wizard is located at...

    wp_root/config/wizard/configwizardlog.txt

    A second log file is located at...

    wp_root/log/configwizard.log.

 

Transfer data to a different database

Panel text Description Default values
Database driver class or JDBC provider The Java class name for the JDBC provider that WebSphere Portal uses to communicate with its databases. Cloudscape: com.ibm.db2j.jdbc.DB2jDriver
DB2: COM.ibm.db2.jdbc.app.DB2Driver
Oracle: oracle.jdbc.driver.OracleDriver
SQL Server: com.microsoft.jdbc.sqlserver.SQLServerDriver
Database class name that the SqlProcessor will use to import SQL files via data source The data source for the JDBC provider that WebSphere Portal uses to communicate with its databases. Cloudscape: com.ibm.db2j.jdbc.DB2jConnectionPoolDataSource
DB2: COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource
Oracle: oracle.jdbc.pool.OracleConnectionPoolDataSource
SQL Server: com.microsoft.jdbcx.sqlserver.SQLServerDataSource
Name of the WebSphere Portal database The core portal database which stores configuration information for pages, portlets, users and other portal administrative objects. Instant Messaging buddy list information is also stored in this database. wpsdb
JDBC URL for WebSphere Portal database The database URL used to access the WebSphere Portal database with JDBC. Cloudscape: jdbc:db2j:wpsdb;create=true
DB2: jdbc:db2:wpsdb
Oracle: jdbc:oracle:thin:@hostname:1521:wpsdb
SQL Server: jdbc:microsoft:sqlserver://hostname:1433;DatabaseName=wpsdb
Database user for WebSphere Portal database The user ID for the database administrator.  
Password for WebSphere Portal database The password for the database administrator.  
Node for for WebSphere Portal database The node for the WebSphere Portal database. wpsNode
Name of Member Manager database The name of the Member Manager database.

Tip: For DB2 and DB2 for z/OS and OS/390, this value cannot exceed 8 characters and can only contain letters and numbers. Refer to your database documentation for more information.

WMMDB
JDBC URL for Member Manager database The database URL used to access the Member Manager database with JDBC. Cloudscape: jdbc:db2j:<dbname>;create=true
DB2: jdbc:db2:wmmdb
DB2_iSeries: jdbc:db2:*LOCAL/QWMMDB
DB2_z/OS: jdbc:db2:WMMDB
Oracle: jdbc:oracle:thin:@hostname:1521:wmmdb
SQL Server: jdbc:microsoft:sqlserver://hostname:1433;DatabaseName=wmmdb
Database user for Member Manager database The user ID for the database administrator.  
Password for Member Manager database The password for the database administrator.  
Name of content publishing database The portal content publishing database which stores documents created by the Document Manager, as well as both documents and discussions created by workplace components. JCRDB
JDBC URL for content publishing database    
Database user for content publishing database    
Password for content publishing database    
Name of feedback database The database that stores information logged by Portal for generating reports for analysis of site activity, including information about campaigns and personalized resources. FDBK50
JDBC URL for feedback database    
Database user for feedback database    
Password for feedback database    
Name of workplace database The core workplace database which contains administrative data, mail-system data, Team Collaboration instance data. NAGANO
JDBC URL for workplace database    
Database user for workplace database    
Password for workplace database    

 

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.