docmain.css" />
View the list of activation files for currently installed components, clients, and other products managed by Management and Security Server.
Use this panel to upload additional activation files.
NOTE:If you see this message, “Activation files installed on the Management and Security Server do not match those available to emulator client sessions,” resolve the conflict by either
manually copying the activation files installed in the WEB-INF/lib/modules folder of the Administrative Server to the ex/modules folder of the emulator client so the contents of both locations match
or, reinstalling the file using Activate New on the Configure Settings - Product Activation panel.
After purchasing an add-on product or another emulator, you will receive information about downloading the product as an activation file, which has this format:
activation.<product_name>.jaw
Download the activation file and note the download destination.
In the Administrative Console, click Configure Settings - Product Activation.
Click Activate New and browse to the activation file for the product you want to install: activation.<product_name>.jaw
Click the file. The new product is added to the Product list.
If you uploaded a product evaluation file, open the column chooser to view the Expiration date.
Restart your browser to ensure that the Administrative Console is fully updated with the new set of activation files. You do not need to restart the MSS server.
Management and Security Server displays the required configuration settings.
Be sure to Complete the activation.
After the activation files are uploaded, further configuration may be required to complete the installation.
Click your product and follow the steps to complete the activation.
Copy the activation file, activation.security_proxy-<12.6.n>.jaw, into the
/securityproxy/lib/modules folder on each machine where Security Proxy Server is installed.
Start the Security Proxy Server.
To configure the Security Proxy Server, refer to Using the Security Proxy Server (a technical reference in the MSS Help).
Copy the activation file, activation.terminal_id_manager-<12.6.n>.jaw, into the Micro Focus/MSS/server/web//webapps/tidm/WEB-INF/lib/modules folder on each machine where Terminal ID Manager is installed.
Restart the Terminal ID Manager servlet.
If the Terminal ID Manager servlet is running under Tomcat, then restart the Tomcat server.
If the Terminal ID Manager is running under a different application server, follow the procedures for that application server to restart the Terminal ID Manager servlet.
If the Terminal ID Manager does not start, you may need to edit the rweb.properties file in the MSSData directory:
Open About > Product Information. Find the MSS Data Path.
In the MSSData directory, open rweb.properties, and look for this line: idmanagement.enabled=false
If the enabled value is false, change the value to true.
Save the file, and then restart the Terminal ID Manager servlet as described above.
In the Administrative Console, open Configure Settings - Automated Sign-on.
Check Enable automated sign-on to mainframe sessions, and enter the required information See Help for assistance.
See the Automated Sign-On for Mainframe Administrative Guide for the required mainframe configuration.
In the Administrative Console, open Authentication & Authorization.
Click Micro Focus Advanced Authentication, and enter the required information. See Help for assistance.