Configure these settings for using Management and Security Server.
The volume purchase agreement (VPA) number appears in the client’s About box and is used by the Metering server. If the VPA is unspecified, it is reported as 00000 in the emulator and in metering reports.
If you did not enter your number during installation, you can add it here.
You can enter up to 45 characters to identify this Administrative Server. This name is helpful for debugging in larger environments where more than one Administrative Server is behind a load balancer. In these cases, it can be difficult for the client to determine which Administrative Server is being accessed.
This string is printed in the Java console.
You can create your own login/links list page and store it separately from the installed default page. The page can have any custom content desired, including graphics, links, or JavaScript.
If you specify a custom login page here, the custom page jsp must be stored on the server in the templates folder directly or in a subfolder. A sample custom login page is available in the MSS/server/web/webapps/mss/templates/samples folder, along with some other samples for dynamic embedded sessions.
If the custom login page is not found under the templates folder, the default login page is displayed. If you are developing a custom login page and have trouble getting it to display properly, you may not be able to access the Administrative Console to change the custom page specification. Rename the custom page in the templates folder, and the default page will be used.
The Reflection for the Web Launcher is a private client-side application that eliminates the need for Oracle’s JRE or the Java plug-in. This feature is available with Reflection for the Web 13.0 and higher.
See Using the Reflection for the Web Launcher (in the Reflection for the Web Installation Guide) for details about the Launcher, the deployment options, and the expected user experience.
Three deployment options are available to accommodate your environment’s readiness to transition away from Oracle’s JRE and/or the Java plug-in and begin using the Reflection for the Web Launcher.
NOTE: In Reflection for the Web versions prior to 13.0, the Hybrid and Launcher options are disabled.
Select the Standard option until you are ready to move away from Oracle’s JRE or the Java plug-in.
The user experience is the same as with previous versions of Reflection for the Web, which rely on the Java browser plug-in and its legacy JNLP (Java Network Launch Protocol) behavior to launch the links list and Reflection for the Web sessions (before version 13.0).
Select the Hybrid option for a phased rollout. As you transition away from the Java browser plug-in and/or Oracle’s JRE, you can roll out Reflection for the Web Launcher to subsets of users.
In the hybrid environment, the user’s setup determines whether Reflection for the Web sessions are launched using either the Standard or the Launcher method.
Standard is used if the user still has the Java browser plug-in. Sessions are launched as they were in previous versions of Reflection for the Web.
Launcher is used when the Reflection for the Web Launcher is installed on a user’s workstation. Sessions are launched using JNLP instead of the Java browser plug-in.
When Hybrid is selected, you have the option to show authenticated users a link to download the Reflection for the Web Launcher Installer.
Select the Launcher option when you are ready to completely transition away from the Java plug-in and/or Oracle’s JRE — and Management and Security Server is being used only for Reflection for the Web emulation.
The Launcher option exclusively uses the Reflection for the Web Launcher, which uses JNLP to launch sessions. Oracle’s Java browser plug-in cannot be used to launch the links list or terminal sessions. When Launcher is selected, you have the option to show authenticated users a link to download the Reflection for the Web Launcher Installer.
NOTE:If the Launcher option is selected and Management and Security Server is used to manage other Micro Focus emulator clients, such as Reflection Desktop, then the end users will experience behavior as if the Hybrid option was selected.
For details about the Deployment Options and the resulting user experience, see the Reflection for the Web Installation Guide.
Check this box to enable individuals to download the Reflection for the Web Launcher, when either Hybrid or Launcher is selected.
When Show link to download the Windows-based installer for the Reflection for the Web Launcher is checked, the user sees a link to manually download the .msi file for the Reflection for the Web Launcher Installer — after they authenticate to MSS.
This one-time option sets up the workstation with the Reflection for the Web Launcher. After the Reflection for the Web Launcher is installed, the user can ignore the download link.
For further distribution details and the expected user experience, see Using the Reflection for the Web Launcher (in the Reflection for the Web Installation Guide).
NOTE:JRE security updates will be provided via an updated .msi file in Reflection for the Web product updates.
Use the OBJECT/EMBED tag to resolve issues for specific browsers:
Use the OBJECT tag to deploy applets that are to be used only with Internet Explorer.
Use the EMBED tag to deploy applets that are to be used only with the Mozilla family of browsers.
You can specify the URL for the OBJECT codebase attribute and the EMBED pluginspage attribute, which is used to download the latest JRE when no JRE is present on the machine. And, you can specify the location if you want to distribute the JRE from an alternate location.
NOTE:The <applet> HTML tag was deprecated in HTML 4.01.
The APPLET tag option has no effect when using the Launcher option to deploy Reflection for the Web Launcher settings.
A direct link is a URL that opens the specified session after the user authenticates. Check Show links list for direct sessions if you want users to see a list of links to their entitled sessions when you provide a direct link to a session.
This setting applies only to sessions that are configured to launch in a frame outside of the browser page.
NOTE:Java version detection is disabled by default to provide faster startup of sessions on the client. When Java detection is enabled, users are informed when their Java version is unsupported by the product.
The specific version of Java detected is also used to configure applet parameters that help manage the behavior of sessions when navigating away from and back to the web page.
To enable Java version detection, edit this configuration file:
Open /mssdata/propertyDS.xml.
Change the enableJavaVersionDetection value from false to true:
<CORE_PROPERTY NAME="enableJavaVersionDetection">
<BOOLEAN> true </BOOLEAN>
</CORE_PROPERTY>
Save the file.