Welcome!

Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Do You Know What You Run?

A handy reference to finding your log files - and your SERVER version

Very large organizations know the value of spending a little (or a lot of) extra money to be in total control of the information. The rest of us have probably run into situations where the server version in production may or may not be exactly the same as the one in the QA section and would most certainly run at different log and debug settings from the server developers are working with. This article will cover the common ways to check basic WebLogic information, including versions and log locations. Knowing exactly what you run will also allow you to speed up that inescapable initial exchange of information with your BEA support engineer and allow him or her to get past configuration and into the technical depth of the actual issue.

Versions, Service Packs, and Rolling Patches
The official numbering for the BEA WebLogic product family is MajorVersion.MinorVersion.ServicePack.RollingPatch. Usually, you'll only hear about MajorVersion.MinorVersion in the press releases (e.g., 5.1, 6.0, 6.1, 7.0, and 8.1 for the WebLogic Server), but of course it is the ServicePack that gets the most workout in day-to-day server maintenance and administration.

Some confusion was introduced by BEA's new policy of Weblogic Platform releases in parallel with the stand-alone BEA WebLogic Server releases. Specifically, BEA WebLogic Platform 8.1 is actually built on the WebLogic Server 8.1sp1 and all the components are versioned at 8.1.1.0.

On the other hand, the rolling-patch was last seen at the time of WebLogic 6.0 and let us hope that was the last time.

In addition to the official numbering, there are also one-off (temporary) patches. Any number of them may be applied at the same time since they don't influence the version number, but sometimes it is very important to know exactly which patches are applied.

One important thing to remember about temporary patches (CRxxxx_spX.jar) is that they are specific to the release/service pack version. Trying to use a patch from an older service pack in the newer one can have disastrous effects - some more obvious than others. Listing 1 is an example of applying a WebLogic Server 7.0sp1 patch on the WebLogic Server 7.0sp2 version.

No problems, right? No problems in the server log version either. Then why does WebLogic Server recompile the JSPs that were already precompiled by the same version of WebLogic? The answer is in the console's version information (see Figure 1).

 

Notice that the Server Release Build value is suddenly transposed into 7.0.1.0 (WebLogic Server 7.0sp1). This is what the JSP compiler checks to determine the need to recompile the JSPs and it is a direct effect of an incorrect patch.

How to Skin a Cat (or Checking Version Numbers)
So, how many approaches are there to check for version number? Let us count the ways.

Remotely
Both of the following methods are good for system administrators who have access to and are comfortable with the WebLogic Server, but don't necessarily have access to the machine on which the WebLogic Server runs. After all, with Node Manager and the admin console, it's easy enough to install the server once and throw away the key (account password, that is).

WebLogic Console
This is the easiest and most complete method of getting the versions. You can find it in the Weblogic Console under Console/[Versions] tab. Figure 2 is the screenshot for the WebLogic Server 8.1sp1 (Platform install).

 

As you can see, the versioning information is very complete. It may also be slightly confusing with multiple components installed. The important thing to remember here is that unless you explicitly expect otherwise, the version numbers for all components should match.

weblogic.Admin VERSION
For those of you who like command lines, weblogic.Admin command provides a VERSION option that will return the equivalent of the last entry set in the console display (see Listing 2).

Onsite
The previous section was good for remote administration. What if you're already on the system and working with the files? Perhaps your WebLogic instance is down or you are support personnel and are actually working with somebody else's files. What options do you have then? Quite a few actually.

Server Log
A lot of the information may be found in the server log files, the version strings section being one of them. You can find the section (message BEA-000214 for WebLogic Server 8.1) near the beginning of the run's log, It looks similar to Listing 3.

Notice that as in our previous example of the bad patch, there is no information provided about the version the patches were for. You can, however, extract that information later in the log by looking at the java.class.path in the logged system properties (WebLogic Server 8.1 Message ID: BEA-141034). All the valid BEA patches will have server version information as part of the patch name (e.g., CR123103_81sp1.jar). All of the third-party or invalid patches will, hopefully, stand out exactly because they are missing that information and naming convention.

Odd Places
If you don't have the administrative access to the WebLogic Server, or all the server log files for the last run start have rolled over and were deleted/archived away, you can get a rough idea of what you are up against from various places in your installation.

From the start scripts, you can often tell a general version of WebLogic (based on WL_HOME) and the patches applied (look for CLASSPATH and PRE_CLASSPATH).

Starting with WebLogic 7, the config.xml may contain a ConfigurationVersion attribute in the Domain tag and a ServerVersion attribute in the Server tag. Both attributes, however, are used more for compatibility indication, so use them as an indication of what the server version is not. For example, if you see

<Domain ConfigurationVersion="7.0.2.0" Name="managedDom">

