Weblogic.system.listenPort property in Weblogic 6.0?

There is any property for manually indicate listen port like:
weblogic.system.listenPort
Baco, por siempre loado,
os libre del cirrotico mal
y del advenimiento gonococico.
[att1.html]

In 6.0, there is a "ListenPort" attribute in the <Server> tag in the config.xml file of the domain that a server belongs to.
Giri
"Paco Avila - Desarrollo" <[email protected]> wrote in message news:[email protected]..
There is any property for manually indicate listen port like:
weblogic.system.listenPort
Baco, por siempre loado,
os libre del cirrotico mal
y del advenimiento gonococico.
[att1.html]

Similar Messages

Use of weblogic.system.home property

Hi,
I am working on Windows 2000, with weblogic 6.0.
I am trying to launch the default weblogic server with the
script startWebLogic.cmd, but I modified the original script
to set the current directory as the script directory.
So I commented the cd ..\.. command and set the weblogic.system.home on the java
weblogic.Server, as it is
written in the adminguide page 2-6
But it seems that weblogic can no longer find the config.xml file.
In fact the exception I got is the following "weblogic.management.configuration.ConfigurationException:
XmlRepository directory .\config does not exist" and the startup.log file contains
the following warning : "####<Feb 10, 2001 12:12:51 PM EST> <Warning> <Management>
<nicolas> <myserver> <main> <> <> <000000> <Unrecognized property: system.home>"
So I am just wondering if the system.home property is still supported or if it is
a documentation mistake (or misunderstanding)
Else is there any way to start a weblogic server with the home dir different than
the installation root.
Thanks
But

"-Dweblogic.RootDirectory=c:\bea\wlserver6.0sp1" . . . Thank you Vijay at BEA
"David Brown" <[email protected]> wrote:
>
Does any have any more information regarding using the new 'ServerMBean.RootDirectory'
property ? I really need to find a way to tell weblogic 6.0sp1 where
to find
it's XmlRepository. (./config)
In our instalaltion, "./config" is under c:\bea\wlserver6.0sp1\, but
we are launching
the JVM from a directory outside of c:\bea\wlserver6.0sp1, so I need
to tell the
VM where to look for ./config
Thanks,
David
"Sanjeev Chopra" <[email protected]> wrote:
Nicolas GANDRIAU <[email protected]> wrote in message
news:3a859168$[email protected]..
Hi,
I am working on Windows 2000, with weblogic 6.0.
I am trying to launch the default weblogic server with the
script startWebLogic.cmd, but I modified the original script
to set the current directory as the script directory.
So I commented the cd ..\.. command and set the weblogic.system.homeon
the java
weblogic.Server, as it is
written in the adminguide page 2-6
But it seems that weblogic can no longer find the config.xml file.
In fact the exception I got is the following"weblogic.management.configuration.ConfigurationException:
XmlRepository directory .\config does not exist" and the startup.logfile
contains
the following warning : "####<Feb 10, 2001 12:12:51 PM EST> <Warning><Management>
<nicolas> <myserver> <main> <> <> <000000> <Unrecognized property:system.home>"
So I am just wondering if the system.home property is still supportedor
if it is
a documentation mistake (or misunderstanding)This is a bug in 6.0 (system.home does not work).
This will be fixed for upcoming ServicePack 1, which defines a new
property - ServerMBean.RootDirectory
Else is there any way to start a weblogic server with the home dirdifferent than
the installation root.
Thanks
But

Reading from a non-HTTP socket in WL; same idea as WL.system.listenPort

Hi Fellow EJBers,
I have a system which must listen on a TCP port that is not the normal
WebLogic port nor the standard HTTP port for client connection
requests. Unfortunately, the protocol is low-level TCP/IP sockets and
as it's coming from a legacy system I cannot change. What I'd like to
do is create a startup class in the EJB server that listens to the
correct port and then hands off the socket ID to a bean for further
processing. Then when the response is ready I can use a simple socket
write() method.
I am hoping that this will allow me to use WebLogic's built-in threading
support in this class. I was hoping to find some way to imitate the
WebLogic properties file entry
weblogic.system.listenPort=7001
but I didn't see any references to it in the documentation. Can I use a
servlet or startup class to do this? I don't want to use events if I
can help it to maintain compatibility. Alternatively, I'm thinking
about using a separate Java process running in a different JVM which
would manage the threading issues. This is less desirable because it
complicates sending responses back and I don't know if I can pass the
socket reference into EJB.
Note that right now I'm only worrying about the listening portion, I
must also send requests out to different machines but here I control the
initiation.
Thanks for any and all help,
Terry ([email protected])

