Yes, I'm talking about Release 2, and I'm not talking about doing a
infrastructure install. I already have a working beast on another server
acting as my OID server. What I'm talking about is performing the enterprise
install of the App Server mainly for Portal and IFS use on a separate
server. The install will never asks where you want the portal repository
installed, it will just assume that you want to install it on the same
database as where your infrastructure lives. It does ask where your SSO
server lives and just runs with the idea of where to install the portal
repository. Very Cheesy.
"Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
news:X6JE9.84195$g9.237224_at_newsfeeds.bigpond.com...
> I take it you mean Release 2 of the Application Server?
>
> Do an infrastructure install and you get a completely new database.
>
> And no, it is not possible to use a pre-existing database for an
> infrastructure (repository) install. The repository database MUST be
9.0.1,
> and has to have certain other attributes about it which the infrastructure
> install gets right and the installer doesn't trust you to have gotten
right.
>
> Regards
> HJR
>
> "dmitchell" <dmitchell_at_cox.net> wrote in message
> news:mfCE9.165396$E54.1269563_at_news1.east.cox.net...
> > Greetings all,
> >
> > How come the new 9.02 AS install does not allow you to point to your own
> > database repository. Its asks me for the location of the OID server, and
> > then proceeds to install the Portal schema on top of the OID database.
Is
> > there not a way to get around this install nature when the DB you want
to
> > install to is other than your separate OID server?
> >
> >
> >
>
>
Received on Tue Nov 26 2002 - 19:42:25 CST
