The User uploaded the CES started task output into that case looking for some explanation. Upon further review, The User believes the logging class not found is probably not a showstopper since it seems to default to a different implementation, but there does seem to be a port issue that we need clarification on. ======================================== When a customer site is focused on getting a connection to the HCI 16196 port, it appears that the request is making it through some of the firewalls, but nothing is being returned. Could the security or configuration around this setting be blocking the connection? How do customers configure this line below in the HCI00 Parmlib member? APPLICATION=TZPROD SECURITY APPL PROFILE NAME |
Recommendation to customers: Customers will have to use the available ports during CES (Common Enterprise Services) installation specified in our documentation. (Click on the link to our BMC Support Central website for more information on: BMC AMI Web Products Installation & Configuration Guide) The customer will have to select option "1-> OK" and provide alternative port instead of selecting option "2-> Ignore". =================================== Please see information below regarding the parameter, APPLICATION=TZPROD SECURITY APPL PROFILE NAME for the HCI00 member: Details about APPLICATION= parameter can be found here https://docs.bmc.com/docs/pages/viewpage.action?pageId=995986583 Description of APPLICATION = parameter: The APPLICATION statement identifies an application profile name also known to the system security software which can optionally be used to further restrict access to the TP port to specific users or groups. User access to this TP port can be restricted by use of an APPL class profile if it is supported by your security software (such as RACF). To use an APPL class profile to restrict access to certain users or groups, specify an application name. The name can be any name you choose to represent the port or system on which this TP is executing, for example WBPROD, WBTEST, or CXTP01. Then add the chosen name as a profile in the APPL class to your security software database. User access can then be controlled by assigning user IDs or groups to have READ access to that profile. Users or groups that do not have READ access will not be permitted to use the port and their BMC AMI DevX Workbench for Eclipse session will be terminated. If the APPLICATION profile name is not specified, then access to the TP port is based on user ID and password authentication only. This is the default action and is consistent with the behavior of all prior releases of BMC AMI DevX Workbench for Eclipse. Therefore, most installations should not specify an APPLICATION profile name and allow user authentication based on user ID and password only. |