Rob,
Could you please explain why you should not create worker threads in the server.
I created a GenericServlet and installed it in the ServerClasses so it does not
ever get more than one instance - it listens on a server socket (in a thread) and
accepts connections and allows replies to the
connected socket. I use it for debugging where you connect to the port with Telnet and
each developer that wants to output a debug string from a JSP back to their Telnet can
do so. It works fine.
I don't want to screw the server up so please enlighten me.
Joe
Rob Woollen wrote:
If you have a legacy system that is sending data over TCP/IP sockets, you have
to have a socket for it somewhere. It's certainly not an ideal situation since
WebLogic already provides these basic services for you, just not for an arbitrary
protocol.
You definitely should not create worker threads in the server. Use WebLogic
events or JMS instead.
-- Rob
Rob Woollen
Software Engineer
BEA WebLogic
[email protected]
Russell Castagnaro wrote:
Rob,
Is it OK to start your own threads that listen on a particular port? I've been
informed over and over again that this is a recipe for disaster. If it is
acceptable to start up a port listener thread at some times, when is it
acceptable and when isn't it? (I know not to do it with Servlets or EJB's)
Thanks in advanced..
Russell
Rob Woollen wrote:
Hi.
Terence Davis wrote:
Hi Fellow EJBers,
I have a system which must listen on a TCP port that is not the normal
WebLogic port nor the standard HTTP port for client connection
requests. Unfortunately, the protocol is low-level TCP/IP sockets and
as it's coming from a legacy system I cannot change. What I'd like to
do is create a startup class in the EJB server that listens to the
correct port and then hands off the socket ID to a bean for further
processing. Then when the response is ready I can use a simple socket
write() method.
Okay, that seems reasonable. Note, that EJB 1.1 (the next version of
the spec) prohibits bean writers from directly reading or writing sockets.
I am hoping that this will allow me to use WebLogic's built-in threading
support in this class. I was hoping to find some way to imitate the
WebLogic properties file entry
weblogic.system.listenPort=7001
but I didn't see any references to it in the documentation.I'm not sure that I follow. You could use your own properties file if
you want to configure a listen port for your socket.
Can I use a
servlet or startup class to do this? I don't want to use events if I
can help it to maintain compatibility.JMS (available in 4.5.x) is a J2EE standard tha has a superset of the
events functionality.
Alternatively, I'm thinking
about using a separate Java process running in a different JVM which
would manage the threading issues. This is less desirable because it
complicates sending responses back and I don't know if I can pass the
socket reference into EJB.
Note that right now I'm only worrying about the listening portion, I
must also send requests out to different machines but here I control the
initiation.
Thanks for any and all help,
Terry ([email protected])
Russell Castagnaro
Chief Mentor
SyncTank Solutions
http://www.synctank.com
Earth is the cradle of mankind; one does not remain in the cradle forever
-Tsiolkovsky

Weblogic.system.home property

Hi,
I used to launch weblogic 5.1 from a directory other that the wl
installation directory by passing -Dweblogic.system.home=myDirectory when
launching the server. This doesn't work with 6.0. I get the following
exception (note that if I start wl from its installation directory,
everything is fine) :
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Unable to start WebLogic Server !!
Improperly formatted license file: D:\license.bea
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Is "weblogic.system.home" still valid ? If not, what is the new way of doing
this?
Thanks, Alexandre.

I don't know if this was a problem in beta-1.
Could you try beta-2 (download from bea.com) and re-post if you still
see the problem?.
I just tried with the latest source line and i can run the server by
specifying a different
weblogic home directory.
Kumar
Alexandre Vauthey wrote:
>
Hi,
I used to launch weblogic 5.1 from a directory other that the wl
installation directory by passing -Dweblogic.system.home=myDirectory when
launching the server. This doesn't work with 6.0. I get the following
exception (note that if I start wl from its installation directory,
everything is fine) :
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Unable to start WebLogic Server !!
Improperly formatted license file: D:\license.bea
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Is "weblogic.system.home" still valid ? If not, what is the new way of doing
this?
Thanks, Alexandre.

Re: Disable HTTP access to Weblogic 6.0

Appears to be: http://e-docs.bea.com/wls/docs60///////config_xml/properties.html
On 20 Jul 2001 08:35:38 -0800, "Florian Kirchhoff" <[email protected]> wrote:
>
Is this possible in Weblogic 6.0?
"Don Dwoske" <[email protected]> wrote:
It looks like you've got a couple of different things going on
here.
If you want to disable http, do this in the WL properties file:
weblogic.httpd.enable=false
your getInitialContext should figure out what port your naming
service is on unless you've hardcoded it to be localhost:80, true?
I switch between ports 80 and 7001 all the time without problems.
-Don
"Gagan Bhalla" <[email protected]> wrote:
Hi,
Can someone tell me how do I disable the HTTP access to
Weblogic.
The environment I am running on my dev machine would be
Win2000+
Weblogic 5.1+ SP6. I am redirecting any HTTP request to
the secure
port and that part is working. But I want to be able to
completely
disable any HTTP requests all together. Is there a way
to do this.
In the weblogic.properties file, if I change the weblogic.system.listenPort
property to point to anything other than port 80, it gives
me errors
on the WLInitialContext. What else do I need to change
in this
so that I can listen on a port other than 80?
Thanks for your help,
Gagan
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: No server found at T3://localhost:80
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java,
Compiled Code)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java,
Compiled Code)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java,
Compiled Code)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:148)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)

I Need to keep HTTP session alive.
But i need to block trace method or say get method.
Any clue how can we do that.
thanks

How to deploy a session bean in Weblogic 9.2

Hi,
Can anyone please point me to the procedure of deploying session bean on weblogic 9.2. My operating system is Fedora 5. Please let me know the steps as i am very new to EJB.
Regards,
Sanjeev

