Splunk Search

websphere missing conf file wsadminCommands.conf

troyrose
New Member

websphere missing conf file wsadminCommands.conf referenced by scripted input file /opt/splunk/etc/apps/SplunkWAS/bin/WebSpherewsadminLauncher.py causes errors to be logged and no metrics are gathered.

Tags (1)
0 Karma

hotsplunk
New Member

problem is this; if you don't want to authenticate to JMS/JMX (or you do and you enter the wrong username and/or password) on the setup page for this app, then this file never gets created (yes, this file gets created at setup time) .. you have to start over from the beginning, trying to retrofit anything after this step doesn't create this file and thus it wont work ..

0 Karma

Curt_Collins
Splunk Employee
Splunk Employee

I'm not quite sure I understand this description. What do you mean by "you have to start over from the beginning"? Can you provide some repro steps?

0 Karma

perlguy9
New Member

I'm running into this same problem after performing the GUI setup.

0 Karma

borshinw
Engager

Websphere app require GUI setup before you can collect any metrics. You can go to the manager and click setup under the name splunkwas.

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!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...