Here are instructions for installing OAS 4.0.7.1 on NT4SP5. OAS 4.0.8 can
be done. You'll need to search Oracle-s docymentation and get ALL the
installation instructions since things work a little differently.
Van
Oracle Application Server 4.0.7
Now I installed Oracle Application Server from the CD_ROM. Note: The
documentation I have from Oracle is very helpful for installing, modifying
an install, or removing OAS. You can choose to do a single node or a
multi-node install. For this first try I chose to do a single node install.
That means I'll be installing a web request broker with an Oracle
Administrator listener, an Oracle HTTP listener, and Oracle Application
Server cartridges. For this first install I'll try to use Oracle products
whenever possible. Later I can try integrating Microsoft, Netscape and/or
third-party products.
- Pre-Checks
- We are going to need a variety of ports.
First we need a "boot port" which will be used by the installer. The
installer will actually use three ports: the one you name as part of the
installation and the two immediately following. I would like to use 2649 so
I will need to have 2649, 2650 and 2651 all free. Known reserved ports are
in C:\winnt\system32\drivers\etc\ However, there may be ports in use that
are not in the "known" list. You can look at ports on your machine with
netstat.
Second we need a port for the Node Manager Listener. This is the one used
for all administration work. I want to use 8888.
Third we need a (TCP) port for the Utilities Administration Listener. This
is the one used to run utilities such as the Log Analyzer. I want to use
8889.
Fourth we need a port for the Web Listener. I want to use port 80. The
proxy server already set
in Netscape is named ldfwsvr2 and runs on port 80. Jack says this will not
cause a problem,
although there may be an issue with the firewall - see step 13 below.
- STOP all Oracle processes and services. If the MSDTC service is running
stop that as well.
- If the Netscape configuration file magnus.conf is empty, the registration
process will abort and cause the browser to hang. Ensure that a valid
Netscape magnus.conf file is present before registering the Netscape
listener. (This only if you are going to use a Netscape listener. I am not
going to.)
- Oracle may modify certain environment variables. Make sure that current
settings for things like PATH are no more than 250-300 characters so you don
't bump up against the 512 character limit.
- Now the actual installation begins. Stop all Oracle processes and
services. I am putting this product
in its own Oracle Home.
name: Oas407
location: E:\Oracle\Oas
- To keep things simple I chose the Enterprise Edition. I used the export
CD-ROM so I have a 40-bit install. For now, that's fine.
- Decide what kind of install - I chose complete.
- The installer asked for the TCP/IP domain for the network. I left this
blank.
- The default web site name of website40 and boot port of 2649 are what I
used. (Oracle will also use ports 650 and 2651.)
- The port for the node manager listener is 8888 and the username/password
combination is oasadmin/oasadmin. This user will perform administration
tasks on the OAS by using the Oracle Application Server Manager. This same
name and password are used to administer the Administration Utilities
- The TCP/IP port I want for the Administration Utilitiy listener is 8889.
- The Web Listener name and port are set to www and 80 by default. I
accepted both defaults for now.
- I was asked which Oracle JDBC drivers to install. The default was to
install them all so I did that.
Oracle says this completes the installation, which is technically true.
However, there are a number of additional steps to take before anything is
useful.
- Reboot the machine.
- Now there are some problems to be fixed with the help of Oracle
support. First we need an entry in the
c:\winnt\system32\drivers\etc\hosts file which names the local machine and
the "server" machine:
127.0.0.1 localhost
10.2.112.112 dbapc_sff
Then in control panel/network go to the protocols tab and select TCP/IP and
go to properties. In the WINS address tab see that both "enable DNS for
Windows resolution" and "enable LMHOSTS lookup" are checked. My default
under the IP Address tab is to obtain an IP address from the DHPC server
which is OK. My default under the DNS tab is to have only the host name
filled in which is OK.
Finally, go to the netscape browser and under the menu item for
edit/preferences choose advanced then proxies then view proxies. There is a
box named exceptions that is empty. Fill in the name of the local machine -
dbapc_sff. This will keep me from being blocked by my own firewall when I
try to connect to my "server".
- Now you can connect to the welcome page. Use a web browser to connect
to
http://hostname.domain:port_number. For my P600 machine this is
http://dbapc_sff:8888/ (Under start menu/programs/Oracle Application
Server, Oracle has provided a two page document OAS 4.0 readme which is
specific to the install you just completed.) You are asked for the node
manager's username and password which is oasadmin/oasadmin. Go into the OAS
manager and expand the site map on the left. Under HTTP listeners pick the
first listener then double click on Network. The first line is filled in
using the name of my computer dbapc_sff. Fill in an identical second line
but use the IP address (10.2.112.112) instead of the computer name. Pick
the second listener and do the same thing.
- There are some Oracle bugs to be taken care of next. (TAR 12548347.600
2 / 1 / 588271# / 1 / 4 / 1 )
Go to the Oracle web site and download the 4.07.1 upgrade and apply it as
below:
(ftp://oracle-ftp.oracle.com/server/patchsets/internet/NT/oas40710/).
In DOS set the Oracle home
>set ORACLE_HOME=E:\oracle\oas
If you have any OAS processes running, shut them down
>owsctl stop
>owsctl stop -nodemgr
Then check in services that the services are actually stopped.
Run the script install.bat
>cd e:\alldata\download\oaspatch\oracle_app_server
>install.bat
Copy over a file
>cd e:\oracle\oas\ows\4.0\bin
>copy owsctl_std.exe owsctl.exe
(for the enterprise edition this would be >copy owsctl_ent.exe owsctl.exe)
Do a quick check
>cd e:\oracale\oas
>dir /s *.prepatch.4071
You should see a list of file names and at the end a "Total Files Listed"
as xxx files. These are the
backup files of OAS 4.0.7.0.0. If you need to revert back to the pre-patch
version of any OAS pieces you will have to
>cd e:\oracle\oas\ows\4.0\bin (or wherever)
>cp oraweb40.exe.prepatch.4071 oraweb40.exe for example
Also, Oracle support emailed me a patch,
e:\alldata\download\oaspatch\Bg768157 that is sometimes needed to fix
problems in a configuration like mine. I did not need to apply the patch.
But if you do apply the patch then afterwards, to fix a bug in the
(non-enterprise edition only), open a DOS box and type
>wrbtypset -e
- At this point you are running the OAS Management tool. What follows are
steps to get the samples
provided by Oracle to run successfully. In the database I'm going to use I
created a user oasadmin/oasadmin. This is the same name as the actual
administration tool user. On the one hand I could name the database user
something else to keep the distinction clear. On the other hand I then have
to remember another set of usernames and passwords.
- From the home page of the OAS Manager choose Utilities/Install/PLSQL
Toolkit. You will be asked
for the SID, connect string and password. You need fill in only the SID and
the password for sys. You do not need a connect string at this point.
Press the button "apply" and you'll see a log box showing what's going on.
I was lucky and the only errors were ones for dropping objects which did not
exist. Those can be ignored. When things were completed a new user had
been created in the database: oas_public with password OASADMIN. This user
owns a dozen or so packages, all of which are valid. I changed the user's
temporary tablespace away from SYSTEM. Similarly install the Log Analyzer
and the Log Tables.
- Reboot the computer or stop and restart OAS. I now created a user
oas_samp identified by oas_samp.
This will be the user that owns the sample tables that I will want to drop
at some point. Then back in the OAS Server Manager choose Oracle
Application Server/DB Access Descriptor and add a DAD for the database user
oas_samp. I used these values:
DAD Name DOASSAMP
Database User OAS_SAMP
Database User Password OAS_SAMP
Database Location (Host) dbapc_sff
Database Name (Oracle SID) DBAV
Connect String TDBAV (although this is not necessary if you are not
transaction enabling
the DAD and it is for a local database)
When I pressed apply I was asked for DBA account info. I wasn't sure which
user to put in data for since several have DBA privileges. In the end I
figured it would be safest to use SYS.
I chose to transaction enable the DAD but this may not work since I didn't
install the Enterprise edition. We'll see.
- From the OAS Manager Home Page I chose Samples Demos. I was asked for
the Administration Port
number which I made 8889 during the install (step 9 above). I was asked for
the username and password for the Admin Server. I chose oasadmin/oasadmin.
Since I had a user for the sample packages and a DAD, I chose to proceed
with installing the samples.
- I was asked for information and used this:
Database Username OAS_SAMP
Database Password OAS_SAMP
Connection String TDBAV
DBA Username sys
DBA Password sys
Then I checked the box for cartridge PL/SQL. The packages installed with
several errors, but the installer indicated a successful install at the end.
Going into SQL*Plus I can see that one package body, CNT is invalid. I
tried compiling it by hand with no luck. Then I repeated these steps for
cartridge LiveHTML, then for JWeb, then for JCO, then for Cweb, then for
MIDE Tools. Now tables and indexes have been added to the valid objects
owned by OAS_SAMP.
- At last. You can now go into any web browser and attach to the OAS
Manager by entering
http://dbapc_sff:8888/ From there you can run the sample applications and
see the code behind each
one.
Additional Notes
You can install OAS into its own home and configure one database listener to
support n database instances. You can then configure the OAS listener to
access each of the three instances serviced by that one database listener by
configuring a separate DAD for each - oracle support
Do not use the OracleOASStart40 Service to stop and start OAS.
If OAS and Oracle are on the same machine then you must place entries into
the \winnt\system32\drivers\etc\hosts file that look like this:
127.0.0.1 localhost
130.238.90.122 server.acme.com server
You may have to change the OAS tnsnames.ora file to look like the 8.1 server
tnsnames.ora file by adding various connection parameters sets.
In the OAS sqlnet.ora file you may have to change names.default_domain to
HILL (or to the domain you installed 8.1 to - look in sqlnet.ora for the 8.1
server - perhaps "world")
To de-install you must use the installer from the OAS CD-ROM, not the
regular installer.
To integrate the OAS with Oracle Enterprise Manager see page C3 in
Installation Guide
Alexey Kirich <alt_at_atlas.kiev.ua> wrote in message
news:38C3AC88.13B23C79_at_atlas.kiev.ua...
> Hi!
> After downloading this trial from technet.oracle.com version have tried
> to install it on WinNT 4.0 with SP5.
> But there are some errors in install scripts, I think. For example, some
> paths are in Unix style: with / directory delimiters. And installation
> said that he can't found some files. After correcting some paths in
> install scripts setup was able to go a little far, but have found
> another errors. I don't know what does it mean.
> Well, my question is: does anyone know how to install this software? Is
> it installable?
> Have anyone tried to install this or previous version of OAS? How to do
> this successfully?
>
> Pls., answer me via e-mail: alt_at_atlas.kiev.ua. Or in this newsgroup.
>
> Any help would be greatly appreciated. Thanks for your attention.
>
Received on Mon Mar 06 2000 - 00:00:00 CST