Я видимо последний кто об этом услышал (хотя в рунете по этому поводу тишина). А суть в том что Oracle разрабатывает проект который исплючит операционную систему из требований по запуску Java. Назваться будет это JRockit Virtual Edition (VE). В этом можно видеть реализацию старой мечты Sun, что JVM (Java Virtual Machine) была сама полноценной виртуально машиной, которой бы не требовалась хост-ОС. Ну судя по всему в ближайшем времени мы сможем увидеть этот продукт, он будет входить в популярный Application Server – Weblogic Server Virtual Edition.
Напомню что такое JRockit – это проприетарная реализация Java Virtual Machine, разработанная Appeal Virtual Machines (BEA), а затем сначала перешла к BEA Systems (в 2002), а потом и Oracle (в 2008). Но с учетом того что BEA Systems это всего лишь подразделение Oracle Corporation, то значит эта технология всегда была в Oracle.

Somehow I keep on running into trouble installing 64-bit Oracle Fusion Middleware SOA suite. The process seems quiet simple if you follow the installation guide. First of all I installed the 64-bit J-Rockit (see this post how to download it).

$ export JAVA_HOME=/u01/app/jrockit
$ export PATH=$JAVA_HOME/bin:$PATH
$ java -version
java version “1.6.0_03″
Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
BEA JRockit(R) (build R27.5.0-110_o-99226-1.6.0_03-20080528-1505-linux-x86_64, compiled mode)

Next I started the generic installer and installed the weblogic server:

$ java -jar /u01/app/install/wls1032_generic.jar

Then it is time to set the environment and start the installer:

source /u01/app/oracle/middleware/wlserver_10.3/server/bin/setWLSEnv.sh
$ /u01/app/install/ofm_soa_11.1.1.2.0/Disk1/runInstaller -jreLoc /u01/app/jrockit

Now you would expect the installer to start, but instead this error is raised:

java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/tmp/OraInstall2009-11-26_11-43-29AM/ext/jlib/glassfish.jaxb_1.0.0.0_2-1-7.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
        at com.sun.xml.bind.v2.model.impl.ModelBuilder.(ModelBuilder.java:173)
        at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422)
        at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:286)
        at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
        at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:117)
        at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:188)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132)
        at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
        at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
        at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
        at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:244)
        at oracle.as.install.engine.config.xml.EngineConfigParser.getEngineConfig(EngineConfigParser.java:59)
        at oracle.as.install.engine.InstallEngine.startOperation(InstallEngine.java:379)
        at oracle.sysman.oio.oioc.OiocOneClickInstaller.main(OiocOneClickInstaller.java:446)
java.lang.NullPointerException
        at oracle.as.install.engine.InstallEngine.startOperation(InstallEngine.java:429)
        at oracle.sysman.oio.oioc.OiocOneClickInstaller.main(OiocOneClickInstaller.java:446)

Somehow this was not what I was expecting. It took me some time to figure out, but here’s what to do: download jaxb-api-2.1.jar to /tmp. Next open the runInstaller script and go to line 186. Change this line from:

$CMDDIR/install/linux64/runInstaller  JVM_OPTIONS=” -mx512m ” “$@” -J-Doracle.installer.appendjre=true $COMMANDLINE

to:

$CMDDIR/install/linux64/runInstaller  JVM_OPTIONS=” -mx512m -Djava.endorsed.dirs=/tmp” “$@” -J-Doracle.installer.appendjre=true $COMMANDLINE

Now you can start the installer and install the SOA suite. (updating the JVM to 1.6.0_04 might also fix the problem, but I can’t seem to find the 1.6.0_04 64-bit JRockit JVM  a newer JRockit can be found here. Just download a JRRT of JRMC and you are set)

Oracle Weblogic Simple Producer (Version 10.3)

Oracle Weblogic Simple producer is a light version of Oracle Weblogic Portal + Oracle Weblogic Federated resources. From here onwards simple producer will be used to indicate Oracle Weblogic Simple Producer. Remote portlets deployed on producer can be consumed by the consumer portal using WSRP protocol.

A simple producer can be created using the following steps:

Step 1: Create the simple producer domain

Step 2: Create the simple producer project

Step 3: Move the existing application to simple producer project or create new application as required.

Step 4: Generate simple producer portlets, books, pages etc.

Step 5: Deploy the simple producer application on simple producer domain

Step 6: Consume the simple producer portlets and you are done.

Following features are supported by Simple Producer:

• Page flow & struts portlets can be created and published as remote portlets
• URL Rewriting is supported

Following features are not supported by Simple Producer:

• Java, JSP, HTML, Clipper or Iframe portlets are not supported
• Registration of remote portlets are not supported
• No portal administration is available for simple producer
• No Backing file support is available for simple producer
• No event support is available for simple producer and thus inter portlet communication is also not available.
• Render dependency file is not supported by simple producer
• Portal APIs are not supported by simple producer

Some time ago I posted about the cloningutillity for Oracle Fusion Middleware 11. Mind you, this is something different from Oracle Fusion Middleware 11R1: 11.1.1.1.0 verses 11.1.1.2.0 . Even though the version sounds like a minor patch, I noticed that the cloningclient.jar utillity somehow lost the option -excludePattern. The error messages for excludepattern are still documented, but if you try to call the utillity with the -excludePattern option this error is raised:

SEVERE : Nov 18, 2009 12:41:58 PM – ERROR – CLONE-20200   The clone option or argument is invalid.
SEVERE : Nov 18, 2009 12:41:58 PM – CAUSE – CLONE-20200   The option or argument “-excludePattern” was not supported by cloning.
SEVERE : Nov 18, 2009 12:41:58 PM – ACTION – CLONE-20200   Provide valid option or argument. Use the “-help” command to know more about cloning options and arguments.

Removing functionality with a bugfix sounds somewhat like unexpected behaviour.

