On 11 February 2011 Oracle released version 6 of there unbreakable linux distribution which is based upon RedHat Enterprise Linux.
Dowload: https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=13443339
Documentation: https://linux.oracle.com/documentation/
Personally I get shivers down my spine, when I have to start a server process with nohup and pipe the output to a separate log, I refer to the startWeblogic.sh / bat script supplied by Oracle on a Weblogic installation. By a lot of weblogic implementation by Oracle you still have to start weblogic this way, OBIEE 11g for example. Well Weblogic has something nice, called WLST or WebLogic Scripting Tool. This is a Jython based interface to your Weblogic environment. Jython is en scripting language based on Python, but specially for Java.
For starting an OBIEE 11g (Oracle Business Intelligence Enterprise Edition) environment I wrote the following script, to boot the weblogic parts of OBI. This can by used on every platform.
StartServers.py example:
import os
if os.environ.has_key('wlsAdminServer'):
wlsAdminServer = os.environ['wlsAdminServer']
if os.environ.has_key('nmUserID'):
nmUserID = os.environ['nmUserID']
if os.environ.has_key('wlsUserID'):
wlsUserID = os.environ['wlsUserID']
if os.environ.has_key('wlsPassword'):
wlsPassword = os.environ['wlsPassword']
if os.environ.has_key('wlsAdminURL'):
wlsAdminURL = os.environ['wlsAdminURL']
if os.environ.has_key('wlsNodeManagerHome'):
wlsNodeManagerHome = os.environ['wlsNodeManagerHome']
if os.environ.has_key('nmPort'):
nmPort = os.environ['nmPort']
if os.environ.has_key('wlsHost'):
wlsHost = os.environ['wlsHost']
if os.environ.has_key('wlsDomainName'):
wlsDomainName = os.environ['wlsDomainName']
if os.environ.has_key('wlsDomainLocation'):
wlsDomainLocation = os.environ['wlsDomainLocation']
print '-- START NODE MANAGER --';
startNodeManager(verbose='true', NodeManagerHome=wlsNodeManagerHome, ListenPort=nmPort, ListenAddress=wlsHost)
print '-- CONNECT TO NODE MANAGER --';
nmConnect(nmUserID, wlsPassword, wlsHost, nmPort, wlsDomainName, wlsDomainLocation, 'ssl')
print '-- START ADMIN SERVER --';
nmStart(wlsAdminServer)
connect(wlsUserID, wlsPassword, url=wlsAdminURL, adminServerName=wlsAdminServer)
domainRuntime()
serverLifeCycles = cmo.getServerLifeCycleRuntimes()
for serverLifeCycle in serverLifeCycles:
if (serverLifeCycle.getState() != 'RUNNING'):
print 'Starting Server: ' + serverLifeCycle.getName()
start(serverLifeCycle.getName(), 'Server')
exit()
I first import some OS variables which I set with an other script, for example I have a bi_env script.
bi_env:
export wlsAdminServer="AdminServer" export nmUserID="nodemanager" export wlsUserID="weblogic" export wlsPassword="" export wlsHost=`hostname` export nmPort="9556" export asPort="7001" export wlsAdminURL="t3://${wlsHost}:${asPort}" export wlsDomainName="bifoundation_domain" export wlsMiddleWareHome="/u00/oracle/product/11.1.1" export wlsDomainLocation="${wlsMiddleWareHome}/user_projects/domains/bifoundation_domain" export wlsNodeManagerHome="${wlsMiddleWareHome}/wlserver_10.3/common/nodemanager"
What you do next is simple, on Linux, but Windows as well, set the environment variables and run the start script. WLST will start all the WLS process in the background as it should be, with the logging in the right place. For example:
./wlserver_10.3/server/bin/setWLSEnv.sh . ~/bi_env java weblogic.WLST StartServers.py
You can also use WLST to stop the processes and check the status, to initiate scripts you can use the above code sample.
StopServers.py:
import os
if os.environ.has_key('wlsAdminServer'):
wlsAdminServer = os.environ['wlsAdminServer']
if os.environ.has_key('nmUserID'):
nmUserID = os.environ['nmUserID']
if os.environ.has_key('wlsUserID'):
wlsUserID = os.environ['wlsUserID']
if os.environ.has_key('wlsPassword'):
wlsPassword = os.environ['wlsPassword']
if os.environ.has_key('wlsAdminURL'):
wlsAdminURL = os.environ['wlsAdminURL']
if os.environ.has_key('wlsNodeManagerHome'):
wlsNodeManagerHome = os.environ['wlsNodeManagerHome']
if os.environ.has_key('nmPort'):
nmPort = os.environ['nmPort']
if os.environ.has_key('wlsHost'):
wlsHost = os.environ['wlsHost']
if os.environ.has_key('wlsDomainName'):
wlsDomainName = os.environ['wlsDomainName']
if os.environ.has_key('wlsDomainLocation'):
wlsDomainLocation = os.environ['wlsDomainLocation']
print '-- CONNECT TO NODE MANAGER AND ADMINSERVER --';
nmConnect(nmUserID, wlsPassword, wlsHost, nmPort, wlsDomainName, wlsDomainLocation, 'ssl')
connect(wlsUserID, wlsPassword, url=wlsAdminURL, adminServerName='AdminServer')
domainRuntime()
serverLifeCycles = cmo.getServerLifeCycleRuntimes()
for serverLifeCycle in serverLifeCycles:
if (serverLifeCycle.getState() == 'RUNNING') and (serverLifeCycle.getName() != wlsAdminServer ):
print 'Stopping Server: ' + serverLifeCycle.getName()
nmKill(serverLifeCycle.getName())
print '-- STOPPING NODE MANAGER --'
stopNodeManager()
exit()
StatusServers.py:
import os
if os.environ.has_key('wlsAdminServer'):
wlsAdminServer = os.environ['wlsAdminServer']
if os.environ.has_key('nmUserID'):
nmUserID = os.environ['nmUserID']
if os.environ.has_key('wlsUserID'):
wlsUserID = os.environ['wlsUserID']
if os.environ.has_key('wlsPassword'):
wlsPassword = os.environ['wlsPassword']
if os.environ.has_key('wlsAdminURL'):
wlsAdminURL = os.environ['wlsAdminURL']
if os.environ.has_key('wlsNodeManagerHome'):
wlsNodeManagerHome = os.environ['wlsNodeManagerHome']
if os.environ.has_key('nmPort'):
nmPort = os.environ['nmPort']
if os.environ.has_key('wlsHost'):
wlsHost = os.environ['wlsHost']
if os.environ.has_key('wlsDomainName'):
wlsDomainName = os.environ['wlsDomainName']
if os.environ.has_key('wlsDomainLocation'):
wlsDomainLocation = os.environ['wlsDomainLocation']
nmConnect(nmUserID, wlsPassword, wlsHost, nmPort, wlsDomainName, wlsDomainLocation, 'ssl')
connect(wlsUserID, wlsPassword, url=wlsAdminURL, adminServerName='AdminServer')
domainRuntime()
serverLifeCycles = cmo.getServerLifeCycleRuntimes();
for serverLifeCycle in serverLifeCycles:
print 'Server: ' + serverLifeCycle.getName() + ', State: ' + serverLifeCycle.getState();
if (serverLifeCycle.getState() == 'RUNNING'):
cd('ServerRuntimes/' + serverLifeCycle.getName());
jvm = cmo.getJVMRuntime();
print 'Java VM Vendor: ' + jvm.getJavaVMVendor();
print 'Heap Free Space: ' + repr(jvm.getHeapFreePercent()) + '%';
print 'Heap Size Current: ' + repr(jvm.getHeapSizeCurrent());
print 'Maximum Heap Size: ' + repr(jvm.getHeapSizeMax());
cd('/');
exit()
One thing you must not forget, is to make a boot.properties file in
Error Starting server AdminServer: weblogic.nodemanager.NMException: Exception while starting server 'AdminServer' wls:/nm/bifoundation_domain> NMProcess:NMProcess: java.io.IOException: Server failed to start up. See server output log for more details. NMProcess: at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331) NMProcess: at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567) NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:116) NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:70) NMProcess: at java.lang.Thread.run(Thread.java:619) NMProcess: NMProcess: Feb 10, 2011 4:56:27 PM weblogic.nodemanager.server.Handler handleStart NMProcess: WARNING: Exception while starting server 'AdminServer' NMProcess: java.io.IOException: Server failed to start up. See server output log for more details. NMProcess: at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331) NMProcess: at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567) NMProcess: at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:116) NMProcess: at weblogic.nodemanager.server.Handler.run(Handler.java:70) NMProcess: at java.lang.Thread.run(Thread.java:619)
You boot.properties should look something like:
#Thu Feb 10 17:10:34 CET 2011 password=password username=weblogic
This file will be encrypted on first use.
In the past few years as Oracle Administrator I’ve managed several types of application server, from single instance to clustered environments and from open source to proprietary software. And since the acquisition of BEA and Sun by Oracle, the choice of the right application server isn’t made it easier.
All the varieties of the J2EE application servers are available; on the moment I write this, those are:
I included Glassfish 3.1 because I was quite positively surprised by the manageability of the server in comparison with version 3.0.
So, the question is simple, which one do I choose. Well the answer is also simple: Choose the one that suits you best! But what are the differences between the application servers, besides the price. What do you expect from an application server?
To answer those questions is simple, if you only look at the basics, namely JDK support, availability, clustering and manageability. To answer those, the following matrix applies:
| JDK | Clustering | Availability | Manageability | |
| OAS 10.1.3.x | 1.4 | Yes | fail-over | Opmn / emctl |
| Weblogic 10.3.x | 1.6 | Yes | fail-over | WLST |
| Glassfish 2.1.x | 1.5 | Yes | No* | asadmin |
| Glassfish 3.0.x | 1.6 | No | No | asadmin |
| Glassfish 3.1.x | 1.6 | Yes | No* | asadmin |
(*: Note that failover is possible for Glassfish through a load balancer, for both Weblogic and OAS failover is done in the application server.
To be ready for the future and you want the most scalable and manageable J2EE server, I would choose for Weblogic server. Although the OAS is still available, Oracle is quite clear about it’s strategy, Weblogic is the infrastructure of choice for their products.
But what about Glassfish? Well Glassfish 2.1.x only supports the J2EE 5.0 stack, it can be upgraded to 6.0, but that only improves performance. Glassfish 3.0 can only run in a single instance and Glassfish 3.1 is not ready yet. And in my opinion, Glassfish will always be the little brother of Weblogic and will never reach the Enterprise class that Weblogic is on.
Another thing you might want to consider is manageability. All three kind of J2EE server have there own tooling supplied. OAS has EMCTL and OPMN, Weblogic has the WLST and Glassfish has asadmin. All three have a web-based management tool.
But the OAS tooling is quite passive in comparison with asadmin. But WLST is more powerful then asadmin. Note that opmn and emctl are also supplied with Weblogic, but I think you should use WLST, since that gives you a better idea of what is running and the log is put in the right place by default. Opmn is supplied for backwards compatibility I think, so the transaction between OAS and Weblogic is made simple.
Next you should consider scalability. You can add extra OC4J instances to an OC4J group, but that is not as easy as with Weblogic or Glassfish. With both Weblogic and Glassfish you can add quite simply extra instance with little to no impact on your environment. Another thing that falls under scalability is choice of JDK. For all three products you’re free on which JDK you use, next to the limitations. But only with Weblogic you can use multiple JDK’s in one J2EE domain, which makes Weblogic very flexible as a platform for hosting J2EE applications.
Conclusion, I must say, I’m quite pro Weblogic. But the best choice is done, by looking at all the factors and price is a big one. If cost weren’t an issue, I would choose Weblogic. As mentioned earlier, Weblogic is scalable, flexible and very well manageable with a very powerful scripting tool. If cost were an issue, I’ll choose Glassfish 2.1.x or wait for a while and choose Glassfish 3.1. Both are a very good and cheap alternative to Weblogic, the basic architecture is similar and Glassfish is very scalable. Another thing you must not forget is what type of application and how many there are going to run on the environment. If it is a simple web fronted J2EE application and it is going to be the only one, the best choice is Glassfish. If it’s the other way around and the applications rely on a secure identity management, the best choice is Weblogic.
As you can see, Oracle supplies a J2EE server for all kinds of markets. From free open source to high-end enterprise. The question is: Which one best suites your needs.
Powered by FireStats