Deployment Architecture

Deployment command for App Profile Server

simuvid
Splunk Employee
Splunk Employee

On behalf of one of out customers, I have a concrete qustion regarding the setup of the Splunk for WebSphere App. I reference to the install guide for the app.
On page 23 is shown how to generate an input. Our WebSphere App looks like following: We have an Deployment Manager (DM) on a seperate server and the same is valid for the App Profile. I have found an example to generate an input file for the DM like following:

java -jar CreateInputs.jar -startpath /opt/IBM/WebSphere80ND/AppServer/profiles/ -hostname MyHost -enablenodemetadata -whitelist '.log$|.txt$' -alldmgrprofile

What needs the command to look like for an server, that only includes the App profiles?

Cheers,

Christian Glatschke

0 Karma

vserebryany
New Member

We use the following command on both nodes and dmgr hosts. As you see we use WAS own JVM and we do substitution right away to put custom index name. Blacklist section helps us weed out rolled over logs.

SPLUNK_ADDON_DIR=${SPLUNK_CONFIGS:?}/splunk_forwarder_addon_was
INDEX_NAME=ind_${PROD:?}_${APP_NAME:?}_${ENVID:?}_app

if [[ -d "/opt/IBM/BPM751/WebSphere/AppServer/profiles/" ]] ; then
    /opt/IBM/BPM751/WebSphere/AppServer/java/bin/java \
    -jar $SPLUNK_ADDON_DIR/bin/CreateInputs.jar \
    -startpath /opt/IBM/BPM751/WebSphere/AppServer/profiles/  \
    -hostname $(hostname) \
    -enablenodemetadata -whitelist '\.log$|\.txt$|\.out$' \
    -blacklist 'native_stderr|trace|(SystemErr_|SystemOut_|native_stdout_)[0-9][0-9]\.[0-9][0-9]\.[0-9][0-9]_[0-9][0-9]\.[0-9][0-9]\.[0-9][0-9]\.log$' \
    -alldmgrprofile \
    -print | sed -e 's/index \= websphere/index = '$INDEX_NAME'/g' > $OUT_FILE 
fi  
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...