When starting the Admin Server of our domain we encountered following error:

####<Nov 13, 2009 11:58:23 AM CET> <Critical> <WebLogicServer> <machine-name> <as> <Main Thread> <<WLS Kernel>> <> <> <12
58109903043> <BEA-000386> <Server subsystem failed. Reason: java.lang.NumberFormatException: null
java.lang.NumberFormatException: null
        at java.lang.Integer.parseInt(Integer.java:415)
        at java.lang.Integer.parseInt(Integer.java:497)
        at weblogic.ldap.EmbeddedLDAP.validateVDEDirectories(EmbeddedLDAP.java:1035)
        at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:212)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>

The first thing we tried is restoring a backup of the ldap folder. This backup can be found at: ../domain-name/server/adminserver/data/ldap/backup/ and should be restored at ../domain-name/server/adminserver/data/ldap/ldapfiles.

When this was not working, we kept looking and stumbled upon a site that told us that this error could be caused when the volume that contains these files is running full. WebLogic will corrupt these files. And the solution is to add ‘replica.num=0′ to the ../domain-name/server/adminserver/data/ldap/config/replicas.prop file. Or just remove this file..

Source: http://ghattus.com/2008/10/number-format-exception-while-starting-weblogic-server.html

On a Weblogic 10 environment, you may get an error like
javax.servlet.ServletException: javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: “java.sql.SQLException: No suitable driver found for jndi_ds
if you are using the sql-taglib to access your JNDI name from the Weblogic application server, configured via the Weblogic console.

The solution is quiet simple, but not that good documented. It is not possible to use the paramter “driver” inside the sql:setDataSource – tag. You rather have to promote the JNDI name in your web.xml like this:

<resource-ref>
<res-ref-name>jndi_ds</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

Than you can set the dataSource with the sql:setDataSource – tag like this:

<sql:setDataSource dataSource="jndi_ds" />

and finally use the sql-taglib as you did in any other environment like Tomcat server and so on.

On a Weblogic server, you don’t need a rewite rule or filter to get rid of this …;jsessionid… stuff on any URL build using the “c:url” tag. You simply need to put one more line to your weblogic.xml:

<session-descriptor>
    <url-rewriting-enabled>false</url-rewriting-enabled>
</session-descriptor>

Experience installing, administering and monitoring tasks related to the support of Websphere Server 5.x and 6.1

Experience on Linux, Solaris and Windows OS environments

Good experience on upgrade process of Websphere 6.1 environments

Experience with Installing, Administering, Configuring Web servers like Sunone (Iplanet) 6.X, Windows IIS 5/6, and Plugins

Aware of Remedy ticketing system/ anything similar Ticketing system

Assist with high-profile initiatives

Roles & Responsibilities

1. Deploy new code release onto the production/non-production environments
2.  Configure the same environments on a regular basis to improve performance or adhere to new release
3. Apply the Security/Performance patches on Websphere Server & Iplanet server
4. Deployment of performance/security related patches for Websphere Server/web servers
5. Experience in monitoring Java applications using Wily Introscope / HP OVO
6. Problem ticket resolution includes RCA if required
7. Work on Solaris, Linux & Windows environments
8. Participate on EACO calls for any emergencies or major releases
9. Able to install and tune web servers such as SunOne 6.1 and Windows IIS
10. Work on infrastructure projects with teams like Network/OS/Development and QA
11. Strong communications skills, both in writing and speaking
12. Knowledge of WSAdmin/JACL/Jython scripting, Unix shell scripting and Windows batch scripting
13. Strong in Java, J2EE, JMS Comcepts

If you are interested for the above position, please send your profile quickly to goutami.m@whizhunt.com   with Job Code & Source in subject Line (Example: Weblogic_Admin/WordPress) is must to process your CV. Please Call 040- 66415264 for any further queries.

When depolying Spring Security on Weblogic 10.3. I encountered 2 pop up one for Spring and one for Weblogic.

Spring Security was configured with basic authentication. If your used is not in Weblogic’s security realm basically you dont get access. Some people also faced the same problem and here are their solutions.

If you use the form base authentication, you should be fine. It just happens for those who use the default basic/digest forms that your web browser provides.

1. Configure web.xml

<login-config>
<auth-method>CLIENT-CERT</auth-method>
</login-config>

add the above to your web.xml.

alternatively you can try this.

2. Edit weblogic config/config.xml
Add the following lines to config.xml in your admin server.

<enforce-valid-basic-auth-credentials>
    false
</enforce-valid-basic-auth-credentials>

Contract – Oracle Developer – Oracle 11g/Oracle WebLogic/Oracle Service Bus – SC Cleared – Excellent rates available

I have an urgent requirement for a Oracle Developer for a 6 month contract based in London. The ideal candidate should have experience with Oracle 11g, Oracle Web Logic 10.3, User interface and the Oracle Service Bus.

The ideal candidate should hold current CTC, SC or DV Clearance (Home Office, Police or MOD) however I may consider candidates willing to go through this process.

Skills should have:
Oracle 11g
Oracle WebLogic
Oracle Service Bus
User Interface

Excellent rates Available

Please send CV’s ASAP and I will contact you with more details.
Regards
Adam Sparey
Senior Consultant
adamsparey@peoplesource.co.uk
0117 922 7000

This case has no clear-cut solution, just a clarification:

Problem: Server crashed.

To be able to gather information, we had asked the customer to provide us with all the available log files – WebLogic log, the Standard Output, and the JVM log, to find the connections, and possibly – be able to identify the reason.

From its first lines, a JMV log file showed that it was a Java Virtual Machine crash, not WebLogic Server running on it:

# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (434F44452255464645520E435050005E 01), pid=15067, tid=8
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_11-b06 mixed mode)

