Documentation > Splunk for WebSphere Application Server > Installation and Configuration Manual > Upgrade to a new release

Installation and Configuration Manual

 


Introduction
Core concepts
Best practices
Plan your deployment
Installation Tools
Download Splunk for WAS
Install Splunk for WAS
Validate your install
Upgrade
  • Upgrade to a new release
Configuration File Reference

Upgrade to a new release

Contents

Upgrade to a new release

Upgrade from Splunk for WebSphere 2.0 to release 2.0.1

If you have the 2.0 software version installed and deployed in your environment , you can perform an in-place upgrade.

The individual components of the Splunk for WebSphere Application Server (WAS) Solution are described on the Product Web page with links to Splunkbase, where you can download each of them. Go to the Product Web page to download the Solution. Download each of the solution components to a shared folder on your network, then install each component.

Upgrade Splunk App for WAS

Note

  • If your Splunk search head has internet access, use the Management UI to perform an upgrade.
  • If your search head does not have internet access, follow the instructions below.

Important: If your Splunk environment uses Deployment Server for indexer app replication, please contact your Splunk designated Sales Engineer or Professional Services representative for assistance.

To upgrade to the latest Splunk App for WAS on the indexer/search head:

  1. Stop the Splunk instance.
  2. Unpack the App, splunk_app_was-2.0.1-131157.tar.gz file directly to $SPLUNK_HOME/etc/apps directory. For example, in a linux environment use the commands:
    sudo gunzip <filename>.tar.gz
    sudo tar -xvf <filename>.tar
  3. For windows, download a third party tool such as WinRAR to unpack a tar.gz file.
  4. Copy the contents of your /local folder and your /lookups folder back to your latest installation.
  5. Start the Splunk instance.

Upgrade the Splunk FA add-on for WAS

Note: The FA Add-on for WAS contains configuration files and installation scripts that help create the Splunk FA add-on for WAS inputs.conf file. These files have the exact same names as those in the /local folder of the new installation. To preserve your current configuration you must create a copy of the current version of your local folder before upgrading to the next version.

To upgrade the Splunk FA add-on for WAS on the Splunk forwarder on the box collecting JMX data.

For each WAS box that has a Splunk forwarder running:

  1. Make a copy of your $SPLUNK_HOME/etc/apps/splunk_fa_addon_was/local folder so that when you install the latest version of the product you can preserve your configuration changes in the files was_fa.conf and was_dmgr.conf.
  2. Stop Splunk.
  3. Unpack the FA add-on, splunk_fa_addon_was-2.0.1-131125.tar.gz to another location that is not the installation location
  4. Install the 2.0.1 release version.
  5. Copy the contents of the /local folder back to the latest installed version.
  6. Start the forwarder (start Splunk).

Upgrade the Splunk Forwarder Add-on for WAS

To upgrade the Splunk Forwarder Add-on for WAS on the Splunk forwarder on each WAS box from which you want to get log data.

  1. Stop the forwarder on the WAS box
  2. Unpack the forwarder add-on, splunk_forwarder_addon_was-2.0.1-131278.tar.gz into the $SPLUNK_HOME/etc/apps directory
  3. Start the forwarder (start Splunk) on the WAS box.
Retrieved from "http://docs.splunk.com/Documentation/WAS/2.0.1/InstallGuide/Upgradetoanewrelease"

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


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!