Append host name to cmdb_ci_app_server_websphere recordsIssue The records in the table cmdb_ci_app_server_websphere have common names like server1, nodeagent etc that would make the records look like duplicates although they belong to different websphere processes and CIs.ReleaseAllCauseOOB discovery populates websphere class records with the name that is present in "last parameter" of the process com.ibm.ws.runtime.WsServer. For example, the ...com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer process which is seen in the ADM input probe has a parameter of /opt/IBM/WPS/profiles/ccmdb/config localhostNode01Cell ccmdb01 server1. The values are: last parameter = server_name = server1last parameter - 1 = node_name = ccmdb01last parameter - 2 = cell_name = localhostNode01Celllast parameter - 3 = config_path = ‘/opt/IBM/WPS/profiles/ccmdb/config’ Some customer would like to have the host server name to be appended to websphere name for further simplicity like the current OOB naming convention for Tomcat@server_name Resolution1) The name on the records of the class - cmdb_ci_app_server_websphere is populated by the Process Classifier script - Websphere Serverhttps://<instance_name>.service-now.com/nav_to.do?uri=discovery_classy_proc.do?sys_id=7b91cd39c0a80fd0005a079e03a09b0d 2) The line 46 on the Classfication script is setting the name on the server record:current.name = result[3];3) This sets the server name from the Process parameter after extracting the last parameter of the below line obtained via ADM probe that is considered as name on the cmdb_ci_app_server_websphere record ("server1") : /opt/IBM/WPS/profiles/ccmdb/config localhostNode01Cell ccmdb01 server1 4) Add a new variable in the script:var computerName = g_sensor.deviceGR.name;5) Append the line 46 with this variable as below:current.name = result[3] + "@" + computerName;6) Run the discovery again and you could notice the record name changed to server1@computer_name