As a number of other factors showed, a client had the Sun JVM installed – something beyond Oracle’s competency. We could only check whatever is was on the surface to see, it anything could trigger the crash.

We noticed the following line:

compacting perm gen total 63232K, used 63113K [0xf1800000, 0xf55c0000, 0xf9800000)
the space 63232K, 99% used [0xf1800000, 0xf55a25e0, 0xf55a2600, 0xf55c0000)

99% looked suspicious (which is true for any occasion), so we checked further:

jvm_args: -XX:MaxPermSize=128m -Xms1024m -Xmx1024m

Although unclear, shortage of memory could had been a reason of the crash. Just to make sure, we advised the customer to increase it to 512, or at least 256 mb.

In the end, we advices the customer to contact the Sun support, since they had a better cpecialty over their own Virtual Machine.

А вы чего, детектива ждали?

En alguna ocasión puede que necesitemos trabajar con el WebLogic Server, WLS, que viene integrado con JDeveloper R1.

Para ello lo podemos levantar y parar mediante los scripts situados en jdeveloper-user-home/DefaultDomain/bin.

Ej: C:\Documents and Settings\user\Datos de programa\JDeveloper\system11.1.1.1.33.54.07\DefaultDomain\bin

En esta ruta encontraran los scripts de parada y arranque del WLS.

Nota:recuerden que pordefecto las credenciales son weblogic/weblogic1

1. WebLogic Server have limited, definable number of threads allowed at the same time. A request sent to the server would have to wait, if all of the threads are currently busy. Assumingly, it should not ever happen.
2. Assumingly, once again, a routine request should come, be processed, and go, leaving a thread idle for the next request.
3. Now, a separate fully functional software entity is not just a server. It is also a database, an OS, some custom-built libraries, hardware, etc. All of them are communicating with each other, and with a server, on a millisecond basis.
4. Now, one of the problem, which may arise at any end of the system, at any point of time, and without a visible notice from the operator – is an event of one particular source start to send requests to the server, each of which would use one particular thread for an infinite time period. And another thread. And then – another. And another… Eventually, that one source can use all of the available threads with its requests, and force the server to crash, or restart itself, or do whatever is supposed to do in this case.
5. The worst part is that this event can have its origins from anywhere, any part of the system – database, custom libraries, OS after an update… An operator would never know, what caused the crash.

Solution:

Check the Thread dumps, – a series of them, generated with equal intervals from one another. Compare and see, which thread are doing what during that particular period – this way, you will be able to see if any request takes suspicious and may be the cause.

Weblogic – Aqualogic Service Bus – EAI – Part 1

This blog is to gather my learnings and understandings about Weblogic(WL)’s Aqualogic Service Bus (ALSB). Initially, i could not appreciate this awesome product from BEA. ALSB is meant mostly for Webservices and SOAP requests. I was trying to use these functionalities for normal GET and POST requests in RESTful services. Before we proceed further, lets look at some basic SOA jargons.

Service Bus:

Service Bus is considered as Enterprise Application Integration (EAI) tool, that would facilitate easy integration of various services (that are building blocks of any software system). This integration tool is created with various technologies that are opted for software middleware infrastructure. So, please note that ESB is not a programing language itself.

Also, ESB is NOT an app or web server. This is an application (could be web application) that runs in an web container. So, if you want to play with ALSB, you would need both WL server and ALSB. You could download trial version which you can use for 60days.

Basic Features of an ESB:

1. Loose coupling of services in a software system. This would provide great flexibility of modifying / enhancing any part of the system without affecting much on the other dependents.
2. ESB should be standard based and flexible, and should support many transport mediums like Messaging Service, SOAP, XML and text etc.
3. It should allow integration with very less coding. In other words, should be configurable.
4. ESB should be more scalable and highly revolvable.

All other features are added as vendors think it is necessary for an ESB. So, an Architect can select appropriate product based on their needs.

Ok! Lets get our hands dirty.

Installation:

ALSB setup can be (of course, trail version) downloaded from BEA site. I downloaded ALSB 3.0 which comes bundled with WL server 10.0.

There is nothing special about this installation. I just followed the installation setup wizard and it went perfect on my XP machine.

Basic Setup:

As basic setup, I created a user domain for my test project. You don’t need to create a new domain, if you prefer to work on example domain, which is created with installation.

So, I created a domain using Start –> All Programs –> Bea Products –> Tools –> Config Wizard. Please follow this link if you have any questions on specific setting.

Once domain is created, start weblogic server from Start –> All Programs –> Bea Products –> User_projects –> –> “Start Server for AquaLogic Service Bus Domain”

Look for server state as running. When server is up and running, it would open Weblogic Admin console automatically. Since we are interested in ALSB and its console, I am not going to discuss about Weblogic Admin Console here.

Weblogic products are considered as one of the best and user friendly because of their Admin Console. All settings and cluster, server maintenance and deployments everything could be done through Admin console.As we expected, ALSB has a Web Admin console, where most of the configuration can be done by just few clicks of mouse.

Ok. I like to wind up this blog at here. So, we have completed the installation of ALSB and before I start next topic, you could play around with various options in admin console to get used to it.

Weblogic – Aqualogic Service Bus – EAI – Part 2
I hope you are familiar with ALSB Admin console. If you don’t have Weblogic ALSB please visit my previous blog for seeting up ALSB on your window machine.

