Tuesday Feb 24, 2015

Full recovery of a corrupt WebLogic embedded LDAP server by Peter van Nes

clip_image002Today one of the Adminservers failed to re-start and was flooding the AdminServer.out with multiple EmbeddedLDAP java.lang.ArrayIndexOutOfBoundException messages per second. I do admit, this is not the first article about how to recover from this issue, and probably not the last. Although i was able to Google multiple articles and blogs on this exception, all of the suggested solutions left me with a seed embedded LDAP. The good news is that  by default a backup is made of the embedded LDAP every day at 23:05 and the last 7 copies are retained. You can find these setting by selecting the domain in the domainstructure of the Weblogic console and then open the tab Security > Embedded LDAP.

So you can recover fully from a corrupt Weblogic embedded LDAP server, just follow these few steps.

· Shutdown admin server

· Move the current data directory so you can access it later.
mv <domain_home>/servers/AdminServer/data to <domain_home>/servers/AdminServer/data.bkp

· Start the admin server Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Thursday Dec 04, 2014

Whole Server Migration by Rene van Wijk

clip_image002In a WebLogic Server cluster, most services are deployed homogeneously on all server instances in the cluster, enabling transparent fail-over from one server instance to another. In contrast, for 'pinned services' such as JMS and the JTA transaction recovery system are targeted at individual server instances within a cluster, WebLogic Server supports failure recovery with migration, as opposed to fail-over.
Migration in WebLogic Server is the process of moving a clustered WebLogic Server instance or a component running on a clustered server instance elsewhere in the event of failure. Upon failure, a migratable server is automatically restarted on the same machine, if possible. If the migratable server cannot be restarted on the machine where it failed, it is migrated to another machine. In addition, an administrator can manually initiate migration of a server instance.

Configure whole server migration

Before we configure whole server migration, we need to know the requirements:

  • The migratable server candidate machines have to be in the same subnet (because the virtual IP address must be valid on each candidate machine). Whole server migration uses a virtual IP address for each migratable server.
  • On each candidate machine, the Node Manager must be initialized such that it can accept commands from the Admin Server.
  • The Node Manager is used to migrate the virtual IP address and assign it to the target machine (i.e., invoke ${DOMAIN_HOME}/bin/server_migration/wlsifconfig.sh addif or invoke ${DOMAIN_HOME}/bin/server_migration/wlsifconfig.sh removeif). Note that the default configuration assumes that the machines are similar, i.e.,
    • The netmask associated with the virtual IP is the same on each candidate machine.
    • The network device (interface) name (for example, eth0 on Linux) is the same on each candidate machine.
    • The functional behavior of the platform-specific OS command used to add and remove the virtual IP (for example, ifconfig and arping on Linux) is the same.
  • Migratable servers cannot define any network channels that use a Listen Address different from the virtual IP address associated with the server. If servers must use multiple network channels associated with multiple IP addresses, whole server migration cannot be used as only migration of a single virtual IP address for each migratable server is supported.
  • Server-specific state must be shared through some highly available sharing mechanism, i.e., the default persistent stores where the XA transaction logs are kept must be accessible on each candidate machine.

As mentioned above the Node Manager invokes the script wlsifconfig.sh to run ifconfig and arping commands (more information on these commands can be found here), for example, Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Tuesday May 13, 2014

A Weblogic Admin Console with a dynamic look and feel by Peter van Nes

In my previous post i explained how to build your a custom look and feel for the Weblogic Administration Console, which is a result of research into a possibility to distinguish Weblogic Consoles in DTAP environments. My initial plan was to develop a separate look and feel for each specific environment, simply because i did not know what the possibilities were. I quickly abandoned this plan and developed one Weblogic Admin Console look and feel which adapts itself to the environment wherein it is deployed.

