> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, May 19, 2004 4:22 PM
> To: 'Cactus Users List'
> Subject: RE: Cactus + Weblogic 8.1
> 
> 
> 
> 
> >  I was able to get my config.xml
> > to start my server successfully after removing the 3des 
> passwords from
> my
> > config. I also had to change the server names in my config.xml to
> match
> > the testserver that cactus is expecting.  I also had to add some
> weblogic
> > dll for nt performance to my system path.  Some reason it wouldn't
> start
> > w/o it.  I also had to add my oracle type 4 driver dll to 
> the path.  I
> > think these last two can be configured from my cactus task some how,
> but
> > i'll get there eventually.
> 
> That sounds too complex a process. We need to streamline this. One
> possible solution is to replace the configXml attribute by a configDir
> attribute which has to point to a custom WL domain directory. What do
> you think?
> 
> [snip]

I try not to much this early in the morning, but i'll give it a shot.

It would be nice if bea would make starting their server just a tad easier, eh?  I 
think the current cactus method for starting the server is ok, it would just be nice 
if you could override some of these settings your self, such as the servername, 
username, password.  The oracle driver is my "fault" for using a type 4 driver, so i 
know i'll have to have a binary driver on any platform i move to.  The other 
performance pak _shouldn't_ be required to start a server IMO, but regardless, i think 
i can overcome that.  

If i would be able to give cactus a $DOMAIN_DIR, and have it pick up what it needs 
from there (config.xml, login stuff, etc) that would be cool.  It would also be easier 
if i could specify a startup script, but only if that would work cleanly (always 
shutdown if it starts up).  I recall issues w/ the eclipse plugin where it would start 
the server, but wouldn't always stop it cleanly.  I know it wasn't using shell scripts 
to start the server, but perhaps it was starting external processes which caused 
issues always stopping it.  


> 
> -Vincent
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to