IBM Announcing GA release of IBM Support Assistant 5.0 Team Server -
That’s right folks, get it while it’s hot! The IBM Support Assistant is the strategic client self-assist tool platform for IBM software. ISA v5 is leaps and bounds above the ISA 4 release from yester-year. The new release provides several deployment mechanisms for your environment, assuring that you can choose the best solution for your needs.
Too many times do I need a good reference of how EJB calls in WebSphere actually work. These two articles provide a great basis of understanding for EJB calls in WebSphere and how WebSphere ORB workload management plays a part in the call flow.
Understanding how EJB calls operate in WebSphere Application Server : http://www.ibm.com/developerworks/websphere/techjournal/0807_pape/0807_pape.html
Comment lines: Ensuring enterprise availability when deploying Enterprise JavaBeans in WebSphere Application Server: http://www.ibm.com/developerworks/websphere/techjournal/1109_col_vanrun/1109_col_vanrun.html
Increasing Resiliency for IBM WebSphere Application Server Deployments -
In my tenure with the IBM WebSphere Foundation SWAT team, we’ve seen many scenarios in which customers, unfortunately and for lack of a better term, shoot themselves in the foot either with the products they use or with their processes and design choices.
To bring about awareness of these scenarios, the SWAT team wrote a guide in 2009 that exposed these malpractices and explained how to mitigate them to avoid these costly mistakes, saving the business bottom-line.
Today, I’m happy to announce that we’ve converted the old guide document into IBM RedPaper format (complete with an EPUB - how spiffy is that?).
Whether you’re a WebSphere Application Server owner/user/admin/developer/whatever or you’re using other JEE middleware, have a look into this insightful document and see if your business is committing these malpractices and take the right steps to correct them before you suffer another costly outage!
Sprint endorsement of IBM DataPowerXC10 appliance -
By using the IBM WebSphere DataPower XC10 Appliance solution, Sprint has been able to keep up with the increasing demand of it’s customers needs. Sprint endorsement of IBM DataPowerXC10 appliance Sprint says DataPower is perfect to “quickly scale” and runs super fast transaction with 16 milliseconds response time, wow, that’s fast! Check the video for more!
Looking into solving some of your business IT problems with an elastic caching solution? Look no further than the IBM DataPower XC10 caching appliance! Check out this success story from Sprint…
New IBM Redbook Draft available for WebSphere eXtreme Scale v8.6: -
If you are a current WXS user or just looking into the elastic caching offerings provided by IBM and you’re looking for information about the latest and greatest that WXS has to offer then take a look at this new IBM Redbooks publication (in draft) and let us know what you think.
I enjoyed creating this revision and working with the team assembled as much as writing the original book as well.. Interested in writing an IBM Redbook publication? Check out the details here: http://www.redbooks.ibm.com/residents.nsf/ResIndex/
I do a lot of work with Eclipse and IBM WebSphere products. On the Windows platform there is a path limitation of 260 chars. This can be problematic if you decide to use a directory structure like so for your Eclipse install or workspaces:
You probably won’t see any operational problems for the most part; I never do. My problems start when I try to backup my Eclipse workspaces with a tool that preserves the directory path to the workspace files in the backup archive. This quickly eats up 260 characters and often causes problems.
To get around this limitation, you can utilize the mklink tool provided with Windows. mklink is described by Windows as:
Creates a symbolic link.
MKLINK [[/D] | [/H] | [/J]] Link Target
/D Creates a directory symbolic link. Default is a file
/H Creates a hard link instead of a symbolic link.
/J Creates a Directory Junction.
Link specifies the new symbolic link name.
Target specifies the path (relative or absolute) that the new link
In layman’s terms, it creates a directory linkage that allows you to put a marker at a more convenient place (such as the root of the drive, e.g. C:\) and have that point to another place on the disk. Ere-go, the aforementioned path could be reduced to C:\Eclipse or C:\Juno-sr2. This should prevent all but the longest paths from becoming a problem when backing them up or trying to copy them from one disk to another.
Been thinking of trying out WebSphere eXtreme Scale? Here's 19 reasons you should. -
Check out what’s new in v8.6 of WebSphere eXtreme Scale. Whether you’re looking at updating from a previous version or looking to make a jump into elastic enterprise-level caching, you can’t go wrong with v8.6. Go grab a trial copy today.
Also, follow @ElasticCaching if interested in WebSphere eXtreme Scale.
I like WebSphere Liberty and I think you should, too.. -
The IBM WebSphere Liberty Profile runtime is a highly composable JEE server that is also modular and extremely easy to deploy and work with. Hit the link and give it a whirl!
Want to move a WebSphere profile from one host to another? -
Today I found myself needing to do just this. I isolate my development environment in a KVM guest (running Win7) and, due to some issues with my employer’s default Win7 image and the RedHat QXL video drivers, I needed to create a ‘vanilla’ Win7 image from scratch. In this development environment I have Websphere 7.0, 8.0, 8.5, and Liberty installed. Both the WAS 8 and 8.5 installations had several profiles created as well. I stumbled across this article written my my colleague Tom Alcott and I was able to easily migrate 4 WAS profiles from my old development environment over to my new KVM guest pretty easily. Just follow the instructions verbatim!
If you’ve used JBoss or some other Java application servers you’ve probably seen that EJB’s can be invoked via RMI-JRMP. And you might possibly have done some testing and seen that EJB invocation via RMI-JRMP is (most times) a ton faster and more efficient than RMI-IIOP. WebSphere, however, only allows for hosted EJB’s to be invoked via RMI-IIOP (through our CORBA-compliant ORB). If you’ve ever found yourself wanting to use the JRMP method for performance reasons, please consider up-voting this Request for Enhancement I created on developerWorks.