I assume that you have WL server running and you can open Admin console of ALSB (http://localhost:7001/sbconsole/) in a web browser. Please note, if you are installing WL10.0 bundle, the port number for ALSB may be 7021.

How ALSB works:

In a nutshell, ALSB acts as a proxy between client and service (any service lives in server). The proxying is done by creating a Proxy Service and Business Service in ALSB. I hope the below diagram could help you understand the “request” and “respose” flow.

As diagram illustrates, ALSB stands between client and service / server to route the requests and responses. Here, I have shown 2 proxy service and 2 business service. However, a project could have ‘n’ number of proxy services and business services. If you happen to have more proxy and business services, you may want to touch base with customer support folks regaring performs impact. I would suggest to have more than one ALSB instances to avoid any performance bottle necks. Few jargons definitions are below.

Project in ALSB.

A project is nothing but a group of proxy and business services. You may like to group proxy and business services of billing services in one project and a separate group for order management services.

Proxy Service:

You have guessed it! Proxy service is contacted by the client to eventually get response from target service. ALSB allows developer or ALSB administrator to modify any request data and metadata through Admin console configuration. For example, consider a case, where you have web service, is contacted by two different vendors (clients) with two different XML requests. You don’t need to write code to understand both request formats. Instead, ALSB Proxy service could be configured using XQuery to convert the request XML to desirable / server understandable format. This means easy addition of new clients with any changes to Target service, which evetually facilitate easy integration of systems.

Using XQuery programming, literally, all request data or parameters could be modified. If also allows to write logics to decide which business services to contact in runtime. This is one of the key feature of an ESB.

Business Service:

Business service represents target service’s URL. Business services are contacted by proxy service to route the requests to target service. If there are more than one target service (multiple instances of same service for scalability), all the URL can be added to single business service. ALSB also provides features for load-balancing of services. Business service also helps to fail-over services. Meaning, if one target service is down, Business service routes the requests to another service when there is an outage encountered by ALSB. It means high availability of your services.

Setting up ALSB:

As mentioned earlier, business services (BS) and proxy services(PS) are grouped under ALSB projects. So, before we create PS, BS, lets create a new project.

1. Open Admin console of ALSB. http://localhost:7001 or http://localhost:7021

2. Go to “Project Explorer” on left panel.

3. Once the Enter project name in text box in “Enter New Project Name:” and click on “Add Project”. If the text box is not enabled, please click on “Edit” on top left panel.

4. Project entry is added to the projects table just below that. Click on your project.

5. Select a “Resource” type from drop down options. First we create PS, So, select Proxy service from the option. On selecting PS option, next page should be automatically loaded.

6. Provide, proxy name and make sure you select “Any XML service option. Click on Next>>. As you can see, here, ALSB can support other services like Messaging, WSDL and SOAP services.

7. Select protocol as “http” and leave rest of the options with default values. Click on Next>> to save the settings for proxy service.

Now, you can new proxy serive is added to “Resources” table.

8. Next, create a business service by selecting “Business Service” in the drop down options.

9. Follow the setting wizard. Provide BS name and type. Please make sure you select same type as PS. Click on Next>>.

10. on next page, we have to some important configuration for BS. Select protocol as http and Load balancing Algorithm as round-robin. Provide End point URL of Target service. In our case any website url. Since other options are not much important at this level, please go with default values and click on Next>>.

11. Since, we are dealing with website, select HTTP request as “GET” and leave rest of the options with default values. Go to next page to save the settings.

Now that we have created both proxy service and business service, you might be wondering! “Wait a second, are we not supposed to hook up proxy service with business service???” Yes!! We should!. That’s next.

I would recommend to save the configurations so far that we have done by hitting “Activate” button on left top panel. Please note, in ASLB console each time as you modify setting, they are created as sessions. Later, if you find that one of the setting needs to be reverted back to original setting. You can go to “View All Sessions” and clicking on appropriate icon under Options.

if you clicked on Activate button, Click on “Create” again to create a new session.

Configure Proxy Service:

1. Click on your project under project explorer section. In Resources section, click on “Edit Message Flow” icon ( the one is activated) under “Actions” column.

2. On the next page right click on proxy service cover and select “Add Route”. Here, as you can see, you can “Add pipeline pair” to add request and response pipelines. Under request and response pipelines, you could “Add Stage” to perform logic operations.

3. So, we have added new Route, Right click on RouteNode1 to select “Edit Route” to modify setting. You can also modify the name of this node to a meaning ful name by selecting “Edit name and Comments”.

4. On Edit Route page, click on “Add an Action” –> Communication –> Routing
5. Now, you get new node added to this page. Click on “*” to select which business service should be contacted by this PS. You can also add other Request and Response Actions like modifying header or to perform some logic operations or Log the event to server log file for reporting purposes.

6. “Save All” this settings and Activate the session to be effective.

Here, PS is hooked up with BS. You can contact PS through your browser by typing http://localhost:7001/proxyServiceName
The response should be eventually from the target website URL. Hope you are getting a proper response. You can further explorer to add stage (as mentioned in step 2) and modify request data and headers.

You can also refer reference documents from BEA site for more information.

Node Managers Weblogic Server utility to start, stop and restartAdministration and Managed Server Instances from remote location (There are other ways as well to start/stop Weblogic check here – Node Manager is optional component).

1. Node Manager Process is associated with a Machine and NOT with specific Weblogic Domain (i.e. Use one node manager for multiple domains on same machine)

2. There are two versions of Node Manager – Java-based and Script-based

Java-based node manager – runs with in JVM (Java Virtual Machine) Process and more secure than script-based node manager. Configuration for java-based node manager are stored in nodemanager.properties

Script-based node manager – is available for Linux and Unix systems only and is based on shell script.

3. There are multiple ways to access Node Manager
- From Administration Console : Environments -> Machines -> Configuration -> Node Manager
- JMX utilities (Java Management eXtension) more here
- WLST commands (WebLogic Scripting Tool)

4.Default port on which node manager listen for requests is localhost:5556, When you configure Node Manager to accept commands from remote systems, you must uninstall the default Node Manager service, then reinstall it to listen on a non-localhost (IP’s other than 127.0.0.1) listen address.

5. Any domain created before creation of Node Manager Service will not be accessible via node Manager(even after restarting node manager), solution is to run the WLST command “nmEnroll” to enroll that domain with the Node Manager.

6. Any domains created after the Node Manager service has been installed should not have to be enrolled against the Node Manager. The Node Manager should automatically be ‘reachable‘ by the domain.

.
How to Configure Node Manager ?

1.Configure each computer (on which you wish to use Node Manager) as a Machine in WebLogic Server
Environments -> Machines -> New (Add Machine) Use Link here
Environments -> Machines -> Machine Name (created above) -> Configuration -> Node Manager

2. Assign each server instance (Admin or Managed that you wish to control with Node Manager) to Machine.
Environments -> Machines -> Machine Name (created above) -> Configuration -> Servers -> Add (Add Server running on this node which you would like to monitor using Node Manager) for more info Click here

3. Enroll domain (created before installation of Node Manager) to Node Manager

Windows
cd $BEA_HOME\user_projects\domains\\bin
setDomainEnv.cmd
java weblogic.WLST
wls> connect(’weblogic’,’weblogic’, ‘t3://mymachine.mydomain:7001′)
wls> nmEnroll(’C:\bea\user_projects\domains/’, ‘C:\bea\wlserver_/common/nodemanager’)

.
Unix /Linux
cd $BEA_HOME/user_projects/domains//bin/
. setDomainEnv.sh
java weblogic.WLST
wls> connect(’weblogic’,’weblogic’, ‘t3://mymachine.mydomain:7001′)
wls> nmEnroll(’$BEA_HOME/user_projects/domains/’, ‘$BEA_HOME/wlserver_/common/nodemanager’)

where “mymachine.mydomain:7001″ is the reference to the Admin Server of the domain to which the server and machine definition belongs

.
How to start Node Manager ?

$WL_HOME\server\bin\startNodeManager.sh (startNodeManager.cmd on Windows)

How to install Node Manager as Service on Windows ?

Use $WLS_HOME\server\bin\installNodeMgrSvc.cmd (Where default WLS_HOME location is c:\bea\wlserver_)

To uninstall Node Manager Service on windows use $WLS_HOME\server\bin\uninstallNodeMgrSvc.cmd

installNodeMgrSvc.cmd will create Windows server with name as Oracle WebLogic NodeManager (C_bea_wlserver_)
.
Important Configuration files

– $WL_HOME/common/nodemanager/ nodemanager.properties, nodemanager.domains, nm_data.properties

–$DOMAIN_HOME/config/nodemanager/nm_password.properties

–$DOMAIN_HOME/servers//data/nodemanager/ boot.properties, startup.properties, server_name.addr, server_name.lck, server_name.pid, server_name.state

Very useful tip, how to decrypt 3DES hashed password from configurations.

http://gustlik.wordpress.com/2008/08/06/decryption-of-configuration-passwords-in-weblogic/

You should add below code to class  from here:

http://geronimo.apache.org/apidocs/2.0.1/src-html/org/apache/geronimo/converter/bea/Weblogic81Utils.html

Below my version of main.
With some errors handlings

public static void main(String args[]) {
try{
if ( args== null || args.length<3 ) {
System.out.println("Usage:" );
System.out.println("arg1 = Server/lib or the Directory which has the requried JAR files");
System.out.println("arg2 = App Domain or the Directory which has SerializedSystemIni.dat");
System.out.println("arg3 = 3DES hashed password");
System.exit(0);
}
if  (! new File(args[0]).exists()) {
System.out.println("Path ["+args[0]+"] does not exists");
System.exit(0);
}
if  (! new File(args[1]).exists()) {
System.out.println("Path ["+args[1]+"] does not exists");
System.exit(0);

}
String beaDir = args[0];
String appDir = args[1];
String hashedPassword = args[2];
Weblogic81Utils weblogic81Utils = new Weblogic81Utils(beaDir, appDir);
String plainTextPassword = weblogic81Utils.decryptString(hashedPassword);
String configXML = weblogic81Utils.getConfigXML();
Properties bootProperties = (Properties) weblogic81Utils.getBootProperties();
System.out.println("---------------------------------------------------------------------");
System.out.println(hashedPassword + " == " + plainTextPassword);
System.out.println("boot.properties" + " <username> " + bootProperties.getProperty("username"));
System.out.println("boot.properties" + " <password> " + bootProperties.getProperty("password"));
System.out.println("---------------------------------------------------------------------");
}
catch (Exception e) {
    throw (RuntimeException)new IllegalArgumentException("Unable to initialize encryption routines from provided ar
guments").initCause(e);
}
} //end of main

Goal: to run Struts2+Spring plugin on a Weblogic 8.1 platform bundled with JDK 1.4.2_08, J2EE 1.3 (Servlet 2.3 and JSP 1.2) using the backported 2.0.14 version.

Premise: it seems that a J2EE 1.4 environment is required to run Struts2, but there are guys that have successfully deployed it on a J2EE 1.3 application server like Weblogic 8.1.

Download the backported version, the standard version and deploy a simple Struts2 project with, at least, these dependencies:

backport-util-concurrent-3.1.jar # from backport package
commons-fileupload-1.2.1.jar # from standard package
commons-io-1.3.2.jar # from standard package
commons-logging-1.0.4.jar # from standard package
freemarker-2.3.15.jar # from standard package
ognl-2.6.11.jar # from standard package
retrotranslator-runtime-1.2.9.jar # from backport package
struts2-core-j4-2.0.14.jar # from backport package
xwork-j4-2.0.7.jar # from backport package

You should be able to run the project without errors. You have to manually backport the plugin to use Spring as DI container (the reported error is the usual “Unsupported major.minor version 49.0“), typing the following command in a terminal:

java -jar retrotranslator-transformer-1.2.2.jar -advanced -srcjar $standard_package_path/lib/struts2-spring-plugin-2.0.14.jar -destjar struts2-spring-plugin-j4-2.0.14.jar

You can find the retrotranslator-transformer jar in the backport package. As usual, you have to add the plugin to the classpath along with all the Spring stuff.

I am discovering the mass deployment features of Fusion Middleware 11g. Oracle’s documentation sents you towards cloningclient.jar, which helps you creating a golden image and clone this image to new machines. What the documentation forgot to mention is that you only find cloningclient.jar on your filesystem after you installed an extra Oracle product in your middleware home (just WLS is not enough, you need SOA or some other component). That’s okay by me, since I am working on a SOA deployment anyway, but the docs could have been more clear on that one.

First of I copied the cloningclient.jar to some NFS share that is present on all my machines. This makes sure I will never have to look for this .jar again. Creating a golden image with cloningclient.jar is rather easy, just follow the documentation and you’ll be okay:

java -jar /software/oracle/32bit/FusionMiddleware/cloningclient.jar createclone -archiveLocation /software/oracle/32bit/FusionMiddleware/OFM_golden_image.jar -sourceMWHomeLoc /u01/app/oracle/mwhome  -excludePattern “*.log,*.bak” -invPtrLoc /u01/app/oracle/mwhome/Oracle_SOA1/oraInst.loc -silent true

Next you logon to a brand new installed machine and you call cloningclient.jar again, again all according to documentation:

java -jar /software/oracle/32bit/FusionMiddleware/cloningclient.jar applyClone -archiveLocation /software/oracle/32bit/FusionMiddleware/OFM_golden_image.jar -targetLocation /u01/app/oracle/mwhome -sourceID all -silent TRUE

Now this should give you a newly installed Fusion Middleware home, but instead you get this nice error:

Log: /u01/app/oracle/oraInventory/logs/install2009-10-21_05-07-57PM.log
contextFile:/tmp/PREREQ20091021_050730/Scripts/prereq/oui/agent_prereq_context.xml
java.lang.UnsatisfiedLinkError: /tmp/PREREQ20091021_050730/oui/lib/linux/liboraInstaller.so: /tmp/PREREQ20091021_050730/oui/lib/linux/liboraInstaller.so: cannot open shared object file: No such file or directory (Possible cause: architecture word width mismatch)
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(Unknown Source)
        at java.lang.ClassLoader.loadLibrary(Unknown Source)
        at java.lang.Runtime.load0(Unknown Source)
        at java.lang.System.load(Unknown Source)
        at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(OiipuUnixOps.java:402)
        at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.<clinit>(OiipuUnixOps.java:125)
        at oracle.sysman.oii.oiip.oiipg.OiipgFileSystem.changePermission(OiipgFileSystem.java:1995)
        at oracle.sysman.oii.oiix.OiixFileOps.changePermission(OiixFileOps.java:2110)
        at oracle.sysman.oii.oiix.OiixFileOps.changePermissions(OiixFileOps.java:2042)
        at oracle.sysman.oii.oiit.OiitLockHeartbeat.<init>(OiitLockHeartbeat.java:178)
        at oracle.sysman.oii.oiit.OiitTargetLocker.getReaderLock(OiitTargetLocker.java:473)
        at oracle.sysman.oii.oiii.OiiiTargetAreaControl.grabReaderLock(OiiiTargetAreaControl.java:361)
        at oracle.as.install.engine.modules.prereq.action.PrereqLauncher.initInstallInventory(PrereqLauncher.java:393)
        at oracle.as.install.engine.modules.prereq.action.PrereqLauncher.<init>(PrereqLauncher.java:128)
        at oracle.as.install.engine.modules.prereq.action.PrereqLauncher.getEnginePreReqLauncher(PrereqLauncher.java:119)
        at oracle.as.clone.util.PreReqUtil.prereqsetupAndLuncher(PreReqUtil.java:148)
        at oracle.as.clone.util.PreReqUtil.prereqcheck(PreReqUtil.java:433)
        at oracle.as.clone.mwhome.cloner.OracleHomeApplyCloner.preReqRun(OracleHomeApplyCloner.java:199)
        at oracle.as.clone.mwhome.cloner.OracleHomeApplyCloner.restoreOH(OracleHomeApplyCloner.java:154)
        at oracle.as.clone.mwhome.cloner.OracleHomeApplyCloner.restoreArchive(OracleHomeApplyCloner.java:122)
        at oracle.as.clone.cloner.ApplyCloner.doClone(ApplyCloner.java:50)
        at oracle.as.clone.request.ApplyCloneRequest.applyArchive(ApplyCloneRequest.java:70)
        at oracle.as.clone.request.ApplyCloneRequest._clone(ApplyCloneRequest.java:48)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:110)
        at oracle.as.clone.process.CloningExecutionProcess.execute(CloningExecutionProcess.java:95)
        at oracle.as.clone.client.CloningClient.main(CloningClient.java:112)

Obviously the architecture word width mismatch is a dead giveaway: I need a 32-bit JRE to run the cloningclient, even though I created the golden image with a 64-bit JRE (the default one from OEL 4). If you happen to look for one, there’s one in the original middleware home. Just copy it to the new server and set the JAVA_HOME environment to the 32-bit JRE.  If you apply the golden image with the cloningclient.jar again, you will run into the next error:

2009-10-21_05-49-49PM : ERROR  : CLONE-20269   Setting Java Library path has failed.
2009-10-21_05-49-49PM : CAUSE  : CLONE-20269   There are following possible causes
 1. The oui library path /tmp/PREREQ20091021_054922/oui/lib was empty
 2. Unable to find oui lib directory name.
  3. The oraInstaller library path /tmp/PREREQ20091021_054922/oui/lib/linux64 was empty.

Again this is 64-bit trouble, only this time the fix is easier. Just call linux32 bash before you restart the clone and now the cloning process will run successfully.  The cloning process also creates an entry in inventory.xml (located in oraInventory/ContentsXML ). You might want to remove this entry if you replay the cloning process over and over again. 

Hope this helps.

When you try to install the 11.1 SOA software, on 64-bit Linux, you might just forget to call linux32 before starting the installer. The actually error in the logging is this:

[2009-10-21T14:35:34.369+02:00] [as] [TRACE:16] [] [oracle.as.install.engine] [tid: 10] [ecid: 0000IHr64fm5mZWBdzR5D51Ark0J000001,0] [SRC_CLASS: oracle.as.install.engine.InstallEngine] [SRC_METHOD: startOperation] THROW[[
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at oracle.as.install.engine.InstallEngine.launchModule(InstallEngine.java:513)
        at oracle.as.install.engine.InstallEngine.processAndLaunchModules(InstallEngine.java:467)
        at oracle.as.install.engine.InstallEngine.startOperation(InstallEngine.java:420)
        at oracle.sysman.oio.oioc.OiocOneClickInstaller.main(OiocOneClickInstaller.java:449)
Caused by: java.lang.UnsatisfiedLinkError: no oraInstaller in java.library.path
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1709)
        at java.lang.Runtime.loadLibrary0(Runtime.java:823)
        at java.lang.System.loadLibrary(System.java:1030)
        at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(OiipuUnixOps.java:420)
        at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.<clinit>(OiipuUnixOps.java:125)
        at oracle.as.install.engine.modules.statistics.util.SysInfo.getAvailableMemory(SysInfo.java:162)
        at oracle.as.install.engine.modules.statistics.element.AvailableMemoryElement.<init>(AvailableMemoryElement.java:39)
        at oracle.as.install.engine.modules.statistics.standard.StandardElementLocator.loadElements(StandardElementLocator.java:63)
        at oracle.as.install.engine.modules.statistics.boot.ProfilerInitializer.initializeProfile(ProfilerInitializer.java:82)
        at oracle.as.install.engine.modules.statistics.Statistics.launchModule(Statistics.java:284)
        ... 8 more

]]

This is a lengthly way of saying: hey! you’re running 32-bit software on a 64-bit OS.

If you do any monitoring of your Weblogic cluster using the Weblogic Administration Console you may want to look at WLST to perform some of the same tasks. This simple WLST script will print JVM, JDBC and Thread details.  The script uses WLST definitions to do most of the work (definitions are like functions, they are re-usable code blocks).  The script should connect to the Administration server and it uses the domain runtime and server runtime MBean.

You can easily modify the script to include any additional monitoring tasks.  Once you have your definitions defined you can call them with managed server names as arguments.

# definition for connecting to a server
def connect_to_server():
  username = 'system'
  password = 'xxxxxx'
  url = 't3://host:port'
  connect(username, password, url)
  domainRuntime()

# definition to print a running servers jvm heap details
def print_heap_details(server_name):
  cd('ServerRuntimes/'+server_name+'/JVMRuntime/'+server_name)
  hfree = float(get('HeapFreeCurrent'))/1024
  hsize = float(get('HeapSizeCurrent'))/1024
  hpercent = float(get('HeapFreePercent'))
  utime = float(((get('Uptime'))/1000)/60)
  hfree = hf/1024
  hsize = hs/1024
  print get('Name')
  print 'JVM Details'
  print 'HeapFreeCurrent ' + `hfree` + ' MB'
  print 'HeapSizeCurrent ' + `hsize` + ' MB'
  print 'HeapFreePercent ' + `hpercent` + '%'
  print 'Uptime ' + `utime` + ' minutes'

# definition to print a running servers jdbc details
def print_jdbc_details(server_name):
  cd('ServerRuntimes/'+server_name+'/JDBCServiceRuntime/'+server_name+'/JDBCDataSourceRuntimeMBeans/ConnectionPool')
  print 'JDBC Details'
  print 'Active Connections Current Count ' + `get('ActiveConnectionsCurrentCount')`
  print 'Active Connections High Count ' + `get('ActiveConnectionsHighCount')`
  print 'Connection Delay Time ' + `get('ConnectionDelayTime')`
  print 'Connections Total Count ' + `get('ConnectionsTotalCount')`
  print 'Failures To Reconnect Count ' + `get('FailuresToReconnectCount')`
  print 'Leaked Connection Count ' + `get('LeakedConnectionCount')`

# definition to print a running servers thread details
def print_thread_details(server_name):
  cd('ServerRuntimes/'+server_name+'/ThreadPoolRuntime/ThreadPoolRuntime')
  print 'Thread Details'
  print 'Completed Request Count ' + `float(get('CompletedRequestCount'))`
  print 'Execute Thread Idle Count ' + `get('ExecuteThreadIdleCount')`
  print 'Execute Thread Total Count ' + `get('ExecuteThreadTotalCount')`
  print 'Hogging Thread Count ' + `get('HoggingThreadCount')`
  print 'Pending User Request Count ' + `get('PendingUserRequestCount')`
  print 'Queue Length ' + `get('QueueLength')`
  print 'Standby Thread Count ' + `get('StandbyThreadCount')`
  print 'Throughput ' + `get('Throughput')`
  print ''

# definition to disconnect from a server
def disconnect_from_server():
  disconnect()
  exit()

# call connect_to_server definition with no arguments
connect_to_server()

# call the definitions with server name arguments
print_heap_details('ManagedNodeA')
print_jdbc_details('ManagedNodeA')
print_thread_details('ManagedNodeA')
print_heap_details('ManagedNodeB')
print_jdbc_details('ManagedNodeB')
print_thread_details('ManagedNodeB')

# call disconnectFromServer definition
disconnect_from_server()

This WLST script prints details found on these BEA Weblogic Administration Console screens:

BEA WebLogic Server Administration Console JVM

BEA WebLogic Server Administration Console JDBC

BEA WebLogic Server Administration Console Threads

This post takes you through the steps to install Apache 2.2.11 on Ubuntu 9.04 64 bit and make it work with Weblogic 10.3. The post walks through the steps that I followed, the problems that I faced and the solutions ( er..hacks) to get them resolved.

Installing Apache

• Is simple do

sudo apt-get install apache2

If you want to build it from sources then follow these steps.

• Once you have installed apache2 then the installation happens at the following locations in Ubuntu

Apache config files are in /etc/apache
Apache log files are in /var/log/apache
Apache libs are in /usr/lib/apache
Other files can be in /usr/share/apache, /var/lib/apache
executables in /usr/sbin apache and apache2ctl

• Now to start apache execute the following

vhazrati@vhazrati-laptop:/usr/sbin$ sudo apache2ctl start

• Note that the server is started as a root, else you might get the following error

(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

You should be able to access the default page on http://localhost now and see It Works!

Now, Integrating with Weblogic

• Download the apache plugins for weblogic 10.3 from the following location

http://download.oracle.com/otn/bea/weblogic/server103/server103_apacheplugins.zip

• Unzip the contents and select the mod_wl_22.so file from the location

<apache-plugin-unzip-location>linux/x86_64

• This file needs to be loaded the following location

/usr/lib/apache2/modules

• to test whether the file is valid or not do ldd

vhazrati@vhazrati-laptop:/usr/lib/apache2/modules$ ldd mod_wl_22.so
linux-vdso.so.1 =>  (0×00007fff02ffe000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0×00007f5cfaaff000)
libm.so.6 => /lib/libm.so.6 (0×00007f5cfa87a000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0×00007f5cfa661000)
libc.so.6 => /lib/libc.so.6 (0×00007f5cfa2ef000)
/lib64/ld-linux-x86-64.so.2 (0×00007f5cfafc5000)

• You might notice that some file like in my case libstdc++.so.5 => was not found!

-bash-3.00$ ldd mod_wl_22.so
libstdc++.so.5 => not found
libm.so.6 => /lib64/tls/libm.so.6 (0×0000002a9572f000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0×0000002a958b5000)
libc.so.6 => /lib64/tls/libc.so.6 (0×0000002a959c3000)
/lib64/ld-linux-x86-64.so.2 (0×000000552aaaa000)

• Goto the synaptic package manager, search and install this file.

• Now create a weblogic.load file with the following contents

LoadModule weblogic_module /usr/lib/apache2/modules/mod_wl_22.so

• and put it at the following location

/etc/apache2/mods-enabled

• You can also create a weblogic.conf file with the following contents at the same location

<Location /medrec>
SetHandler weblogic-handler
WebLogicHost 127.0.1.1
WebLogicPort 7011
</Location>

This would help in redirecting a request like http://localhost/medrec to the weblogic server running on 127.0.1.1 and at 7011 port with the application name medrec.

• Restart Apache

vhazrati@vhazrati-laptop:/usr/sbin$ sudo apache2ctl restart

• Check whether the weblogic_module has been loaded successfully or not

vhazrati@vhazrati-laptop:/usr/sbin$ apache2 -t -D DUMP_MODULES
apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
Loaded Modules:
core_module (static)
log_config_module (static)
logio_module (static)
mpm_worker_module (static)
http_module (static)
so_module (static)
alias_module (shared)
auth_basic_module (shared)
authn_file_module (shared)
authz_default_module (shared)
authz_groupfile_module (shared)
authz_host_module (shared)
authz_user_module (shared)
autoindex_module (shared)
cgid_module (shared)
deflate_module (shared)
dir_module (shared)
env_module (shared)
mime_module (shared)
negotiation_module (shared)
setenvif_module (shared)
status_module (shared)
weblogic_module (shared)

• If you see the weblogic_module loaded fine then you have configured it correctly and can now access the application at

http://localhost/medrec/

• To test whether the apache2.conf file is correct or not you can use

vhazrati@vhazrati-laptop:/usr/sbin$ apache2 -t
apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
Syntax OK

Other Potential Problem(s)

• You may encounter the problem bad user name ${APACHE_RUN_USER}

this is because the value of ${APACHE_RUN_USER} is not getting picked up. Ideally it should be picked up from /etc/apache2/envvars

which has the following entries

# envvars – default environment variables for apache2ctl

# Since there is no sane way to get the parsed apache2 config in scripts, some
# settings are defined via environment variables and then used in apache2ctl,
# /etc/init.d/apache2, /etc/logrotate.d/apache2, etc.
export APACHE_RUN_USER=www-data
export APACHE_RUN_GROUP=www-data
export APACHE_PID_FILE=/var/run/apache2.pid

However, still in your case if these values are not picked up then goto the /etc/apache2/apache2.conf file and make the following changes

# These need to be set in /etc/apache2/envvars
# User ${APACHE_RUN_USER}
# Group ${APACHE_RUN_GROUP}
User www-data
Group www-data

• The weblogic.load file is not read for some reason and hence the weblogic_module is not loaded

Make an entry in the httpd.conf file at the following location

/etc/apache2/httpd.conf

and enter the LoadModule and other configuration data in this file

LoadModule weblogic_module /usr/lib/apache2/modules/mod_wl_22.so

<Location /medrec>
SetHandler weblogic-handler
WebLogicHost 127.0.1.1
WebLogicPort 7011
</Location>

There is an entry in the apache2.conf file to include the httpd.conf file, hence the changes of httpd.conf would get loaded

# Include all the user configurations:
Include /etc/apache2/httpd.conf

Further Reading

http://www.oracle.com/technology/obe/fusion_middleware/wls103/cluster/config_proxy_srvr/config_proxy_srvr.htm#t3

http://vikashazrati.wordpress.com/2008/12/14/apache-on-ubuntu/

http://download.oracle.com/docs/cd/E13222_01/wls/docs100/plugins/apache.html