chances are very high that you are running a WebLogic 7 SP2 or higher. It could, of course, still be WebLogic 8.1 in a compatibility mode, so take this value with a grain of salt.

The last odd place to cover is the new domain-info.xml file that WebLogic 8 installs in the domain directory when configured from templates (e.g., WebLogic Configuration Wizard). The file contains the list of base templates and extensions installed over the domain's lifetime. Again, this is more curiosity than a real information source (but don't say we haven't tried to cover for the difficult cases).

Log File Names and Locations
A running WebLogic instance will generate many log files. Table 1 is a list of the core log files. Each extension (Integration, Portal, Workshop, etc.) will also have its own list of logs and should be covered separately (see Table 1).

 

The interesting thing about a server log (and probably BEA products in general) is that in the chase for ever better and ever more useful functionality, the formats and locations of log files keep changing. This especially hits hard those people who are used to running on one version of WebLogic and then upgrading to the latest release. I'm not even going to mention the plight of us - the BEA support personnel - who support at least four versions of WebLogic (5.1 onwards) on top of template and customers variations.

Following is a quick list of server log-related quirks that may have wasted your time in multiversion environments.

  • The default location of the server log file is in <domain>/<servername> for WebLogic Server 5.1, 7.0, and 8.1, but <domain>/logs for WebLogic Server 6.1. To add to the confusion, WebLogic Server 7.0 may have a zero-sized weblogic.log file in the <domain>/logs that is actually a dummy and will never be written to.
  • With WebLogic 8.1 in a development mode, a log file will be automatically rolled over at server startup regardless of the current file size. This and other differences between production and development mode are described at http://e-docs.bea.com/platform/docs81/confgwiz/newdom.html#devprod.
  • When the log file is rolled over, the archived file will change its extension to .logXXXXX (e.g., myserver.log00001), even while transaction logs (for example) will use the more appropriate myserver.XXXX.tlog. This is especially challenging to the Windows administrators, where the file extension mappings are very important.
  • To find the beginning of the log (e.g., to check the version info), the best line to search for in WebLogic Server 5.1 through WebLogic Server 7.0 is "FileLogger". As in:

    ####<29/10/2003 7:53:49> <Info> <Logging> <arafalov01> <myserver>
    <main> <> <> <000000> <FileLogger Opened.>

  • WebLogic 8.1 has improved its internationalization and it is now unwise to rely on the text message itself. The message ID is a better reference. BEA-170019 is WebLogic 8.1's equivalent to the FileLogger and will usually read as shown in Listing 4.
Conclusion
Do you know what you run right now? Perhaps not all aspects, but with a solid knowledge of how to detect the exact server version and a handy reference to the location of all the log files, you're on your way to becoming the Master of WebLogic. Good luck!

More Stories By Alexandre Rafalovitch

