Installation and Configuration Manual

 


A note from us

This documentation does not apply to the most recent version of WAS. Click here for the latest version.

A note from us

April 2012

Welcome to our newest release, Splunk for WebSphere Application Server 2.0. We are excited to have it in your hands. With this release we focused on enhancing the installation and deployment for very large scale environments and we rewrote the documentation.

We want your all-round experience to be great. We have spent a lot of time gathering feedback from you on the earlier product versions. We've been heads down 24/7 developing new features and solving problems and challenges that you've thrown our way. Now we have 2.0! It's easier to deploy and use. We worked on The Plan - our guide to a headache free successful installation. Follow The Plan.

While on the note of headaches, some of you have reported problems when cutting and pasting from code examples in pdf versions of our documentation. There is a potential for error when you cut and paste code from pdf files into your environment and you forget to remove the special characters that come along with the code. If you want to cut and paste, do it from the Wiki. One of these days we'll have a cookbook and life will be easier.

We also want to note that the Wiki is live and we continually update content and fix issues that we find. We can't do this with your pdf doc (we would if we could). Always make sure that you are using the latest version of the documentation.

We hope this helps. If there's something else we need to share, we want you to let us know by emailing us with you comments and feedback directly at websphere@splunk.com.

in the meantime...
Happy Splunking!

This documentation applies to the following versions of WAS: 2.0 View the Article History for its revisions.


Comments

links pointed by The Plan are broken

Mzorzi, Splunker
May 14, 2012

You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!