# Installation and Upgrade Guide

# Post-Installation Steps

After you run the Studio installer, complete the following steps:

1. Configure the Studio database. For information, see Configuring the Studio Database.
2. Register Studio objects with the portal. For information, see Registering the Studio Remote Portlet Package with the Portal.
3. Start the Studio service. For information, see Starting and Stopping the Studio Service.
4. Verify connectivity among Studio components. For information, see Verifying Installation.

## Configuring the Studio Database

This section describes how to set up the Studio database. It includes the following topics:

- Configuring a Microsoft SQL Server Database
- Configuring an Oracle Database

Note: | If installing on a Windows machine you can use a SQL Server or Oracle database; UNIX and Linux users can only configure an Oracle database.

### Configuring a Microsoft SQL Server Database

To script a Microsoft SQL Server database:

1. Follow the instructions for creating and configuring the Studio database for your version of Microsoft SQL Server.
2. Script the Studio database by following the instructions in Scripting the Studio Database.

#### Creating and Configuring the Studio Database on Microsoft SQL Server 2000

1. Create the Studio database:

1. Set the Studio database name to the name you specified for the Studio database when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1.
2. Verify that the initial size of the Studio database is sufficient for your Studio deployment. For a relatively small installation, configure a database that is at least 100 MB. For a large enterprise with as many as 20,000 users, configure a database that is as large as 1 GB.

2. Create the Studio database user:

1. Create the Studio database user with the user name you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1.
2. Configure the Studio database user to use SQL Server Authentication.
3. Set the Studio database user password to the password you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1.
4. Set the Studio database user’s default database to the Studio database.
5. Grant the Studio database user the public and db_owner roles for the Studio database.
6. On the Studio database Properties | Permissions tab, grant the Studio database user all permissions on the Studio database.

#### Creating and Configuring the Studio Database on Microsoft SQL Server 2005

To set up the Studio database on Microsoft SQL Server 2005:

1. Configure the SQL Server instance to use SQL Server and Windows Authentication mode.
2. Create the Studio database:

1. Set the Studio database name to the name you specified for the Studio database when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1.
2. Verify that the initial size of the Studio database is sufficient for your Studio deployment. For a relatively small installation, configure a database that is at least 100 MB. For a large enterprise with as many as 20,000 users, configure a database that is as large as 1 GB.
3. Configure the Studio database to use SQL Server 2000 (80) compatibility level.

3. Create the Studio database user:

1. Create the Studio database user with the user name you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1.
2. Configure the Studio database user to use SQL Server Authentication.
3. Set the Studio database user password to the password you designated when you completed the worksheets provided in the Installation Worksheet for AquaLogic Interaction Studio 2.2 MP1.
4. Set the Studio database user’s default database to the Studio database.
5. Grant the Studio database user the sysadmin server role.

#### Scripting the Studio Database

Run the database script as the Studio database user on the Studio database created above.

1. Copy the <PT_HOME>\ptstudio\2.2\sql\MSSQLServer\cretbl.sql script from the Studio host machine to the Studio database host machine.
2. To delete previous tables (if they exist) and create the tables required for the new portal components, run the <PT_HOME>\ptstudio\2.2\sql\MSSQLServer\cretbl.sql script.

### Configuring an Oracle Database

This section describes how to create and configure the Oracle database for Studio. It describes the following basic steps:

1. Set up your database environment. For details, see Setting Up Your Database Server Environment.
2. Customize the database scripts provided by the Studio installer. For details, see Customizing the Oracle Database Scripts.
3. Run the scripts to configure the Studio database. For details, see Creating and Configuring the Studio Database.

#### Setting Up Your Database Server Environment

You must use the same database vendor and version for your Studio database as you do for your portal database. For example, if your portal database runs on Oracle Server 9i, your Studio database must also run on Oracle Server 9i. Do not mix and match database types or versions within your system.

Before you create the Studio database:

- Run the latest Oracle patch set.
- Set up the database to archive log files. With the default configuration, you must shut down the database to get a read-consistent backup.
- Customize the Oracle database scripts, as described in the next section.

#### Customizing the Oracle Database Scripts

The installation wizard installs database scripts for Oracle 9i databases in the following locations:

- For Windows: C:\bea\alui\ptstudio\2.2\sql\Oracle\oracle_nt9.2
- For UNIX or Linux: /opt/bea/alui/ptstudio/2.2/sql/Oracle/oracle_unix9.2

The database scripts for Oracle 10g databases are in the following locations:

