2 Preparing for Foundation Pack Installation

2.1.1 Installation Location Screen

On this screen you set the home directory for installation. Table 2-1 lists the fields located on the Installation Location screen.

2.1.2 SOA Server Details Screen

All artifacts associated with the Foundation Pack infrastructure components are deployed to the SOA Suite server. This screen contains the fields listed in Table 2-2.

When you click Next, Foundation Pack Installer checks whether the node manager service is available. You may also need to check whether the node manager service is active from Oracle WebLogic Admin server Console. If your node manager is not active in the admin console, refer to Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server for troubleshooting.

2.1.3 AIA Database Details Screen

Configure the following database schemas for installation of AIA. These schemas are displayed in the screen. The AIA Instance name that you have provided (see Table 2-1) will be prefixed to the schema names. The following are the AIA related schemas:

• <INST>_AIA: Holds error handling setup information, system setup information, CAVS data, and so on.

• <INST>_XREF: Holds the cross-reference information.

• <INST>_AIALIFECYCLE: Holds information created for AIA project lifecycle workbench application.

• <INST>_JMS: For JMS usage in AIA.

To configure these schemas you need JDBC connection details, passwords for the schemas, and SYS user credentials (if you want AIA Foundation Pack Installer to create the schema and underlying tables). Keep the information ready before you run the Installer.

When you configure the schemas you can:

• Choose the same JDBC information for one or more schemas. The schemas can reside in many or one physical database server.

• Choose to connect to an existing AIA schema (created manually using scripts). This means a particular schema holds information common to multiple installations. For example: AIALIFECYCLE.

Fill out the information below for all the AIA schemas.

Database Connection Details

You can either Enter Custom JDBC URL or enter the required details in Host Name, Port and Service Name fields. When you opt for custom JDBC URL, the other three fields disappear. This will be useful when connecting to Oracle RAC databases.

Enter the Custom JDBC URL, as shown in Table 2-3.

Or

Enter Database Connection Details, as shown in Table 2-4.

Schema Details

If you choose to connect to an existing schema, you will be prompted to enter username and password.

If you choose to create a new schema, you will be prompted to enter the admin username/password required to create the required schema. This is typically SYS.

The database chosen here can be the same server as the database server that SOA Suite uses, or it can be different physical database server.

Connect to Existing Schema

Connect to existing schema, as shown in Table 2-5.

Or

Create New Schema

Create new schema, as shown in Table 2-6.

2.1.4 Metadata Service Repository Screen

This is the location where AIA Foundation Pack Metadata Artifacts are stored. Though the screen contains multiple fields, you need to provide only the password. Data in the other fields normally populates automatically. If it does not, then you need to enter the data manually. The screen contains the fields listed in Table 2-7.

2.1.5 Oracle Enterprise Repository Details Screen (Optional)

Oracle Enterprise Repository is a product separate from AIA Foundation Pack and is an optional component in the context of AIA Foundation Pack installation and execution.

If you do not want to adopt Oracle Enterprise Repository at this time, click Next to skip this page.

During AIA Foundation Pack installation, provide the Oracle Enterprise Repository-related information when prompted by the AIA Foundation Pack Installer. The screen contains the fields listed in Table 2-8.

When you click Next, Foundation Pack Installer prompts you to enable Remote JDBC. For harvesting, Remote JDBC must be enabled prior to invoking Harvester.

For information about how to enable remote JDBC, see Oracle Fusion Middleware Installation Guide for Oracle Application Integration Architecture Foundation Pack, Enabling Remote JDBC Connection in WebLogic Server.

Click OK and continue with installation.

Run-time service information is not automatically available in Oracle Enterprise Repository at the end of AIA Foundation Pack installation. Populating this information is a post-install activity.

For more information about adopting Oracle Enterprise Repository after AIA Foundation Pack has been installed, see "Harvesting Oracle AIA Content" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

2.2.1 Ensuring Correct Settings for Node Manager Startup

