5 Reasons to use my services

  1. 1
    WebSphere Author
    You may not know, but I am one of the most well-known WebSphere authors and have several books published.

    IBM WebSphere Application Server 8.0 Administration Guide

    IBM WebSphere Application Server 8.0 Administration Guide

    WebSphere Application Server 7.0 Administration Guide

    WebSphere Application Server 7.0 Administration Guide

  2. 2
    Community Knowledge Transfer
    For many years I have been contributing to the IBM WebSphere community. I continually share insights via my top ranking knowledge sites and blogs.
  3. 3
    WebSphere Training
    I have spend many years training Administrations & Support staff alike on the fundamentals of WebSphere Application Server and related IBM product in the WebSphere brand. If you have any need for training please contact me via Learners International.

    Learners International was founded in 2012 to produce affordable Middleware Training.

  4. 4
    WebSphere Consulting

    Infrastructure Architecture

    Need advice about your WebSphere architectures? I have worked for many clients around the world and so have extensive skills acquired from helping customers plan their WebSphere Application Server environments. I also have many years of SOA and ESB practical, hand on experience.

    Trouble Shooting

    In almost mot my roles I have applied by knowledge and insights of the WebSphere brand, thus helping my customers with not only WebSphere related issue, but also Java and JEE application issues.


    Ask anyone I have worked with I am sticker for documentation. In a world where Knowledge Transfer is paramount, you can be assured I will encourage documentation for any process I am involved with as part of any engagement.

  5. 5

    I pride myself in my ability to communicate. I am an enthusiastic and passionate individual. I strive to do my the best for my clients and the people I work with.

Welcome to the Websphere Blog

Steven Robinson is a JEE specialist consultant focusing on Oracle WebLogic Server, IBM WebSphere Application Server and and RedHat Jboss.

I have created this blog to allow some of my knowledge to spill out into the JEE community. As a result of many years as an IT consultant, I have helped many organization’s in both Europe and the United States of America, to sort out issues and problems with Java-based application-server platforms.

I provide expertise in the following areas.

  • Training and knowledge transfer
  • Advanced Jython scripting
  • Java debugging and general JEE problem solving
  • JEE Application packaging
  • Server build including Build/Deploy automation such as Continuous Integration
  • Mobile application provisioning
  • JMS and WMQ Messaging (Internal and External)
  • WebServices, SOA and ESB

Use the blog to learn about the three big JEE Application Server platforms: IBM WebSphere Application, Oracle WebLogic Server and RedHat JBoss. Looking through these pages within you will find Tutorials, answers to common questions and sample scripts.

To suggest content you can reply to my JEE Topic Suggestions page or post questions to my FAQ page.

Cheers, Steve

Recent posts in my IBM WebSphere knowledege base

[important]This article is a snippet from my training course content[/important] [notice]You can get the rest of the series from http://www.webspheretrainer.com/category/websphere-application-server-network-deployment/job-manager/[/notice] Introduction to the Job Manager A Deployment Manager configured in a Network Deployment environment maintains a centralized repository of all the configuration of the resources in the cell. Any changes to the configuration made through.. read more →

When a WXS ENV was created FQDN for some DNS was wrong.  DNS entries for a catalog server  and a container  server  wrong, because the LPARS had been built at a later date to the other nodes in the cell. So when the nodes were federated, WAS recorded the results of DNS resolver on the.. read more →

When the Catalog (cat) Node04 was created, the DNS was wrong. This means that when the catalog service domain was created the DMGR did a reverse look-up to find the FQDN for the cat 04’s IP Address. At that time it got it wrong. So essentially it stored the dat04’s (WXS Container 04) hostname as.. read more →

This error occurs when you have one container server left and you stop that server and start it up quickly after stopping it. The issue is that the catalog server doesn’t know it went down yet. It can take up to 30 to 40 seconds to detect the server went down depending on your.. read more →

I posted this article http://blog.webspheretools.com/2012/02/18/steve-robinson-legend/ 45 minutes later it was #1 and #2 in Google? Lets see if this is real or not over the coming weeks. If it still #1 in 7 days then I guess it must be true? read more →

I posted this article http://blog.webspheretools.com/2012/02/18/steve-robinson-legend/ And two minutes later it was #1 in Google? Lets see if this is real or not over the coming weeks. If it still #1 in 7 days then I guess it must be true? read more →

I am posting this post to see how long it takes for Google to rank me #1 for his key word “Steve Robinson the Legend” I often take the  micky at myself, and try to have a bit of fun more these days. I am often very serious and spend all my time publishing information.. read more →

15 Feb 2012
February 15, 2012

WebSphere Temp Folders

February 15, 2012 IBM WebSphere Application Server 0 Comment

Often you may need to deal with WebSphere Application Sever temp files. Network Deployment version: Deployment manager temp folder for example: <dmgr_profile_temp>/temp -> mostly Contains expanded information from deployments. Each custom or deployment manager profile stores temporary data in the appropriate directory: <profile_root>/wstemp This directory is primarily used by the WebSphere Application Server workspace management.. read more →

Error: Solution: http://www.webspheretrainers.com/?p=903 read more →

When a WAS cell is created to use the DMGR and NodeAgents for the catalog service, it means that often later in the cycle of the project, the environment may need to be changed to use a cluster with JVMs as the catalog service. The reason for this is that we can stop and start.. read more →