IBM Knowledge Center. Configuring IBM Web. Sphere Portal Server v. Oracle Database. This chapter discusses configuring the IBM Websphere portal server v. Oracle database. It contains the following topics: 4. Before You Begin. Before beginning the database configuration, verify that a supported version of Oracle Database software is installed. Refer to the Minimum Technical Requirements for this information. In addition, we strongly recommend you visit the IBM Web. Sphere Portal Version v. Information Center and review the "Configuring Web. Sphere Portal to use a database" section: http: //www- 1. Windows_standalone_Configuring_Web. Collecting troubleshooting data for Security configuration issues with IBM WebSphere Portal 7.0 expedites time to resolution by enabling IBM Support to provide informed problem analysis. Where can I find WebSphere configuration files? up vote 21 down vote favorite. 9. I would like to know where are the WebSphere configuration details saved? In Portal 6.1 does anyone know which files now contain your LDAP config and mappings? First place to learn more about the new Portal 6.1 security configuration would be the InfoCenter. WebSphere Portal V5.1. IBM WebSphere Portal. Select version. IBM WebSphere Portal 7 Product Documentation. Sphere_Portal_to_use_a_database_wp. For advanced configurations, refer to the IBM Web. Installing IBM WebSphere Portal v8.5 on the Primary Node 2. Configuring the Primary Node for a Remote Database 3. wpcollector is a command line tool that automates the collection of portal logs and configuration files.Sphere Portal Version v. Information Center. Working with Properties Files. You must modify the approriate properties files before transferring your data from the default database to the Oracle or Oracle RAC database. Working with properties files: Multiple databases can be used to hold information for applications such as Feedback and Like. Minds. For example, you could use the following property values: release. Db. Name=reldbjcr. Db. Name=jcrdbfeedback. Db. Name=fdbkdblikeminds. Db. Name=lmdbcommunity. Db. Name=commdbcustomization. Db. Name=custdb. If you are using a remote database, enter the values for the remote server. Regardless of the operating system, use a forward slash (/) instead of a backslash (\) in the property files for file system paths. There might be additional database properties other than those listed here. Only change the properties within this task and skip all other properties. The recommended value listed for each property represents the specific information that is required to configure Web. Sphere Portal to your target database. Depending on which database domain has to be configured, replace dbdomain with: releasecustomizationcommunityjcrfeedbacklikeminds. The values for at least one of the following properties must be unique for the release, customization, community, and JCR domains: dbdomain. Db. Namedbdomain. Db. Urldbdomain. Db. Schema. If you use the same values for all three properties across the release, customization, community, and JCR domains, the database- transfer task fails due to ambiguous database object names. If Db. User, Db. Url, and Db. Password are not the same across domains, the value for Data. Source. Name must differ from the Data. Source. Name of the other domains. In other words, this value must be unique for the database domain. When doing a single database, single user, and multi schema database transfer, there can be only one user for each domain (release, community, customization, JCR, Feedback, and Like. Minds), and the schema for each database must be different. The user must be a superuser or DBA and must have authority over all other schemas for the transfer to work. Locate the following files and create a backup copy of each before changing any values: wp_profile_root/Config. Engine/properties/wkplc. Config. Engine/properties/wkplc_dbdomain. Config. Engine/properties/wkplc_dbtype. Default values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Print out the steps below for reference before modifying the properties files. Make sure to enter the appropriate values for each instance of each property. In wkplc_dbdomain. Use a text editor to open the properties file wkplc_dbdomain. For dbdomain. Db. Type, type oracle. For dbdomain. Db. Name, type the name of the Web. Sphere Portal domain database. Note. This value is also the database element in the dbdomain. Db. Url property. For dbdomain. Db. Schema, type the schema name of the database domain. Note. Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that you need to understand. For dbdomain. Data. Source. Name, type the name of the data source that Web. Sphere Portal uses to communicate with its databases. Do not use the following reserved words: release. DScommunity. DScustomization. DSjcr. DSlmdb. DSfeedback. For dbdomain. Db. Url, type the database URL used to access the Web. Sphere Portal database with JDBC. The value must conform to the JDBC URL syntax specified by the database. Note. The database element of this value should match the value of Db. Name. For dbdomain. Db. User, type the user ID for the database configuration user. For dbdomain. Db. Password, type the password for the database configuration user. For dbdomain. Db. Config. Role. Name, type the name of the group for database configuration users. Database rights are granted to this group instead of individuals. The user specified for dbdomain. Db. User must be assigned to this group. Optional: For dbdomain. Db. Runtime. User, type the user ID of the database user that should be used by Web. Sphere Portal to connect to the database at runtime. If no value is specified for this setting, the database configuration user will be used to connect to the databases at runtime. If dbdomain. Db. Runtime. User is specified, you must set dbdomain. Db. Runtime. Password to be the password of the runtime database user. For dbdomain. Db. Runtime. Role. Name, type the name of the group for database runtime users. Database rights are granted to this group instead of individuals. The user specified for dbdomain. Db. Runtime. User must be assigned to this group. Optional: For dbdomain. DBA. Db. User, type the database administrator user ID for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank. Optional: For dbdomain. DBA. Db. Password, type the database administrator password for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank. For dbdomain. Db. Home, type the root location for the database. Note. This value is used to specify the location to create the tablespaces. Save and close the file. Update the following properties in the file wkplc_dbtype. For oracle. Db. Driver, type the name of the Oracle JDBC driver class. For oracle. Db. Library, type the directory and name of the . JDBC driver class. For oracle. Jdbc. Provider. Name, type the name of the JDBC provider that Web. Sphere Portal uses to communicate with its databases. Save and close the file. Update the Was. Password value in the wkplc. This value is the password for the Web. Sphere Application Server security authentication used in your environment. Save and close the file. Creating the Oracle Database for IBM Web. Sphere Portal Server v. Launch Database Configuration Assistant (dbca), click Next: Description of the illustration image. Select create database, click next: Description of the illustration image. Select General Purpose or Transaction Processing, click next: Description of the illustration image. Provide the SID, click next: Description of the illustration image. Select Configure with Enterprise. Manager, click next: Description of the illustration image. Provide account and password details, click next: Description of the illustration image. Configure the storage options, and then click next: Description of the illustration image. Configure file locations, click Next: Description of the illustration image. Configure recovery options, click next: Description of the illustration image. Do Not install sample schemas, click next: Description of the illustration image. Configure UNICODE Character Set: Description of the illustration image. Configure Connection Mode, click next: Description of the illustration image. Configure Security settings, click next: Description of the illustration image. Configure maintenance task, click next: Description of the illustration image. Review storage information, click next: Description of the illustration image. Review information, click finish: Description of the illustration image. Once the installation completes review the installation summary information: Description of the illustration image. From sqlplus command line perform the following select query. SQL> select * from NLS_DATABASE_PARAMETERS. Description of the illustration image. Oracle Database Setup Considerations. Listed below are some important considerations before setting up Oracle databases to work with Web. Sphere Portal. For information about creating databases, refer to the Oracle product documentation. For information on the recommended database architecture and the databases you will need to create, see the Planning for Oracle topic. Be sure that all databases to be used with Web. Sphere Portal are created as UNICODE character set databases. If you are using Oracle 1. Oracle JDBC driver download site, copy it to the Web. Sphere Portal machine, and update the wkplc_dbtype. Db. Library=(the path to the local ojdbc. If you are using Oracle 1. Oracle server to the Web. Sphere Portal machine and update the wkplc_dbtype. Db. Library=(the path to the local ojdbc. The typical location is the oracle_home/sqldeveloper/jdbc/lib directory. Record the copy location on your local machine for future reference. When creating Oracle databases for use with Web. Sphere Portal, you should consider the following information: The Oracle databases must be created manually before configuring Web. Sphere Portal. All databases must be created using UNICODE Database and National character sets such as UTF8, AL3. UTF8, or AL1. 6UTF1. It is recommended that all databases to be used with Web. Sphere Portal are configured in Dedicated Server Mode. Determine if your Oracle server will be remote or local to the Web. Sphere Portal installation. After installing the database software for Web. Sphere Portal, you will need to set the buffer pools allocated to the Oracle database in order for Web. Sphere Portal to communicate with the Java Content Repository database. Use the following recommended values as a guide. Refer to the Oracle product documentation for information on how to set the buffer pools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2016
Categories |