I looked for this information in ServletConfig, in ServletContext, in JVMID
ServletConfig or ServletContext do not have anything (at least I do not see anything),
The newsgroups recommend the following code
public static String getLocalUrlString()
String urlString;
JVMID jvmid = JVMID.localID();
urlString = jvmid.getHostAddress();
weblogic.rjvm.Protocol proto
=weblogic.rjvm.Protocol.getDefaultProtocol();
int port = jvmid.getPort(proto);
return urlString + ISoapConstants.SCHEME_DELIMITER + port;
I also tried
weblogic.rjvm.Protocol does not exist in current version, and I did not get any real information inside JVMID
Also tried JVMID.localID().ports(), which returns null
System.getProperty("weblogic.system.bindAddr"); or weblogic.system.listenPort property,
getProperty returns null
Tried also another approach from the newsgroups - JwsContext.
/** @common:context */
JwsContext context;
String myPort = context.getService().getURL().getPort();
String myUrl = context.getService().getURL().toString();
context is null
None of them worked.
Do you have any other ideas?
All those ideas I found in the newsgroups were to the previos version(s) of weblogic - up to 8.1. I have not found anything specific to 9.2

Can I change JNDI port number?

Does anyone know where to change JNDI port number.
Currently, (it seems) relies on weblogic.system.listenPort property
which is the same for HTTP and JNDI. We would like to use separate ports for
HTTP and JNDI server.
Thank you
-Mik

In article <39fb0341$[email protected]>, [email protected] says...
Does anyone know where to change JNDI port number.
Currently, (it seems) relies on weblogic.system.listenPort property
which is the same for HTTP and JNDI. We would like to use separate ports for
HTTP and JNDI server.
Thank you
-Mik
You don't. WebLogic is a "complete services" application server which
means it is listening at its 'listenPort' for all service requests. I'd
love for the ability to split off ports, and this may be the case in
6.0. In <6.0, however, you're stuck with two ports: the SSL port and
the normal port.
Jesse

Weblogic.system.AdminListenPort

Friends,
Can anyone tell me about the weblogic.system.AdminListenPort property?
It is referred to in the admin console for WLS 5.1 but I cannot find any
info about the property at
http://www.weblogic.com/docs51/resources.html. Even a website search
turned up nothing.
I am hoping to be able to use it to cause my server to accept console t3
connections on the adminListenPort and reject them on port 80. port 80
is outside the firewall and I do not want joe blow to be trying to point
a console at our server.
- Kevin

It is not a publicly available port and the fact that it is mentioned in the
console is a defect. We are planning to officially add such functionality
in the future. Though, if you want to use it today, you can specify a
separate port for administration and functionality using the property in
your properties file. However, since it is not a official feature,
technical support will likely not be able to help you if there are problems.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Kevin McEntee" <[email protected]> wrote in message
news:[email protected]..
Friends,
Can anyone tell me about the weblogic.system.AdminListenPort property?
It is referred to in the admin console for WLS 5.1 but I cannot find any
info about the property at
http://www.weblogic.com/docs51/resources.html. Even a website search
turned up nothing.
I am hoping to be able to use it to cause my server to accept console t3
connections on the adminListenPort and reject them on port 80. port 80
is outside the firewall and I do not want joe blow to be trying to point
a console at our server.
- Kevin

Weblogic.system.DNSName

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is there any way to get WLS 5.1 (without clustering) to honor the
weblogic.system.DNSName property? I don't want to enable http tunneling
since: it's slow and I don't need http in any case.
My situation is this. I'd like to use a virtual IP on a BigIP (F5) load
balancer which sits between the WL clients and the WL servers. The home
interface the servers send back to the client however, seems to contain the
WLS real IP address (the weblogic.system.bindAddr). When the client
reconnects to the server the stub uses this address instead of the virtual
ip address which it needs to use.
weblogic.system.DNSName is documented
http://search.bea.com/weblogic/go50/query.html?col=weblogic&qp=url%3Ahttp%3A
%2F%2Fwww.weblogic.com%2Fdocs51%2F&qt=weblogic.system.DNSName&qs=&qc=&pw=100
%25&ws=0&qm=0&st=1&nh=10&lk=1&rf=0&rq=0
to do exactly what I wish. However, it seems that this is only supported
when running a cluster. I don't have a need for clusters since all requests
are stateless. I'm only interested in gaining better load balancing
support.
Thanks,
Bryan Talbot
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.2
iQA/AwUBOiMogUzuKKcxAa+OEQI5CwCeMa4AkMUBFJhXlbMfeCyB7RoD4iQAniV0
hbesDuOZlPj6PIG4gl5XiBag
=AtM+
-----END PGP SIGNATURE-----

Yes, many people are running in this configuration (and support should NOT
          have told you this).
          In your scenario, A and B should be the "external IP addresses" of the
          firewall that are exposed to the web servers (the firewall would be
          configured to map requests to A and B to the "internal IP addresses of the
          servers where WLS is running). You still need to set the
          weblogic.system.DNSName parameter on one weblogic server to A and on the
          other server to B so that the session IDs are generated with A and B
          encoded in them rather than the "internal IPs" of the machines where
          weblogic is running.
          Hope this helps,
          Robert
          Arunanand Addepalli wrote:
          > Has anyone successfully implemented weblogic (510SP8) clustering thru
          > DMZ, where the webservers are in DMZ (we are using NAT) and weblogic
          > servers are in the local network. Using Solaris 2.7 and NES as
          > webservers. The problem i am facing is that when i am defining the DNS
          > names as "A:7001,B:7001" in the obj.conf where A and B are teh DNS
          > names of the weblogic servers. i also defined weblogic.system.DNSName
          > parameter.
          >
          > Six months back i logged this call at bea support and they closed the
          > call suggesting me to push my weblogic servers in to the DMZ.
          >
          > If somebody can help, thanks in advance.
          >
          > Regards
          > Arun