At most sites there is a way to determine if your host is running in a Development, Test, Acceptation or Production environment. The key data used to differentiate these environments depends on the infrastructure. It can be for example the IP-address, DNS name or Weblogic Domain name. A customer for example has standardized the weblogic domain names in such a way that the first position of the domain name corresponds with the environment. A Weblogic Development domain therefore always starts with a ‘D’, test with ‘T’, etc.  In this article i will show you how to make the Weblogic Console adapt its look and feel based on the Weblogic Domain name.

The Weblogic Admin Console login page is defined in /login/LoginForm.jsp which imports the MBeanUtils.class file. This class contains a lot of valuable methods. One of those methods, getDomainName() returns as it says the name of the Weblogic Domain. Simply by adding the following single line of Java as a JSP expression to LoginForm.jsp gives you the Weblogic domain name for which the Admin Console is opened. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Friday Feb 28, 2014

WebLogic troubleshooting: Diagnostic watch causing stuck threads by Tony van Esch

In one of our SOA/BPM environments, the stability of the WebLogic server running the SOA and BPM Suite was not as it should be. There were problems deploying ear files and accessing the BPM workspace etcetera. Enterprise Manager Fusion Middleware control homepage would show that everything is running fine. But accessing the soainfra pages would fail.

failed_to_get

In the AdminServer logs the following relevant entries were found. Apparently the AdminServer fails at communicating with the soa_server1 managed server. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Wednesday Feb 26, 2014

Automatic Scaling an Application using WebLogic by René van Wijk

Say we want to add (or start) managed server instances when running an application, for example, when the number of open sessions reach a certain value. For this value we have calculated that the memory consumption is beyond a level, such that the garbage collection is affected. By adding (or starting) a new server we balance the load (the number of sessions with its corresponding memory consumption) across multiple servers. By using the WebLogic Diagnostic Framework, we can collect the metrics we need and create a watch for that metric with a corresponding notification. By using this notification we can then further create the logic needed in order to add (or start) a managed server. For example, by using the notification service that come with the WebLogic Diagnostic Framework we can send a JMS message or a JMX notification. In this post we are going to use the JMS approach. Environment The WebLogic environment consists of a cluster, spanning two machines, and consisting of four managed servers. This can be easily set-up by using the scripts presented in the post Automate WebLogic 12.1.2 Deployment. The diagnostic module is configured as follows - See more at: Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Technorati Tags:

Monday Feb 24, 2014

WebLogic Hackathon: Automated Provisioning using Puppet by Ronald van Luttikhuizen

This presentation accompanies a hands-on-lab session in which Puppet will be used to automatically provision Oracle WebLogic Server. Puppet is a tool to automate configuration management.

Together with Chef it's one of the more popular configuration management tools at the moment. Puppet allows you to describe the desired (to-be) state of your servers by declaring resources. These declarations can describe user accounts, security settings, packages, directories, files, executable statements, services, and so on.

Manifests are the files in which resource declarations are listed. Puppet periodically applies manifests by translating manifests into specific commands (catalogs) and executes those on the managed servers. Puppet is capable of inspecting the machines so it only applies those changes that are necessary. If a machine is already in the desired state Puppet will apply no changes.

Read also the post: Hands-on-lab material available for WebLogic provisioning using Puppet !!

Get the presentation here.


WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Thursday Feb 20, 2014

Automatic Scaling an Application using WebLogic by René van Wijk

Say we want to add (or start) managed server instances when running an application, for example, when the number of open sessions reach a certain value. For this value we have calculated that the memory consumption is beyond a level, such that the garbage collection is affected. By adding (or starting) a new server we balance the load (the number of sessions with its corresponding memory consumption) across multiple servers. By using the WebLogic Diagnostic Framework, we can collect the metrics we need and create a watch for that metric with a corresponding notification. By using this notification we can then further create the logic needed in order to add (or start) a managed server. For example, by using the notification service that come with the WebLogic Diagnostic Framework we can send a JMS message or a JMX notification. In this post we are going to use the JMS approach. Environment The WebLogic environment consists of a cluster, spanning two machines, and consisting of four managed servers. This can be easily set-up by using the scripts presented in the post Automate WebLogic 12.1.2 Deployment. The diagnostic module is configured as follows - See more at: Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Tuesday Feb 18, 2014