- For Windows: C:\bea\alui\ptstudio\2.2\sql\Oracle\oracle_nt10
- For UNIX or Linux: /opt/bea/alui/ptstudio/2.2/sql/Oracle/oracle_unix10

Note: | You should only customize and run the scripts needed for your installation. Check the Creating and Configuring the Studio Database section to determine if you are creating a new database or just the tablespace.

Customize the values specified in the scripts according to the following table.

Table 5-1 Database Scripts
File Name | Function | Change
--- | --- | ---
CreateService.bat (Windows only) | Creates an instance service for PTSTUDIO and sets the ORACLE_SID environment variable to ptstudio. | Replace the default password, `welcome`, for the `sys` user with a secure password. Make sure the location of initplum.ora is correct. The default is C:\oracle\ora92\database\initptstudio.ora.
Note: | You must manually copy this file to the correct location.
ShutdownPTStudio.bat (Windows only) | Shuts down Studio. | Replace the default password, `welcome`, for the `sys` user with a secure password. If necessary, change the SID.
create_studio_oracle.sql | Creates Studio schema and tablespaces. | If necessary, change the location of tmp1PTSTUDIO.dbf (the temporary tablespace) and data1PTSTUDIO.dbf (the Studio tablespaces). If necessary, replace the default user, `studioapp`, with the user that will run the Studio database. If necessary, replace the default password, `studioapp`, for the Studio database user with a secure password.
crdb1.sql | Creates the database. | If necessary, change the location of log1PTSTUDIO.dbf, log2PTSTUDIO.dbf, and log3PTSTUDIO.dbf (the log files) and systPTSTUDIO.dbf (the system tablespace files). If necessary, change the SID.
crdb2.sql | Creates and configures the default Studio database tablespaces. |
initptstudio.ora | Stores the database configuration settings | The Oracle DBA should review this script. The runtime settings default to a small database and need to be modified to fit your Studio system by a qualified Oracle DBA. If necessary, change the SID.
RegisterSIDPTSTUDIO.reg | Registers the database | Replace the default password, `welcome`, for the `sys` user with a secure password. If necessary, change the SID.
StudioServerCreateTables_oracle.sql | Configures the Studio database schemas |

#### Creating and Configuring the Studio Database

This section describes how to create and configure an Oracle database for Studio. The topics in this section describe the following options:

- Creating and Configuring the Studio Database on Windows
- Creating and Configuring the Studio Database on UNIX and Linux
- Creating a Studio Tablespace in an Existing Database on Windows
- Creating a Studio Tablespace in an Existing Database on UNIX and Linux

You need to complete only one of these options to configure your Studio database.

##### Creating and Configuring the Studio Database on Windows

Complete the following steps:

1. On the computer where the database resides:

- Create the folder %ORACLE_HOME%\oradata\[ORACLE_SID],
  where [ORACLE_SID] is your SID, for example %ORACLE_HOME%\oradata\PTSTUDIO.
- Create the folder %ORACLE_HOME%\ptstudioscripts.
- Copy the Studio database scripts from the default Studio installation location into this folder. The default installation location is noted at the beginning of Customizing the Oracle Database Scripts.

2. Copy initptstudio.ora from the ptstudioscripts folder to the database folder under %ORACLE_HOME%.
3. From the ptstudioscripts folder, run RegisterSIDPTSTUDIO.reg to set PTSTUDIO as the default Oracle database in the registry.
4. Run the CreateService.bat batch file from the ptstudioscripts folder to create an instance service for PTSTUDIO and to set the ORACLE_SID environment variable to PTSTUDIO.
5. Use sql*plus to execute crdb1.sql within the script directory. This script creates the Studio database. Log in as the system user to execute this script.

1. At the command prompt, type: `sqlplus /nolog`
2. Type: `connect system/<password> as sysdba`. The default password is `manager`.
3. Execute the script by typing: `@crdb1.sql`

If you do not execute the script from the script directory, you must type the full pathname. For example: `@C:\oracle\ora9i\ptstudioscripts\crdb1.sql`

The output text appears. If the script finishes with “`Statement processed with no errors`,” then the crdb1.sql script succeeded. The output for this script can be found in 1-rdbms.lst.

6. As the system user, execute crdb2.sql to create the required tablespaces and the Studio database user. Type: `@crdb2.sql`.

If you do not execute the script from the script directory, you must type the full path name. For example: `@C:\oracle\ora9i\ptstudioscripts\crdb2.sql`

