|When you configure Oracle for Mashup Center, you must configure it for both MashupHub and Lotus® Mashups. This topic covers only the configuration steps for Lotus Mashups in a Windows® environment.
When you configure Oracle for Mashup Center, you must configure it for both MashupHub and Lotus® Mashups. This topic covers only the configuration steps for Lotus Mashups in a Windows® environment.
Before you begin
Before starting to configure Oracle for Lotus Mashups, you must first install Mashup Center and the Oracle database server. For instructions on installing Mashup Center, see Installing IBM Mashup Center
. For instructions on installing the Oracle database server, see the Oracle 11g documentation
Note: To configure Oracle for MashupHub, see Migrating the catalog database
Note: Before configuring the database, download
the ojdbc6.jar file (JDBC Driver Version 220.127.116.11.0 or above) from Oracle. You may also use the JAR file that is located in the Oracle database installation path at .../product/11.1/jdbc/lib.
- Create a new database with the following settings:
- Provide a database name, for example MASHUPS.
- Set the password for the SYSTEM account.
- Specify AL32UTF8 for the character sets.
- Leave the default values for the other settings.
- Stop the Lotus Mashups server.
- Do the following steps to configure Lotus Mashups:
- Open MashupCenter_install_root/Config/database_oracle.properties, and specify the connectivity information for the database and user, for example:
# Oracle database user ID and password. Note that the user ID is the same as the
schema ID in Oracle. The default user ID is Mashups. If you want to change
the default schema, change the user ID here. An example might be LMDBHA.
# Oracle connection details
# Oracle database details. The database name should match the name
that you provided in the first step above.
- If the MashupCenter_install_root/Config/lib/oracle directory does not contain ojdbc6.jar, copy it over from the Oracle installation folder.
- Create the data source and configure Lotus Mashups to use RDBMS persistence by changing to the MashupCenter_install_root/Config folder and running the following task: config.bat action-create-db-mashup-oracle. After you run the task, five SQL scripts are created in the following directory: MashupCenter_install_root/mm_profile/dbscripts/LotusMashups/li1w500Node02_server1/Oracle/MASHUPS. In addition, a new data source is created in IBM® WebSphere Application Server. If you change the schema, change the user ID with the new schema to authenticate with the data source.
- Do the following steps to create the Lotus Mashups Oracle user and the tables:
- Open the Oracle SQL Plus tool, and log on with the SYS account.
- Connect as SYSDBA by running the connect as SYSDBA command and entering the SYS account.
- If you are configuring Oracle in a High Availability environment, open the createTablespace.sql script, locate the MASHUPSREGTABSPACE property, and add a path to the shared directory that is accessed by both database instances. If no path is specified, the table space will only be created locally and will not point to the shared directory. No action is required if you are running a stand-alone Oracle database server.
- Run the following SQL scripts from the SQL Plus command window. Note that the command format to run SQL scripts is @/script.sql, where is the path of the script and script.sql is the name of the script file. In Lotus Mashups, the is MashupCenter_install_root/mm_profile/dbscriptLotusMashups/oracle/database_name.
Note: If you change the schema, modify the following SQL script files to use the new schema before running the scripts.
- To create the table spaces, run SQL> @/createTablespace.sql.
- To create the Oracle schema, run SQL> @/createSchema.sql
- To create tables, run SQL> @/createTable.sql.
- To grant access to the user, run SQL> @/createGrant.sql.
- Start the Lotus Mashups server.
- Do the following steps to test the connection and make sure everything is working as expected:
Parent topic: Configuring data persistence: imc3
- Open the WebSphere Application Server administrative console, and click Resources > JDBC > Data sources.
- Confirm that the login name for the data source is the same as the schema name. If you change the default schema, update the schema definition either in the WebSphere Application Server administrative console or in the ConfigService.properties file. If you modify the ConfigService.properties file, run the following task to make the change effective: config.bat update-was-config.
- Select the check box beside the new data source and test the connection.