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
From 2013, NTT Communications has been providing cPaaS service, SkyWay. Its customer’s expectations for leveraging WebRTC technology are not only typical real-time communication use cases such as Web conference, remote education, but also IoT use cases such as remote camera monitoring, smart-glass, and robotic. Because of this, NTT Communications has numerous IoT business use-cases that its customers are developing on top of PaaS. WebRTC will lead IoT businesses to be more innovative and address...
When shopping for a new data processing platform for IoT solutions, many development teams want to be able to test-drive options before making a choice. Yet when evaluating an IoT solution, it’s simply not feasible to do so at scale with physical devices. Building a sensor simulator is the next best choice; however, generating a realistic simulation at very high TPS with ease of configurability is a formidable challenge. When dealing with multiple application or transport protocols, you would be...
SYS-CON Events announced today that App2Cloud 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. App2Cloud is an online Platform, specializing in migrating legacy applications to any Cloud Providers (AWS, Azure, Google Cloud).
IoT is at the core or many Digital Transformation initiatives with the goal of re-inventing a company's business model. We all agree that collecting relevant IoT data will result in massive amounts of data needing to be stored. However, with the rapid development of IoT devices and ongoing business model transformation, we are not able to predict the volume and growth of IoT data. And with the lack of IoT history, traditional methods of IT and infrastructure planning based on the past do not app...
Internet-of-Things discussions can end up either going down the consumer gadget rabbit hole or focused on the sort of data logging that industrial manufacturers have been doing forever. However, in fact, companies today are already using IoT data both to optimize their operational technology and to improve the experience of customer interactions in novel ways. In his session at @ThingsExpo, Gordon Haff, Red Hat Technology Evangelist, shared examples from a wide range of industries – including en...
To get the most out of their data, successful companies are not focusing on queries and data lakes, they are actively integrating analytics into their operations with a data-first application development approach. Real-time adjustments to improve revenues, reduce costs, or mitigate risk rely on applications that minimize latency on a variety of data sources. Jack Norris reviews best practices to show how companies develop, deploy, and dynamically update these applications and how this data-first...
Intelligent Automation is now one of the key business imperatives for CIOs and CISOs impacting all areas of business today. In his session at 21st Cloud Expo, Brian Boeggeman, VP Alliances & Partnerships at Ayehu, will talk about how business value is created and delivered through intelligent automation to today’s enterprises. The open ecosystem platform approach toward Intelligent Automation that Ayehu delivers to the market is core to enabling the creation of the self-driving enterprise.
"We're a cybersecurity firm that specializes in engineering security solutions both at the software and hardware level. Security cannot be an after-the-fact afterthought, which is what it's become," stated Richard Blech, Chief Executive Officer at Secure Channels, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Consumers increasingly expect their electronic "things" to be connected to smart phones, tablets and the Internet. When that thing happens to be a medical device, the risks and benefits of connectivity must be carefully weighed. Once the decision is made that connecting the device is beneficial, medical device manufacturers must design their products to maintain patient safety and prevent compromised personal health information in the face of cybersecurity threats. In his session at @ThingsExpo...
SYS-CON Events announced today that Grape Up 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. Grape Up is a software company specializing in cloud native application development and professional services related to Cloud Foundry PaaS. With five expert teams that operate in various sectors of the market across the U.S. and Europe, Grape Up works with a variety of customers from emergi...
Detecting internal user threats in the Big Data eco-system is challenging and cumbersome. Many organizations monitor internal usage of the Big Data eco-system using a set of alerts. This is not a scalable process given the increase in the number of alerts with the accelerating growth in data volume and user base. Organizations are increasingly leveraging machine learning to monitor only those data elements that are sensitive and critical, autonomously establish monitoring policies, and to detect...
SYS-CON Events announced today that Massive Networks 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. Massive Networks mission is simple. To help your business operate seamlessly with fast, reliable, and secure internet and network solutions. Improve your customer's experience with outstanding connections to your cloud.
Because IoT devices are deployed in mission-critical environments more than ever before, it’s increasingly imperative they be truly smart. IoT sensors simply stockpiling data isn’t useful. IoT must be artificially and naturally intelligent in order to provide more value In his session at @ThingsExpo, John Crupi, Vice President and Engineering System Architect at Greenwave Systems, will discuss how IoT artificial intelligence (AI) can be carried out via edge analytics and machine learning techn...
Everything run by electricity will eventually be connected to the Internet. Get ahead of the Internet of Things revolution and join Akvelon expert and IoT industry leader, Sergey Grebnov, in his session at @ThingsExpo, for an educational dive into the world of managing your home, workplace and all the devices they contain with the power of machine-based AI and intelligent Bot services for a completely streamlined experience.
In the enterprise today, connected IoT devices are everywhere – both inside and outside corporate environments. The need to identify, manage, control and secure a quickly growing web of connections and outside devices is making the already challenging task of security even more important, and onerous. In his session at @ThingsExpo, Rich Boyer, CISO and Chief Architect for Security at NTT i3, discussed new ways of thinking and the approaches needed to address the emerging challenges of security i...
SYS-CON Events announced today that Datera, that offers a radically new data management architecture, has been named "Exhibitor" 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. Datera is transforming the traditional datacenter model through modern cloud simplicity. The technology industry is at another major inflection point. The rise of mobile, the Internet of Things, data storage and Big...
SYS-CON Events announced today that GrapeUp, the leading provider of rapid product development at the speed of business, will exhibit at SYS-CON's 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. Grape Up is a software company, specialized in cloud native application development and professional services related to Cloud Foundry PaaS. With five expert teams that operate in various sectors of the market acr...
SYS-CON Events announced today that CA Technologies has been named "Platinum Sponsor" of SYS-CON's 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. CA Technologies helps customers succeed in a future where every business - from apparel to energy - is being rewritten by software. From planning to development to management to security, CA creates software that fuels transformation for companies in the applic...
Internet of @ThingsExpo, taking place October 31 - November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 21st Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The Internet of Things (IoT) is the most profound change in personal and enterprise IT since the creation of the Worldwide Web more than 20 years ago. All major researchers estimate there will be tens of billions devic...
In his opening keynote at 20th Cloud Expo, Michael Maximilien, Research Scientist, Architect, and Engineer at IBM, discussed the full potential of the cloud and social data requires artificial intelligence. By mixing Cloud Foundry and the rich set of Watson services, IBM's Bluemix is the best cloud operating system for enterprises today, providing rapid development and deployment of applications that can take advantage of the rich catalog of Watson services to help drive insights from the vast t...