The output text appears. This script may take up to 40 minutes to complete. It is not as easy to determine if this script was successful. This is especially true since some errors are acceptable, such as “`ORA-00942 table or view does not exist`” or “`ORA-1432/ORA-1434 public synonym to be dropped does not exist.`” The output for this script can be found in 2rdbms.lst.

7. Exit sql*plus.
8. Log back in to sql*plus as the Studio user and execute StudioServerCreateTables_oracle.sql to create Studio schemas.

1. At the command prompt, type:
   `sqlplus <studio_user>/<password>@<SID>`
2. Type: `@StudioServerCreateTables_oracle.sql`.

If you do not execute the script from the script directory, you must type the full pathname. For example: `@C:\oracle\ora9i\ptstudioscripts\
StudioServerCreateTables_oracle.sql`

9. Exit sql*plus.

##### Creating and Configuring the Studio Database on UNIX and Linux

Complete the following steps:

1. Log in to the Oracle Server computer as the owner of the Oracle system files.
2. Create the folder $ORACLE_HOME/oradata/[ORACLE_SID],
   where [ORACLE_SID] is your SID, for example $ORACLE_HOME/oradata/PTSTUDIO.
3. Create a .zip file called ptstudiosql.zip that includes all the SQL scripts in the appropriate installation directory. The installation location is noted at the beginning of Customizing the Oracle Database Scripts.
4. FTP the ptstudiosql.zip file to the UNIX or Linux computer on which your database resides.
5. On the UNIX or Linux computer on which the portal database resides:

1. Log in as the Oracle user.
2. Create the directory $ORACLE_HOME/ptstudioscripts.
3. Unzip the ptstudiosql.zip file in the $ORACLE_HOME/ptstudioscripts directory.

6. Make sure that the ORACLE_HOME and ORACLE_SID variables are set.

In all the SQL script execution steps, replace ORACLE_SID with the SID or the TNS Alias (if it differs from the SID).

7. From the ptstudioscripts folder, copy initptstudio.ora under the database directory (for example, to /opt/ora9i/database).
8. Create an entry for the database PTSTUDIO in the /var/opt/oracle/oratab file. Add the following line to the end of the file: `PTSTUDIO:$ORACLE_HOME:Y:`
9. Create an Oracle password file by executing the orapwd utility.

1. Go to the $ORACLE_HOME/bin directory by typing the command:
   `cd $ORACLE_HOME/bin.`
2. Then type: `./orapwd file=$ORACLE_HOME/dbs/orapwPTSTUDIO
   password=<password>`, where`<password>` is the Oracle sysuser password.

10. Use sql*plus to execute crdb1.sql within the script directory. This script creates the Studio database. Log in as the system user to execute this script.

1. At the command prompt, type: `sqlplus /nolog`
2. Type: `connect system/<password> as sysdba`. The default password is `manager`.
3. Execute the script by typing: `@crdb1.sql`

If you do not execute the script from the script directory, you must type the full path name. For example: `@/ora/ora9i/database/ptstudioscripts/crdb1.sql`

The output text appears. If the script finishes with “`Statement processed with no errors`,” then the crdb1.sql script succeeded. The output for this script can be found in 1-rdbms.lst.

11. As the system user, execute crdb2.sql to create the required tablespaces and the Studio database user. Type: `@crdb2.sql`.

If you do not execute the script from the script directory, you must type the full pathname. For example: `@/ora/ora9i/database/ptstudioscripts/crdb2.sql`

The output text appears. This script may take up to 40 minutes to complete. It is not as easy to determine if this script was successful. This is especially true since some errors are acceptable, such as “`ORA-00942 table`” or “`view does not exist`” or “`ORA-1432/ORA-1434 public synonym to be dropped does not exist.`” The output for this script can be found in 2rdbms.lst.

12. Exit sql*plus.
13. Log back in to sql*plus as the Studio user and execute StudioServerCreateTables_oracle.sql to create Studio schemas.

1. At the command prompt, type:
   `sqlplus <studio_user>/<password>@<SID>`
2. Type: `@StudioServerCreateTables_oracle.sql`.

If you do not execute the script from the script directory, you must type the full pathname. For example: `@/ora/ora9i/database/ptstudioscripts/StudioServerCreateTables_oracle.sql`

14. Exit sql*plus.
15. Configure the listener for this database and start the listener.

##### Creating a Studio Tablespace in an Existing Database on Windows

Complete the following steps:

1. On the computer where the database resides create the folder %ORACLE_HOME%\ptstudioscripts. Copy the Studio database scripts from the default Studio installation location into the folder that you created in the previous step. The installation location is noted at the beginning of Customizing the Oracle Database Scripts.
2. Use sql*plus to execute create_studio_oracle.sql within the script directory. This script creates the Studio database. Log in as the system user to execute this script.

