INSTALLATION GUIDE FOR EXPRESS SERVER 6.3.4.

on
Solaris and CONNECTION TO WINNT CLIENT

AUTHOR:
MANIKANDAN

Wipro Technologies
May 2006
 1) Download the Server Patch: p2378266_634_SOLARIS.zip from
metalink.oracle.com. The patch number is 2378266.

2) Create the user “oracle” (Installation user) with a proper password and copy the
zip file (i.e., p2378266_634_SOLARIS.zip) to oracle’s home directory.

3) Create other users: oesdba (DBA User), oesinit (Initialization User) and oesguest
(Guest User) with proper passwords. Out of these, the oesdba user is mandatory
and the others are optional but recommended. Also, the oesdba user should be able
to access all the directories and files residing in the oracle user’s directories.

4) Change the ownership of all the installation files to oracle user.

Connect as oracle user. Unzip the file using the following command:
$unzip p2378266_634_SOLARIS.zip in oracle’s home directory.

5) Go to the following directory in oracle’s home:

$HOME/71121-H-MLE/Disk1/install/solaris/.

6) Assign execute permissions to the runInstaller file in this manner:

$chmod 775 runInstaller

Define the ORACLE_HOME in the .profile file in the home directory. i.e., add the
following lines at the end of the .profile file:

ORACLE_HOME=<location for ORACLE_HOME>

export ORACLE_HOME

Set the same for oesdba (mandatory), oesinit and oesguest (if applicable).

7) Now run the runInstaller in the $HOME/71121-H-MLE/Disk1/install/solaris/

directory:

$./runInstaller

8) The following Welcome Screen will appear:

9) Then, we have to enter the oracle sid name and the path for the home directory. Press
Next:
10) The following products are displayed. Select the product and click NEXT.

11) The installation types are shown. Choose the one that applies for your installation:
12) If Oracle HTTP Server is configured on the system, it will prompt for its
configuration. Choose ‘yes’ if you want to configure it. This is useful for the Oracle
Express Web Agent, which allows the administration of Instance Manager through web.
13) The installer will give the list of products that will be installed. Please go through the
list to find out any anamolies.
14) Installation Taking Place #1:

15) Installation Taking Place #2:

16) Successful Installation Completion:

17) Connect as root in the Server and run the root.sh script that will configure the Express
Server.
18) Sometimes the netca can fail if the ORACLE_HOME is not properly configured.
Please re-run netca from $ORACLE_HOME/bin after the installation gets over.
19) Completed Installation:

INSTALLING THE EXPRESS INSTANCE MANAGER 6.3.4.0.0

Steps:

1) Follow the same steps from 1 to 3 for the installation of Express Server.

2) This time, in Step 3, select Express Instance Manager and Click NEXT.

3) The following Screen appears indicating the installation:

4) Installation Taking Place:

4) Installation Successfully Completed:

INSTALLING WEB LISTENER COMPONENTS AND SNAPI CLIENT 6.3.4.0.0

Steps: Similar to the installation of Express Instance Manager except for that in Step 3,
you have to select Oracle Web Listener Components 6.3.4.0.0. or SNAPI Client
6.3.4.0.0 respectively.

CLIENT-SIDE INSTALLATION FOR EXPRESS:

Steps:

1) Download the file p2378248_634_WINNT available in metalink as patch number

2378248. I have done the same for WINNT client.

2) The installation is similar to that of Server’s except that the Express Client’s
products include the following:

• Oracle Express OLAP Client Products and Utilities, that include,

1) Adminstrator Tool
2) Sales Analyzer Client
3) Financial Analyzer (OFA)
4) Express Connection Editor and Utility
5) Oracle Batch Manager
6) Oracle Relational Access Manager Adminstrator
7) Oracle Web Publisher
• Personal Express 6.3.4.0.0.

3) Choose one of the installations and Continue.

4) NOTE: The Express Client will prompt for Shared LAN Server, which you have
to deselect if you are doing Custom Setup. Opt for Shared Workstation Server if
ORACLE INTERNET DIRECTORY (OID) is available. Otherwise, you have to
provide the OID’s location which will be prompted to you.

STARTING THE EXPRESS SERVICE ON THE SERVER AND TESTING THE

CONNECTION BETWEEN CLIENT AND SERVER:

Starting the Express Instance Manager:

1) Connect as oesdba to the Server.

2) Go to $OLAP_HOME/oes634/eim/
3) Run eim.sh.

Starting the Service:

The following Snapshot shows the EIM started.

Once the EIM is started, we have to check the services’ status. We can do this by
expanding the instance list on which we have to authenticate the user by entering the user
id and password. The snapshot is shown below.
After this we can check the service status in this manner. If the service is not started, we
can start it using the service start radio button. The log directory specifies each and every
step during the startup or shutdown of the services.

Testing the Connection from Client:

1) Start the Express Connection Editor from the Client Machine.

2) If a connection has not been defined at all, choose define. Enter the proper values for
the connection. The Snapshot below gives a brief idea:

3) Click OK to complete the creation of .xcf (Express Connection File).

4) Start any application (example: Express Analyzer). Select the appropriate Connection
file from $OLAP_HOME/ECF634/ (depending on the version. $OLAP_HOME/ECF632/
in our case).

5) Click “Open” and Check if the connectivity has some errors.