Error in starting weblogic commerce server on Win2000

I downloaded the evaluation release of Weblogic Commerce 3.1 and th licence,
and installed it on Windows 2000 Professional,
I have a Weblogic Application Server 5.1 installed
the server did not start and gave an error, please help us as to what the
problem is and how to get it running.
=========== Error Message ===============
JAVA_CLASSPATH IS
C:\jdk\lib\tools.jar;C:\weblogic\lib\weblogic510sp6boot.jar;C:
\weblogic\classes\boot
WEBLOGIC_CLASSPATH IS
C:\weblogic\lib\weblogic510sp6.jar;C:\weblogic\lib\WebLogi
c_RDBMS.jar;C:\weblogic\license;C:\weblogic\classes;C:\weblogic\lib\weblogic
aux.
jar;C:\weblogic\lib\weblogic-tags-510.jar;C:\WebLogicCommerceServer3.1\licen
se;C
:\WebLogicCommerceServer3.1\classes;C:\WebLogicCommerceServer3.1\lib\rules.j
ar;C
:\WebLogicCommerceServer3.1\lib\jrulesserviceprovider.jar;C:\WebLogicCommerc
eSer
ver3.1\deploy\bmp\classes;C:\WebLogicCommerceServer3.1\eval\win32\Taxware\cl
asse
s;C:\weblogic\eval\cloudscape\lib\cloudscape.jar;C:\weblogic\eval\cloudscape
\lib
\tools.jar;C:\weblogic\eval\cloudscape\lib\client.jar
Fri Dec 01 11:04:39 GMT+05:30 2000: <WebLogicServer> Read global
properties C:\WebLogicCommerceServer3.1\weblogic.propertie
Fri Dec 01 11:04:39 GMT+05:30 2000: <WebLogicServer> No per-server
properties files found
Fri Dec 01 11:04:39 GMT+05:30 2000: <Logging> FileLogger initialized.
Fri Dec 01 11:04:39 GMT+05:30 2000: <WebLogicServer> ************
WebLogic Server (5.1.0 04/03/2000 17:13:23 #66825) 'serve
:\WebLogicCommerceServer3.1
Fri Dec 01 11:04:39 GMT+05:30 2000: <WebLogicServer> ************ (c)
1995, 1996, 1997, 1998 WebLogic, Inc., (c) 1999 BEA S
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.swapIntervalSecs', current value: '10'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.ConnectionConsumer', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.enforceClientCert', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.login.readTimeoutMillis', current value: '5000'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.propertiesFile', current value: 'C:\WebLogicCo
.properties'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.bindAddr', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.servlet.reloadCheckSecs', current value: '-1'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.authRealmName', current value: 'WebLogic Server
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.SSLHandler.enable', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.startupFailureIsFatal', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.http.keepAliveSecs', current value: '60'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.servlet.classpath', current value: ''
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.tunneling.clientPingSecs', current value: '45'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.defaultWebApp', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.persistentStoreDir', current value: 'se
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.perServerPropertiesFile', current value: 'null
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.queue', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.invalidationIntervalSecs', current valu
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.persistence', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.cache.user.enable', current value: 'tr
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.rmi.dgc.callSystemGC', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.enableEvents', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.maxTransactedDurableSubscribers', current value:
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.weight', current value: '100'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.connectionPoolArgs', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.disableGuest', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.persistentStorePool', current value: ''
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.URLAclFile', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.percentSocketReaders', current value: '33'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.zac.enable', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jdbc.TXDataSource', current value: '[weblogic.jdbc.TX
.jts.commercePool=commercePool ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.DNSName', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.ejb.deploy', current value: 'C:/WebLogicCommerceServe
C:/WebLogicCommerceServer3.1/lib/axiom.jar,C:/WebLogicCommerceServer3.1/lib/
ebusiness.jar,C:/WebLogicCommerceServer3.1/lib/adv
erceServer3.1/lib/bridge.jar,C:/WebLogicCommerceServer3.1/lib/document.jar,C
:/WebLogicCommerceServer3.1/lib/p13nadvisor.jar,C:
.1/lib/portal.jar,C:/WebLogicCommerceServer3.1/lib/ruleeditorbeans.jar,C:/We
bLogicCommerceServer3.1/lib/rulesservice.jar,C:/We
lib/servicemgr.jar'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.workspace.showUserKeysOnly', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.enable', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.allow', current value: '[weblogic.allow.reserve.weblo
commercePool=everyone
weblogic.allow.execute.weblogic.servlet.Certificate=system
weblogic.allow.execute.weblogic.servlet.Admin
low.execute.weblogic.servlet.AdminLicense=system
weblogic.allow.execute.weblogic.servlet.AdminConnections=system
weblogic.allo
et.classes=everyone
weblogic.allow.execute.weblogic.servlet.AdminClients=system
weblogic.allow.execute.weblogic.servlet.AdminV
llow.execute.weblogic.servlet.AdminMain=system
weblogic.allow.execute.weblogic.servlet.AdminThreads=system
weblogic.allow.rese
tionPool.docPool=everyone weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.execute.weblogic.servlet.AdminEvents=
ite.weblogic.workspace=everyone
weblogic.allow.execute.weblogic.servlet.AdminJDBC=system
weblogic.allow.execute.weblogic.servl
ow.execute.weblogic.servlet.AdminProps=system
weblogic.allow.execute.weblogic.servlet.ConsoleHelp=everyone ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.listenPort', current value: '7501'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.allow', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.servlet.reloadOnModify', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.io.fileSystem', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.startupArgs', current value: '[weblogic.system
p=TraceFlags=E ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jdbc.enableLogFile', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cookie.domain', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.debug', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.clustering.enable', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.enable', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.shutdownArgs', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.rmi.startupClass', current value: '[weblogic.rmi.star
blogic.rmi.internal.RegistryImpl ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.keepAlive.enable', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.jdbc.connTimeoutSecs', current value: '
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.name', current value: 'server'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.helpPageURL', current value: 'http://www.weblo
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.key.server', current value: 'C:\WebLogicComm
okey.pem'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.rmi.startupArgs', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.topicSessionPool', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.logFileBufferKBytes', current value: '8'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.home', current value: 'C:\weblogic'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.documentRoot', current value: 'public_html'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.servlet.reloadOnModifyRecursive', current value
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.errorPage', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.certificate.authority3', current value: 'nul
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.administrativePort', current value: '0'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.certificate.authority2', current value: 'nul
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.startupClass', current value: '[weblogic.syste
tup=com.beasys.commerce.foundation.plugin.weblogic.TraceStartup
weblogic.system.startupClass.KeyBootstrap=com.beasys.commerce.
otstrap
weblogic.system.startupClass.serviceManager=com.beasys.commerce.servicemanag
er.CommerceServiceManagerStartup ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.nonPrivGroup', current value: 'nobody'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.cluster.multicastTTL', current value: '1'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.home', current value: 'C:\WebLogicCommerceServ
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.https.keepAliveSecs', current value: '120'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jndi.transportableObjectFactories', current value: ''
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.certificateCacheSize', current value: '3'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.tunneling.clientTimeoutSecs', current value: '4
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jdbc.DataSource', current value: '[weblogic.jdbc.Data
l.docPool=docPool ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.nonPrivUser', current value: 'nobody'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.zac.publishRoot', current value: 'exports'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.clientRootCA', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.cluster.defaultLoadAlgorithm', current value: 'round-
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.enable', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.administrator.phone', current value: '(None)'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jdbc.connectionPool', current value: '[weblogic.jdbc.
rl=jdbc:beasys:docmgmt:com.beasys.commerce.axiom.document.ref.RefDocumentPro
vider,driver=com.beasys.commerce.axiom.document.jd
=0,initialCapacity=10,maxCapacity=20,capacityIncrement=1,allowShrinking=true
,shrinkPeriodMins=15,refreshMinutes=5,props=jdbc.u
mmercePool;jdbc.isPooled=true;weblogic.t3.waitForConnection=true;weblogic.t3
.waitSecondsForConnection=999999999999;weblogic.jt
onSecs=999999999999;docBase=C:/WebLogicCommerceServer3.1/dmsBase;schemaXML=C
:/WebLogicCommerceServer3.1/dmsBase/doc-schema.xml
nPool.commercePool=url=jdbc:cloudscape:Commerce;create=true;upgrade=true,dri
ver=COM.cloudscape.core.JDBCDriver,loginDelaySecs=
Capacity=20,capacityIncrement=1,allowShrinking=true,shrinkPeriodMins=15,test
ConnsOnReserve=true,testTable=WLCS_IS_ALIVE,refres
ne;password=none;server=none;weblogic.t3.waitForConnection=true;weblogic.t3.
waitSecondsForConnection=999999999999,weblogic.jts
nSecs=999999999999,verbose=false ]'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.debug', current value: 'false'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.jdbc.logFileName', current value: 'C:\WebLogicCommerc
og'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.cluster.dnsName', current value: 'null'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.requireAuthentication', current value: 'true'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.cluster.multicastAddress', current value: ''
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.defaultSecureProtocol', current value: 't3s'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.cache.auth.enable', current value: 'tr
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.system.executeThreadCount', current value: '15'
Fri Dec 01 11:04:39 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cookie.comment', current value: 'Weblog
ng Cookie'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.tableNamePrefix', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.connectionPool', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.shutdownClass', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.defaultServlet', current value: 'file'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.cluster.name', current value: 'mycluster'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.defaultProtocol', current value: 't3'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.postTimeoutSecs', current value: '30'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.group', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.cache.caseSensitive', current value: '
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.certificate.server', current value: 'C:\WebL
rver\democert.pem'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.mimeType', current value: '[weblogic.httpd.mime
.wmlscriptc=wmlsc weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.image/gif=gif weblogic.httpd.mim
stream=exe weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.application/pdf=pdf weblogic.httpd.mimeType.appl
ar weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
weblogic.httpd.mimeType.applica
tpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.application/vnd.
ttpd.mimeType.application/x-java-serialized-object=ser ]'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.webApp', current value: '[weblogic.httpd.webApp
rceServer3.1/server/webapps/examples/portal/portal.war
weblogic.httpd.webApp.tools=C:/WebLogicCommerceServer3.1/server/webapps
c.httpd.webApp.wlcs=C:/WebLogicCommerceServer3.1/server/webapps/wlcs/ ]'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.minPasswordLen', current value: '8'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.connectionFactoryArgs', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.persistentStoreType', current value: 'f
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cacheEntries', current value: '1024'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.certificate.authority', current value: 'C:\W
\server\ca.pem'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.resource.MailSession', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cookie.maxAgeSecs', current value: '-1'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.login.readTimeoutMillisSSL', current value: '25000'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.cluster.enable', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.SSL.ciphersuites', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.indexFiles', current value: 'index.html,index.h
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.password', current value: '[weblogic.password.system=
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.enableLogFile', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.enableReverseDNSLookups', current value: 'fals
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.indexDirectories', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.maxLogFileSize', current value: '1024'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.logFile', current value: 'C:\WebLogicCommerceS
.log'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.timeoutSecs', current value: '3600'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.logFileFormat', current value: 'common'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.perClusterPropertiesFile', current value: 'nul
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.key.export.lifespan', current value: '500'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.CORBA.connectionPool', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'java.system.property', current value: '[java.system.property.c
/WebLogicCommerceServer3.1/db/data ]'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.logFileName', current value: 'C:\WebLogicCommer
s.log'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.defaultMimeType', current value: 'text/plain'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.debug.httpd.servlet', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.connectionFactoryName', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.SSLListenPort', current value: '7502'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.URLResource', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cookie.name', current value: 'WebLogicS
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.quiescent', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.register', current value: '[weblogic.httpd.regi
sys.commerce.foundation.flow.FlowManager
weblogic.httpd.register.AdminProps=admin.AdminProps
weblogic.httpd.register.classes=w
hServlet weblogic.httpd.register.AdminEvents=admin.AdminEvents
weblogic.httpd.register.AdminMain=admin.AdminMain weblogic.http
gic.servlet.ServerSideIncludeServlet
weblogic.httpd.register.servletimages=weblogic.servlet.internal.InternalImag
eServlet webl
oleHelp=weblogic.servlet.ClasspathServlet
weblogic.httpd.register.AdminJDBC=admin.AdminJDBC
weblogic.httpd.register.ShowDocSer
.content.ShowDocServlet
weblogic.httpd.register.*.jsp=weblogic.servlet.JSPServlet
weblogic.httpd.register.AdminCaptureRootCA=a
weblogic.httpd.register.AdminRealm=admin.AdminRealm
weblogic.httpd.register.AdminLicense=admin.AdminLicense weblogic.httpd.reg
certificate weblogic.httpd.register.AdminConnections=admin.AdminConnections
weblogic.httpd.register.AdminClients=admin.AdminCl
ister.file=weblogic.servlet.FileServlet
weblogic.httpd.register.AdminVersion=admin.AdminVersion
weblogic.httpd.register.authen
.ClientAuthenticationServlet
weblogic.httpd.register.AdminThreads=admin.AdminThreads ]'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.clientRootCA4', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.clientRootCA3', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.clientRootCA2', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cookies.enable', current value: 'true'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.servlet.extensionCaseSensitive', current value:
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.cache.group.enable', current value: 't
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.nativeIO.enable', current value: 'true'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.rmi.enableServerSideStubs', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.cookie.path', current value: '/'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.session.URLRewriting.enable', current value: 't
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.enableSetUID', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.cache.acl.enable', current value: 'tru
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.topic', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.administrator.name', current value: 'WebLogic Adminis
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.jms.queueSessionPool', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.ssl.enable', current value: 'true'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.administrator.location', current value: '(None)'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.enableSetGID', current value: 'false'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.initArgs', current value: '[weblogic.httpd.init
Filename=/weblogic/admin/help/NoContent.html
weblogic.httpd.initArgs.*.jsp=pageCheckSeconds=0,packagePrefix=jsp,compileCo
mmand
gDir=C:/WebLogicCommerceServer3.1/server/classfiles,verbose=false,keepgenera
ted=false weblogic.httpd.initArgs.file=defaultFile
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.administrator.email', current value: 'root'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.enableConsole', current value: 'true'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.security.realm.cache.perm.enable', current value: 'tr
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.system.user', current value: 'system'
Fri Dec 01 11:04:40 GMT+05:30 2000: <Config> Property name:
'weblogic.httpd.charsets', current value: 'null'
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> awt.toolkit =
sun.awt.windows.WToolkit
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> cloudscape.system.home
= C:/WebLogicCommerceServer3.1/db/data
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> commerce.properties =
C:\WebLogicCommerceServer3.1\weblogiccommerce.prop
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> file.encoding = Cp1252
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> file.encoding.pkg =
sun.io
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> file.separator = \
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.awt.fonts =
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.awt.graphicsenv =
sun.awt.Win32GraphicsEnvironment
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.awt.printerjob =
sun.awt.windows.WPrinterJob
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.class.path =
C:\jdk\lib\tools.jar;C:\weblogic\lib\weblogic510sp6boo
s\boot
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.class.version =
46.0
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.compiler =
symcjit
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.ext.dirs =
C:\jdk\jre\lib\ext
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.home = C:\jdk\jre
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.io.tmpdir =
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.library.path =
C:\jdk\bin;.;C:\WINNT\System32;C:\WINNT;C:\WINNT\sys
System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;C:\Program
Files\Microsoft Visual Studio\Common\MSDev98\Bin;
ft Visual Studio\Common\Tools;C:\Program Files\Microsoft Visual
Studio\VC98\bin;C:\jdk\bin;C:\weblogic\bin;C:\weblogic\bin;C:\
1\eval\win32\CyberCash\bin;C:\WebLogicCommerceServer3.1\eval\win32\Taxware\b
in
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.protocol.handler.pkgs = weblogic.utils|weblogic.utils
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.security.manager
=
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.security.policy =
C:\weblogic\weblogic.policy
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.specification.name = Java Platform API Specification
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.specification.vendor = Sun Microsystems Inc.
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.specification.version = 1.2
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vendor = Sun
Microsystems Inc.
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vendor.url =
http://java.sun.com/
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vendor.url.bug =
http://java.sun.com/cgi-bin/bugreport.cgi
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.version = 1.2.2
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vm.info = build
JDK-1.2.2-001, native threads, symcjit
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vm.name = Classic
VM
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.vm.specification.name = Java Virtual Machine Specification
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.vm.specification.vendor = Sun Microsystems Inc.
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
java.vm.specification.version = 1.0
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vm.vendor = Sun
Microsystems Inc.
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> java.vm.version =
1.2.2
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> line.separator =
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> os.arch = x86
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> os.name = Windows NT
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> os.version = 5.0
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> path.separator = ;
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> pipeline.properties =
C:\WebLogicCommerceServer3.1\pipeline.properties
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> sun.boot.class.path =
C:\jdk\jre\lib\rt.jar;C:\jdk\jre\lib\i18n.jar;C:\j
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> sun.boot.library.path
= C:\jdk\jre\bin
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props>
sun.io.unicode.encoding = UnicodeLittle
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> user.dir =
C:\WebLogicCommerceServer3.1
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> user.home =
C:\Documents and Settings\Administrator
Fri Dec 01 11:04:40 GMT+05:30 2000: <System Props> user.language = en
Fri Dec 01 11:04:40 GMT+05:30 2

Hello Muffy,
It looks like you do not have WLS 5.1 service pack 6 installed correctly. I
say this because I do not see the sp6 message at the top of your log and I saw
this message in your log:
org.xml.sax.SAXParseException: Element "weblogic-enterprise-bean" allows no
further input; "transaction-isolation" is not allowed
Ture Hoefner
BEA Systems, Inc.
2590 Pearl St.
Suite 110
Boulder, CO 80302
www.bea.com

How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?

Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception

Dear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r

Weblogic as web server

Is there any hints to get Weblogic up & running on port 80 as a web server?
We have IIS working fine, but this is a development box that just needs to
be viewed & doesn't need IIS. We're not using servlets either. Instead of
pointing my client to http://www.abc.com:7001/index.jsp , I'd like to point
them to http://www.abc.com/index.jsp & have them see the same thing.
Are there a few commands that I need to put in the weblogic.properties file?

change the following property in your weblogic.properties file.
weblogic.system.listenPort=80
Kumar
Mike Kendzierski wrote:
Is there any hints to get Weblogic up & running on port 80 as a web server?
We have IIS working fine, but this is a development box that just needs to
be viewed & doesn't need IIS. We're not using servlets either. Instead of
pointing my client to http://www.abc.com:7001/index.jsp , I'd like to point
them to http://www.abc.com/index.jsp & have them see the same thing.
Are there a few commands that I need to put in the weblogic.properties file?[att1.html]

How to monitor WebLogic Server when enable the Administration Port

It works fine when use Listenport 7001, but when enable the Administration Port(9002), it does not work.
Maybe I should do something to set the system environment property, but how?
help~
Sorry for my poor English~
Thanks~

HI,
If the admin port is enabled then you have to use these parameters to run any scripts
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=DemoTrust
-The you can use Admin URL: t3s://localhost:9002 with Admin Port and Secure Protocol.
Example:
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST application_status.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Connecting to t3s://localhost:9002 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'Domain_7001'.
.Regards,
Ravish Mody
http://middlewaremagic.com/weblogic
Come, Join Us and Experience The Magic…

Starting WebLogic server from concole

When I start WebLogic server using startweblogic.cmd everything seems to be okay.
Using the 'Start a new WebLogic server or cluster' command from WebLogic Console
5.1.0, I get the following error message:
Attempting to start server on the machine running the console using
C:\weblogic\jre1_2\jre\bin\java.exe -mx32m -ms32m -classpath "C:\weblogic\jre1_2\jre\lib\rt.jar;C:\weblogic\jre1_2\jre\lib\i18n.jar;C:\weblogic\lib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib\cloudscape.jar"
-Dweblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib\weblogicaux.jar
-Dweblogic.system.discardOutAndErr=true -Djava.security.manager -Djava.security.policy==C:\weblogic\weblogic.policy
-Dweblogic.system.name=kenapp00111 -Dweblogic.system.home=C:\weblogic -Dweblogic.cluster.enable=false
-Dweblogic.cluster.name=mycluster -Dweblogic.system.listenPort=7001 -Dweblogic.system.SSLListenPort=7002
-Dweblogic.cluster.multicastAddress=237.0.0.1 weblogic.Server
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Loaded License : C:/weblogic/license/WebLogicLicense.xml
However Unable to start because :
No License found for WebLogic
As well as the fact that: No License found for Tengah
As well as the fact that: No License found for WebLogic/JDBC
As well as the fact that: No License found for Tengah/JDBC
As well as the fact that: No License found for jdbcKona/T3
Is the 'server name' the name of the machine or 'myserver' ? Could there really
be something wrong with the licence file ?
Thanks for helping !
Hilmar

1. "myserver" is the name of the server. It doesn't want the name of the
machine the server is on.
2. It is possible that something is wrong in the license file. I've made a
typo when changing the license on my server that prevented weblogic from
starting.
Hope this helps.
"Hilmar" <[email protected]> wrote in message
news:[email protected]..
>
When I start WebLogic server using startweblogic.cmd everything seems tobe okay.
Using the 'Start a new WebLogic server or cluster' command from WebLogicConsole
5.1.0, I get the following error message:
Attempting to start server on the machine running the console using
C:\weblogic\jre1_2\jre\bin\java.exe -mx32m -ms32m -classpath"C:\weblogic\jre1_2\jre\lib\rt.jar;C:\weblogic\jre1_2\jre\lib\i18n.jar;C:\we
blogic\lib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib
\cloudscape.jar"
-Dweblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib\weblogicaux.jar
-Dweblogic.system.discardOutAndErr=true -Djava.security.manager -Djava.security.policy==C:\weblogic\weblogic.policy
-Dweblogic.system.name=kenapp00111 -Dweblogic.system.home=C:\weblogic -Dweblogic.cluster.enable=false
-Dweblogic.cluster.name=mycluster -Dweblogic.system.listenPort=7001 -Dweblogic.system.SSLListenPort=7002
-Dweblogic.cluster.multicastAddress=237.0.0.1 weblogic.Server
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Loaded License : C:/weblogic/license/WebLogicLicense.xml
However Unable to start because :
No License found for WebLogic
As well as the fact that: No License found for Tengah
As well as the fact that: No License found for WebLogic/JDBC
As well as the fact that: No License found for Tengah/JDBC
As well as the fact that: No License found for jdbcKona/T3
Is the 'server name' the name of the machine or 'myserver' ? Could therereally
be something wrong with the licence file ?
Thanks for helping !
Hilmar

Starting Weblogic Server Cluster remotely via VPN

We have a site-to-site VPN setup from our office to our ISP so we can
 control our system remotely. We can stop our Weblogic servers (in a
 cluster) remotely via the VPN no problem via the "stopweblogic.cmd" command
 where we just change the IP address of our remote server. We're having
 trouble starting them through the WebLogic console applet. We can bring the
 applet up & running, but no luck starting them.
 Is there another way to start your weblogic servers (besides using something
 like PC Anywhere).
 Or is there any documentation that could point to an answer here?
 Any suggestions?
 Mike Kendzierski
 B2BGalaxy.com


1. "myserver" is the name of the server. It doesn't want the name of the
machine the server is on.
2. It is possible that something is wrong in the license file. I've made a
typo when changing the license on my server that prevented weblogic from
starting.
Hope this helps.
"Hilmar" <[email protected]> wrote in message
news:[email protected]..
>
When I start WebLogic server using startweblogic.cmd everything seems tobe okay.
Using the 'Start a new WebLogic server or cluster' command from WebLogicConsole
5.1.0, I get the following error message:
Attempting to start server on the machine running the console using
C:\weblogic\jre1_2\jre\bin\java.exe -mx32m -ms32m -classpath"C:\weblogic\jre1_2\jre\lib\rt.jar;C:\weblogic\jre1_2\jre\lib\i18n.jar;C:\we
blogic\lib\i18n.jar;C:\weblogic\classes\boot;C:\weblogic\eval\cloudscape\lib
\cloudscape.jar"
-Dweblogic.class.path=C:\weblogic\license;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib\weblogicaux.jar
-Dweblogic.system.discardOutAndErr=true -Djava.security.manager -Djava.security.policy==C:\weblogic\weblogic.policy
-Dweblogic.system.name=kenapp00111 -Dweblogic.system.home=C:\weblogic -Dweblogic.cluster.enable=false
-Dweblogic.cluster.name=mycluster -Dweblogic.system.listenPort=7001 -Dweblogic.system.SSLListenPort=7002
-Dweblogic.cluster.multicastAddress=237.0.0.1 weblogic.Server
$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
Loaded License : C:/weblogic/license/WebLogicLicense.xml
However Unable to start because :
No License found for WebLogic
As well as the fact that: No License found for Tengah
As well as the fact that: No License found for WebLogic/JDBC
As well as the fact that: No License found for Tengah/JDBC
As well as the fact that: No License found for jdbcKona/T3
Is the 'server name' the name of the machine or 'myserver' ? Could therereally
be something wrong with the licence file ?
Thanks for helping !
Hilmar

Weblogic.system.listenPort property in Weblogic 6.0?

Similar Messages

Maybe you are looking for