IBM Support

How to use multiple URLPrefix for PowerShell connection to discover Windows targets in TADDM?

How To


Summary

TADDM can use multiple URLPrefix for PowerShell connection on Windows target.

Steps

By default TADDM use "wsman" as prefixURL for PowerShell connections. 
There are two ways to achieve this functionality.
Method 1: By restricting Scope-set/IP on below property in collation.properties file so that windows targets using different URLs for PowerShell can be discovered:
com.ibm.cdb.session.ps.urlPrefix
Below are the examples for using the property:
com.ibm.cdb.session.ps.urlPrefix.<scopename1>=wsabc
com.ibm.cdb.session.ps.urlPrefix.<scopename2>=wsdef
com.ibm.cdb.session.ps.urlPrefix.<172.20.x.x>=wsghi
Note - Default value of this property:
com.ibm.cdb.session.ps.urlPrefix=wsman
Method 2: Contact TADDM support for providing efix for APAR - IJ18732
APAR Details: TADDM TO SUPPORT FALLBACK OPTION FOR URLPREFIXES FOR CONNECTIVITY THROUGH POWERSHELL.
Reference URL: http://www-01.ibm.com/support/docview.wss?crawler=1&uid=swg1IJ18732
By applying this efix, multiple URL Prefixes can be specified using below property in collation.properties file on TADDM.
com.ibm.cdb.session.ps.urlPrefix
If one prefix fails for PowerShell connection, TADDM will try the next one. Multiple prefixes can be added with "," as separator.
Below is the example for using the property:
com.ibm.cdb.session.ps.urlPrefix=wsabc,wsman,wsghi
*TADDM supported version for this APAR - 7.3
The fix for this APAR will be included in FP7

Document Location

Worldwide

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 January 2020

UID

ibm11125171

Page Feedback