Alexandre Rafalovitch is a senior developer relationship engineer with BEA in Sydney Australia, with 13 years of experience in software development and support. He is a Sun Certified Java Programmer, BEA WebLogic Certified Developer and an Introscope 4 Certified Administrator
(Wily Technology). Alexandre's current focus is on Weblogic Server and on tool building for internal and external support use.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
No hype cycles or predictions of a gazillion things here. IoT is here. You get it. You know your business and have great ideas for a business transformation strategy. What comes next? Time to make it happen. In his session at @ThingsExpo, Jay Mason, an Associate Partner of Analytics, IoT & Cybersecurity at M&S Consulting, presented a step-by-step plan to develop your technology implementation strategy. He also discussed the evaluation of communication standards and IoT messaging protocols, data...
The 22nd International Cloud Expo | 1st DXWorld Expo has announced that its Call for Papers is open. Cloud Expo | DXWorld Expo, to be held June 5-7, 2018, at the Javits Center in New York, NY, brings together Cloud Computing, Digital Transformation, Big Data, Internet of Things, DevOps, Machine Learning and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding busin...
Smart cities have the potential to change our lives at so many levels for citizens: less pollution, reduced parking obstacles, better health, education and more energy savings. Real-time data streaming and the Internet of Things (IoT) possess the power to turn this vision into a reality. However, most organizations today are building their data infrastructure to focus solely on addressing immediate business needs vs. a platform capable of quickly adapting emerging technologies to address future ...
Nordstrom is transforming the way that they do business and the cloud is the key to enabling speed and hyper personalized customer experiences. In his session at 21st Cloud Expo, Ken Schow, VP of Engineering at Nordstrom, discussed some of the key learnings and common pitfalls of large enterprises moving to the cloud. This includes strategies around choosing a cloud provider(s), architecture, and lessons learned. In addition, he covered some of the best practices for structured team migration an...
With tough new regulations coming to Europe on data privacy in May 2018, Calligo will explain why in reality the effect is global and transforms how you consider critical data. EU GDPR fundamentally rewrites the rules for cloud, Big Data and IoT. In his session at 21st Cloud Expo, Adam Ryan, Vice President and General Manager EMEA at Calligo, examined the regulations and provided insight on how it affects technology, challenges the established rules and will usher in new levels of diligence arou...
In his Opening Keynote at 21st Cloud Expo, John Considine, General Manager of IBM Cloud Infrastructure, led attendees through the exciting evolution of the cloud. He looked at this major disruption from the perspective of technology, business models, and what this means for enterprises of all sizes. John Considine is General Manager of Cloud Infrastructure Services at IBM. In that role he is responsible for leading IBM’s public cloud infrastructure including strategy, development, and offering m...
In his session at 21st Cloud Expo, Raju Shreewastava, founder of Big Data Trunk, provided a fun and simple way to introduce Machine Leaning to anyone and everyone. He solved a machine learning problem and demonstrated an easy way to be able to do machine learning without even coding. Raju Shreewastava is the founder of Big Data Trunk (www.BigDataTrunk.com), a Big Data Training and consulting firm with offices in the United States. He previously led the data warehouse/business intelligence and B...
Recently, REAN Cloud built a digital concierge for a North Carolina hospital that had observed that most patient call button questions were repetitive. In addition, the paper-based process used to measure patient health metrics was laborious, not in real-time and sometimes error-prone. In their session at 21st Cloud Expo, Sean Finnerty, Executive Director, Practice Lead, Health Care & Life Science at REAN Cloud, and Dr. S.P.T. Krishnan, Principal Architect at REAN Cloud, discussed how they built...
22nd International Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, and co-located with the 1st DXWorld Expo will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud ...
22nd International Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, and co-located with the 1st DXWorld Expo will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud ...
DevOps at Cloud Expo – being held June 5-7, 2018, at the Javits Center in New York, NY – announces that its Call for Papers is open. Born out of proven success in agile development, cloud computing, and process automation, DevOps is a macro trend you cannot afford to miss. From showcase success stories from early adopters and web-scale businesses, DevOps is expanding to organizations of all sizes, including the world's largest enterprises – and delivering real results. Among the proven benefits,...
@DevOpsSummit at Cloud Expo, taking place June 5-7, 2018, at the Javits Center in New York City, NY, is co-located with 22nd Cloud Expo | 1st DXWorld Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait...
Cloud Expo | DXWorld Expo have announced the conference tracks for Cloud Expo 2018. Cloud Expo will be held June 5-7, 2018, at the Javits Center in New York City, and November 6-8, 2018, at the Santa Clara Convention Center, Santa Clara, CA. Digital Transformation (DX) is a major focus with the introduction of DX Expo within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive ov...
SYS-CON Events announced today that T-Mobile exhibited at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. As America's Un-carrier, T-Mobile US, Inc., is redefining the way consumers and businesses buy wireless services through leading product and service innovation. The Company's advanced nationwide 4G LTE network delivers outstanding wireless experiences to 67.4 million customers who are unwilling to compromise on qua...
SYS-CON Events announced today that Cedexis will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Cedexis is the leader in data-driven enterprise global traffic management. Whether optimizing traffic through datacenters, clouds, CDNs, or any combination, Cedexis solutions drive quality and cost-effectiveness. For more information, please visit https://www.cedexis.com.
SYS-CON Events announced today that Google Cloud has been named “Keynote Sponsor” of SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Companies come to Google Cloud to transform their businesses. Google Cloud’s comprehensive portfolio – from infrastructure to apps to devices – helps enterprises innovate faster, scale smarter, stay secure, and do more with data than ever before.
SYS-CON Events announced today that Vivint to exhibit at SYS-CON's 21st Cloud Expo, which will take place on October 31 through November 2nd 2017 at the Santa Clara Convention Center in Santa Clara, California. As a leading smart home technology provider, Vivint offers home security, energy management, home automation, local cloud storage, and high-speed Internet solutions to more than one million customers throughout the United States and Canada. The end result is a smart home solution that sav...
SYS-CON Events announced today that Opsani will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Opsani is the leading provider of deployment automation systems for running and scaling traditional enterprise applications on container infrastructure.
SYS-CON Events announced today that Nirmata will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place on Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Nirmata provides a comprehensive platform, for deploying, operating, and optimizing containerized applications across clouds, powered by Kubernetes. Nirmata empowers enterprise DevOps teams by fully automating the complex operations and management of application containers and its underlying ...
SYS-CON Events announced today that Opsani to exhibit at SYS-CON's 21st Cloud Expo, which will take place on October 31 through November 2nd 2017 at the Santa Clara Convention Center in Santa Clara, California. Opsani is creating the next generation of automated continuous deployment tools designed specifically for containers. How is continuous deployment different from continuous integration and continuous delivery? CI/CD tools provide build and test. Continuous Deployment is the means by which...