To ensure correct settings for Node Manager startup:

1. Navigate to the $MW_HOME/wlserver_10.3/common/nodemanager.

2. Open the nodemanager.properties file and verify the value for StartScriptEnabled property.

3. If it is false change to StartScriptEnabled=true

4. If you changed the above value, restart Node Manager by navigating to $MW_HOME/wlserver_10.3/server/bin and using the appropriate commands.

5. While starting the node manager, ensure that you set the listen address different from localhost. It is preferred to give the fully qualified name of the machine.

   For Example: ./startNodeManager.sh for Linux and startNodeManager.bat for Microsoft Windows.

   Before running the command, navigate to the WebLogic console, click Machines, Nodemanager. Here ensure that the value of Listen address and Listen port are the fully qualified name of the machine and port number respectively.

6. Ensure that you start the SOA Server using the Node manager.

To ensure correct settings for Node Manager startup in production environment:

You may also need to check whether the node manager service is active from Oracle WebLogic Admin server Console. If your node manager is not active in the admin console, refer to http://download.oracle.com/docs/cd/E13222_01/wls/docs92/server_start/nodemgr.html for troubleshooting.

2.2.2 Performing Prerequisites for Cluster Installation

To perform prerequisites for cluster installation:

1. Open admin console

2. Click on View Changes and Restart in Change Center.

3. Click on Restart Checklist.

4. Ensure that there is no admin server or any of the soa_servers of the cluster on the restart checklist.

5. If there are any servers listed, restart the mentioned server.

If you are installing only Foundation Pack on cluster, then:

1. Open the <WebTier_HOME>/instances/<instances_name>/config/OHS/ohs1/mod_wl_ohs.conf file.

2. Add the following code.

   <Location /AIA>
   SetHandler weblogic-handler
   WebLogicCluster <machine1_hostname>:<port>,<machine2_hostname>:<port>
   WLLogFile /tmp/web_log.log
   </Location>
   

2.2.3 Creating AIA schemas (Optional)

AIA Foundation Pack Installer gives you the flexibility to choose the schema name, password along with the default and temporary tablespace on which the schemas have to be created.

In addition to that, AIA Foundation Pack allows you to create AIA Schemas and other DB artifacts in a manner that best fits your organization standards and advanced database options. AIA schemas along with the database artifacts can be created using the SQL script templates shipped with the AIA Foundation Pack installation bundle under <shiphome>/cd/Disk1/misc/sql of your AIA Foundation Pack Installation CD. These SQL scripts should be executed for creating the schemas before launching the Installer.

Follow the below steps before you launch the installer.

1. Create AIA, XREF, AIALIFECYCLE, JMS schemas. The scripts located under <shiphome>/cd/Disk1/misc/sql folder i.e. createAIASchema.sql, createJMSSchema.sql, createLifecycleSchema.sql, createXRefSchema.sql can be used as templates to create the schemas.

2. Execute populate data scripts as described below:

   1. populateAIASchema.sql against AIA schema.

   2. populateJMSSchema.sql against JMS schema.

   3. populateLifecycleSchema.sql against AIALIFECYCLE schema.

   4. Execute SOA_HOME/rcu/integration/soainfra/sql/xref/createschema_xref_oracle.sql against XREF Schema.

Once you finish the above process, launch the installer and in the Database Details Screen, choose Connect To option to connect to the schema that was created. For other schema types for which the SQL scripts were not executed manually choose the Create New Schema option.

2.2.4 Administering MDS Tablespace

AIA Foundation Pack loads a lot of data to MDS as a part of deployment. The default tablespace allocated may not be sufficient when multiple repetitive AIA Foundation Pack deployments are done on the same server. This may cause the error

"Unable to extend tablespace "

If you see the message you can increase the tablespace size.

If you have cleared a large amount of data from a data object, and expect the tablespace to have more data, you may still see this error. The tablespace release is not synchronous, and you must run command ALTER TABLE table_name SHRINK SPACE.