WebLogic Hackathon: Automated Provisioning using Puppet by Ronald van Luttikhuizen

This presentation accompanies a hands-on-lab session in which Puppet will be used to automatically provision Oracle WebLogic Server. Puppet is a tool to automate configuration management.

Together with Chef it's one of the more popular configuration management tools at the moment. Puppet allows you to describe the desired (to-be) state of your servers by declaring resources. These declarations can describe user accounts, security settings, packages, directories, files, executable statements, services, and so on.

Manifests are the files in which resource declarations are listed. Puppet periodically applies manifests by translating manifests into specific commands (catalogs) and executes those on the managed servers. Puppet is capable of inspecting the machines so it only applies those changes that are necessary. If a machine is already in the desired state Puppet will apply no changes.

Read also the post: Hands-on-lab material available for WebLogic provisioning using Puppet !!

Get the presentation here.


WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Monday Feb 03, 2014

Automate WebLogic Installation and Configuration by René van Wijk

In this post, we will show how to create automation scripts in order to set-up middleware environments.

Preparation

As an example, we will use the Oracle Service Bus. In the example, we will use the following software

First, we have to decide how the directory structure will look, for example.

Installation

To silent install JRockit, we need the following XML file - See more here!

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Monday Dec 30, 2013

Cloud Control: Automatic refresh of Weblogic domain members by Tony van Esch

enable_refresh_domain_jobIt’s a fact that Weblogic domains are dynamic in nature, especially when SOA components are involved. Out of the box Cloud Control does not update the target list of a Weblogic domain. Ofcourse you can manually trigger a refresh of the Weblogic domain, but it would be much better to automate this procedure.

Automation can be achieved by enabling the ‘refresh domain’ job per domain.

Go to a domain and under the ‘General’ tab, click on the ‘Weblogic Domain Refreshed’ date.

To check the refresh jobs in Cloud Control, go to Enterprise > job > Activity Read the complete article here.


WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Monday Nov 18, 2013

Setup a 12c Fusion Middleware Infrastructure by René van Wijk

In this post, we will show how to create automation scripts in order to set-up middleware environments.

Preparation
In the example, we will use the following software Oracle JDK Fusion Middleware Infrastructure (fmw_infra_121200.jar) which can be obtained from the Oracle Software Delivery Cloud.

Oracle HTTP Server (ohs_121200_linux64.bin) which can be obtained from the Oracle Software Delivery Cloud.

First, we have to decide which directory structure we are going to use. Below an example is given in which the binaries (that create the run-time) are separated from the configuration. - See more.

Installation To install a Fusion Middleware Infrastructure (that uses Oracle JDK as the Java Virtual Machine) we can use the following script - See more. Read the full article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Monday Oct 28, 2013

Developing geometry-based Web Services for WebLogic | Part 1 by Ronald van Luttikhuizen

In a recent project we developed Web Services that expose geographical data in their operations. This blog explains the use case for the service, gives an overview of the software architecture, and briefly discusses GML as markup language for geographical data. Part 2 of this blog provides pointers on the implementation of the service while part 3 discusses the deployment on Oracle WebLogic Server.

Use Case

The "BAG" (Basisregistratie Adressen en Gebouwen) is a Dutch national database containing information on all addresses and buildings in the Netherlands, and is maintained by Dutch municipalities. For several object types the BAG also maintains the associated geographical location and shape; for example for premises and cities. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Thursday Sep 26, 2013

Session Management using WebLogic12 by René van Wijk