1. At the command prompt, type: `sqlplus /nolog`
2. Type: `connect system/<password> as sysdba`. The default password is `manager`.
3. Execute the script by typing: `@create_studio_oracle.sql`

If you do not execute the script from the script directory, you must type the full path name. For example: `@C:\oracle\ora9i\ptstudioscripts\create_studio_oracle.sql`

3. Exit sql*plus.
4. Log in to sql*plus as the Studio user and execute StudioServerCreateTables_oracle.sql to create Studio schemas.

1. At the command prompt, type:
   `sqlplus <studio_user>/<password>@<SID>
   `SID is the database name.
2. Type: `@StudioServerCreateTables_oracle.sql`.

If you do not execute the script from the script directory, you must type the full path name. For example: `@C:\oracle\ora9i\ptstudioscripts\
StudioServerCreateTables_oracle.sql`

5. Exit sql*plus.

##### Creating a Studio Tablespace in an Existing Database on UNIX and Linux

Complete the following steps:

1. Log back in to the Oracle Server computer as the owner of the Oracle system files.
2. Create a .zip file called ptstudiosql.zip that includes all the SQL scripts in the appropriate installation directory. The installation location is noted at the beginning of Customizing the Oracle Database Scripts.
3. FTP the ptstudiosql.zip file to the UNIX or Linux computer on which your database resides.
4. On the UNIX or Linux computer on which the portal database resides:

1. Log in as the Oracle user.
2. Create the directory $ORACLE_HOME/ptstudioscripts.
3. Unzip the ptstudiosql.zip file in the $ORACLE_HOME/ptstudioscripts directory.

5. Use sql*plus to execute create_studio_oracle.sql within the script directory. This script creates the Studio database. Log in as the system user to execute this script.

1. At the command prompt, type: `sqlplus /nolog`
2. Type: `connect system/<password> as sysdba`. The default password is `manager`.
3. Execute the script by typing: `@create_studio_oracle.sql`

If you do not execute the script from the script directory, you must type the full pathname. For example:
`@/ora/ora9i/database/ptstudioscripts/create_studio_oracle.sql`

6. Exit sql*plus.
7. Log in to sql*plus as the Studio user and execute StudioServerCreateTables_oracle.sql to create Studio schemas.

1. At the command prompt, type: `sqlplus <studio_user>/<password>@<SID>`
2. Type: `@StudioServerCreateTables_oracle.sql`.

If you do not execute the script from the script directory, you must type the full pathname.

8. Exit sql*plus.
9. Configure the listener for this database and start the listener.

## Registering the Studio Remote Portlet Package with the Portal

You register the Studio portlets with the portal by importing the Studio remote portlet package.

To import the remote portlet package into the portal:

1. Log in to the portal as an administrator.
2. Click Administration.
3. From the Select Utility menu, select Migration - Import.
4. Click Browse and locate the ptstudio.pte file in <PT_HOME>\ptstudio\2.2\serverpackages\. Click Open.
5. Click Load Package.
6. Select Overwrite Remote Servers.
7. Click Finish.

## Starting and Stopping the Studio Service

This section describes how to start and stop the BEA ALI Studio service.

### Starting the Studio Service in Windows

From the Service Control Manager, start the BEA ALI Studio service.

Or, from the command line, run

    $ <install base>\ptstudio\2.2\bin\service.bat start

### Starting the Studio Service in UNIX and Linux

From the command line, run

    $ .<PT_HOME>/pthome.sh

    $ sh <PT_HOME>/ptstudio/2.2/bin/service.sh start

Note: | If your PT_HOME is a directory other than /opt/bea/alui, you will need to edit the file <PT_HOME>/pthome.sh so that PT_HOME is set to the correct value.

### Stopping the Studio Service in Windows

From the Service Control Manager, stop the BEA ALI Studio service.

Or, from the command line, run

    $ <install base>\ptstudio\2.2\bin\service.bat stop

### Stopping the Studio Service in UNIX and Linux

From the command line, run

    $ sh <PT_HOME>/ptstudio/2.2/bin/service.sh stop

## Verifying Installation

To verify successful installation and initial configuration:

1. If you are working on a Windows machine and have not yet done so, reboot the Studio host computer.
2. To display a diagnostics page that enables you to verify your installation, enter the following URL in your Web browser: `http://<studio_host>:<port>/studio/gw?m=admin.diagnostics`

If the diagnostics page reports errors, see Troubleshooting.