In this post we take a look at WebLogic session management. We will take a look at Coherence*Web, and see how things have simplified in WebLogic 12.1.2 when compared to WebLogic 12.1.1. We use the Java 7 Flight Recorder to analyze some WebLogic diagnostics. To persist sessions we have the following options.

  • In-memory replication – node that Web applications which have persistent store type set to replicated or replicated_if_clustered will have to be targeted to the cluster or all the nodes of that cluster. If it is targeted to only some nodes in the cluster, the Web application will not be deployed. In-memory replication requires that Web applications be deployed homogeneously on all the nodes in a cluster.
  • JDBC-based persistence – WebLogic maintains the HTTP session state using file-based or JDBC-based persistence. Coherence*Web – a remark from the documentation: “
  • Coherence*Web is not a replacement for WebLogic Server’s in-memory HTTP state replication services. However, you should consider using Coherence*Web when an application has large HTTP session state objects, when running into memory constraints due to storing HTTP session object data, or if you want to reuse an existing Coherence cluster.” To configure a persitent type set the persistent Read the full article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Wednesday Aug 21, 2013

Fun with Enterprise Manager for WebLogic by René van Wijk

Oracle Enterprise Manager is Oracle’s integrated enterprise information technology management product line, which provides a complete, integrated, and business-driven enterprise cloud management solution. Oracle Enterprise Manager creates business value from IT by leveraging the built-in management capabilities of the Oracle stack for traditional and cloud environments, enabling customers to achieve unprecedented efficiency gains while dramatically increasing service levels. The key capabilities of Enterprise Manager include:

  • A complete cloud lifecycle management solution enabling you to quickly set up, manage, and support enterprise clouds and traditional Oracle IT environments from applications to disk.
  • Maximum return on IT management investment through the best solutions for intelligent management of the Oracle stack and engineered systems with real-time integration of Oracle’s knowledge base with each customer environment.
  • Best service levels for traditional and cloud applications through business-driven application management.

Tuning

After installing and configuring enterprise manager it might be beneficial to tune the environment. To tune the agent, navigate to the${AGENT_HOME}/agent_inst/sysman/config directory. Open the file emd.properties and edit the agentJavaDefines property, set the memory parameters for the Java Virtual Machine to, for example, Set extra tuning parameters for the Java Virtual Machine in the s_jvm_options.opt file, for example: Read the full article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Wednesday Apr 24, 2013

WebLogic Logging Configuration by René van Wijk

In general, it is a good idea to use log rotation to prevent having to stop a WebLogic server to remove a large log file that is filling up the file system. It is also a good idea to create a separate partition such that the root file system does not fill up. A partition is a contiguous set of blocks on a drive that are treated as if they were independent disks. The default installation of today’s Enterprise Linux distributions uses flexible partitioning layouts by creating one or more logical volumes. Some of the partitions that we might want to consider separating out from root to provide more flexibility and better performance in the environment

  • /home – A file server environment would benefit from separating out /home to its own partition. This is the home directory for all users on the system, if there are no disk quotas implemented, so separating this directory should isolate a user’s runaway consumption of disk space.
  • /tmp – If we are running a high-performance computing environment, large amounts of temporary space are needed during compute time, then released upon completion.
  • /usr – This is where the kernel source tree and Linux documentation (as well as most executable binaries) are located. The /usr/local directory stores the executables that must be accessed by all users on the system and is a good location to store custom scripts developed for our environment. If it is separated to its own partition, then files will not have to be reinstalled during an upgrade or reinstall by simply choosing not to have the partition reformatted
  • /var – The /var partition is important in mail, Web, and print server environments because it contains the log files for these environments and the overall system log. Chronic messages can flood and fill this partition. If this occurs and the partition is not separate from the /, service interruptions are possible. Depending on the environment, further separation of this partition is possible by separating out /var/spool/mail for a mail server or /var/log for system logs.
  • /opt – The installation of some third-party software products, such as WebLogic Server, default to this partition. If not separate, the installation will continue under / and, if there is not enough space allocated, could fail.


Read the full article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Search

Archives
« March 2015
SunMonTueWedThuFriSat
21
27
28
29
30
31
    
       
Today