Profile Node

Profiles contain the rendering mode, environment settings, and specific browser plug-ins to be used in rendering content. To create a new Profile, use the Actions Pane ‘Add’ item.

The Actions Pane includes the Delete, Copy, Cut, Paste items which are helpful when working on a project populated with several Profiles. The Copy, Cut and Paste items integrate with the system clipboard and are especially useful when working with multiple Ion Configuration Manager instances loaded with unique project files.

[]{#_Browser_Engine_Selection .anchor}

Profile Type Selection

Profiles are the basis for all Ion settings management. To start any type of Ion managed configuration, the first step is to select which type of Profile to create. Ion offers three types of Profiles:

• Global Java Profile

• Enterprise Mode Profiles

• Standard Ion Profiles

Global Java Profile

Global Java Profiles are designed for Ion configurations which ONLY require Java version management. A Global Java Profile cannot modify or manage any other browser settings. Selecting this Profile type will launch the Java Wizard, which guides the Java management process and settings.

Enterprise Mode Profiles

Enterprise Mode Profiles can be created and managed within the Ion Configuration Manager. Unlike Standard Ion Profiles, Enterprise Mode Profiles simply enable the Microsoft Enterprise Mode feature.

Enterprise Mode Profiles are ‘limited’, in that no other browser settings can be modified or managed. For example, no Java management is possible with an Enterprise Mode Profile selection.

Standard Ion Profiles

Standard Ion Profiles are the most flexible and powerful type of Profile available. To being, select the Rendering Mode that most Rendering modes are a collection of settings, anchored by Internet Explorer Document Modes, designed to provide maximum backward compatibility for business applications that require legacy versions of Internet Explorer. This screen shows the available rendering mode templates:

This chart provides a list of the Internet Explorer rendering modes accessible by Ion:

+-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Rendering Mode | Description | +=============================+===========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+ | Default | This creates an empty Profile with no Document Mode or customized values. All settings are default settings or blank values. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion Adaptive IE Quirks Mode | Renders content by dynamically selecting either the IE7 Standards or Quirks Mode rendering behavior based on the presence and location of a DOCTYPE on the page. Pages will be rendered using the IE7 Standards behavior if the page contains a DOCTYPE in the 1^st^ position (no text preceding the declaration) and that DOCTYPE declaration is anything other than ‘QUIRKS’. Pages will be rendered using the Quirks Mode behavior if the page has no DOCTYPE declaration, expressly includes a QUIRKS DOCTYPE declaration or if the DOCTYPE declaration is NOT in the 1^st^ position. | | | | | | In either case the IE6 UA string is declared regardless of which rendering Mode is selected. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion Emulate IE7 Mode | Standards Mode directives are displayed in Internet Explorer 7 Standards Mode and Quirks Mode directives are displayed in IE5 Mode. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion Emulate IE8 Mode | Standards Mode directives are displayed in Internet Explorer 8 Standards Mode and Quirks Mode directives are displayed in IE5 Mode. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion Emulate IE9 Mode | Standards Mode directives are displayed in Internet Explorer 9 Standards Mode and Quirks Mode directives are displayed in IE5 Mode. | | | | | | Note: This Profile will default to the highest available version of IE Standards Mode engine on systems running versions lower than IE9. E.g. IE8 systems will use IE8 Standards Mode. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion Emulate IE10 Mode | Standards Mode directives are displayed in Internet Explorer 10 Standards Mode and Quirks Mode directives are displayed in IE5 Mode. | | | | | | Note: This Profile will default to the highest available version of IE Standards Mode engine on systems running versions lower than IE10. E.g. IE8 systems will use IE8 Standards Mode, IE9 systems will use IE9 Standards Mode, etc. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion IE Quirks Mode | Renders content as if it were displayed in Quirks Mode by Internet Explorer. IE Quirks is similar to the rendering behavior in IE 5.5. This Profile can be used to force a web application to render using ‘Quirks’ Mode directives. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion IE Edge Mode | To plan for future browser version continuity, Ion includes the ‘Default IE Edge Mode Profile’ to enable rules to always use the default (latest) browser engine installed on the system. | | | | | | Note: Ion supports multiple versions of IE (8, 9, 10). Customers are advised to use caution in selecting this value as it will have important behavioral, rendering and scripting differences when used on different Internet Explorer versions. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion IE7 Standards Mode | Renders content as if it were displayed in Standards Mode by Internet Explorer 7. This Profile can enable scenarios where a web application renders properly using the IE8’s ‘IE7 Mode’ but the given line-of-business application may require granular setting configurations that are not possible or appropriate changes to make globally to the IE8 browser configuration. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion IE8 Standards Mode | Renders content as if it were displayed in Standards Mode by Internet Explorer 8. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion IE9 Standards Mode | Renders content as if it were displayed in Standards Mode by Internet Explorer 9. | | | | | | Note: This Profile will default to the highest available version of IE Standards Mode engine on systems running versions lower than IE9. E.g., IE8 systems will use IE8 Standards Mode. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Ion IE10 Standards Mode | Renders content as if it were displayed in Standards Mode by Internet Explorer 10. | | | | | | Note: This Profile will default to the highest available version of IE Standards Mode engine on systems running versions lower than IE10. E.g. IE8 systems will use IE8 Standards Mode, IE9 systems will use IE9 Standards Mode, etc. | +-----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Any Profile can be modified to suit specific web application compatibility issues. For example, Ion makes it possible to specify different versions of the Java Runtime Environment (JRE) on a per-Profile basis, whereas changing the JRE version for Internet Explorer globally would only allow for a single version to be loaded at a time.

Care should be used when selecting IE Edge, Emulate IE9, Emulate IE10, IE9 Standards and IE10 Standards since the rendering engines, and therefore rendering behavior, will be very different when the Profile is invoked on systems running Internet Explorer versions lower than the mode specified.

This table shows the specific document mode that will be invoked in each Rendering Mode:

---

Rendering Mode If IE8 is installed If IE9 is installed If IE10 is installed If IE11 is installed

---

Default IE8 Standard Mode IE9 Standards Mode IE10 Standards Mode IE11 Standards Mode

Ion Adaptive IE Quirks IE8 Quirks Mode or IE7 Standards Mode (as evaluated by DOCTYPE) IE9 Quirks Mode or IE7 Standards Mode (as evaluated by DOCTYPE) IE10 Quirks Mode or IE7 Standards Mode (as evaluated by DOCTYPE) IE11 Quirks Mode or IE7 Standards Mode (as evaluated by DOCTYPE)

Ion Emulate IE7 Mode Emulate IE7 Mode for IE8 Emulate IE7 Mode for IE9 Emulate IE7 Mode for IE10 Emulate IE7 Mode for IE11

Ion Emulate IE8 Mode IE8 Standards Mode Emulate IE8 Mode for IE9 Emulate IE8 Mode for IE10 Emulate IE8 Mode for IE11

Ion Emulate IE9 Mode IE8 Standards Mode IE9 Standards Mode Emulate IE9 Mode for IE10 Emulate IE9 Mode for IE11

Ion Emulate IE10 Mode IE8 Standards Mode IE9 Standards Mode IE10 Standards Mode IE10 Standards Mode

Ion IE Quirks Mode IE8 Quirks Mode IE9 Quirks Mode IE10 Quirks Mode IE11 Quirks Mode

Ion IE Edge Mode IE8 Standards Mode IE9 Standards Mode IE10 Standards Mode IE11 Standards Mode

Ion IE7 Standards Mode IE7 Standards Mode for IE8 IE7 Standards Mode for IE9 IE7 Standards Mode for IE10 IE7 Standards Mode for IE11

Ion Ion IE8 Standards Mode IE8 Standards Mode IE8 Standards Mode for IE9 IE8 Standards Mode for IE10 IE8 Standards Mode for IE11

Ion IE9 Standards Mode IE8 Standards Mode IE9 Standards Mode IE9 Standards Mode for IE10 IE9 Standards Mode for IE11

Ion IE10 Standards Mode IE8 Standards Mode IE9 Standards Mode IE10 Standards Mode IE10 Standards Mode

Profile Editor

The Profile Editor is used to modify settings, values and configurations for a given Profile. Editing a Profile may involve creating or modifying entries in any of the Managers available for each Profile in the Objects pane. To get started, highlight a Profile to view the Profile Properties in the Content Pane. The remainder of section 3.3.5 will walk through the Profile Properties and the managers available for each full Profile.

Full Profiles can access all the Managers used by Ion. Global Java Profiles can only set the desired version of Java for the Profile. None of the Managers or Advanced Profile Settings are available to Global Java Profiles. Global Java Profiles are described in section 3.3.3.

Profile Properties

Profile details (Name, Description, Document Mode, and User Agent String) other than Java Version and Java Platform can be edited on the Profile Properties screen. Java Version and Java Platform are modified via the Java Version Manager. Profiles are assigned default values based on the Rendering Mode template selected when adding a new Profile, or when selecting ‘Change rendering mode’ from the Actions Pane. Most values can be left at defaults, but Name and Description should be edited to reflect information relevant to your web applications and organization. Additional information about each setting is available from the ‘rollover’ information panel display in the Content Pane.

Name — The Profile Name can be modified to suit your remediation project.

Description — The Description field allows for a more complete explanation of the Profile.

Document Mode — Ion allows you to define which Document Mode is included for pages loaded using the specified Profile. Internet Explorer Document Modes are used to trigger different rendering and scripting engine behaviors. The default Document Mode included with each Profile is set based on the rendering mode selected when the Profile is created. The Document Mode can be changed at any time and is exclusive of the rendering mode choice. More information about Document Modes can be found on the MSDN website.

User Agent String — User Agent (UA) String settings let you specify the value passed to a web server by Internet Explorer for a given Profile. Some common web application compatibility issues can be resolved by simply adjusting the UA string values. Using this feature, Profiles can be configured to send the desired UA string without impacting the standard Internet Explorer UA string values. UA strings are defined by the originally selected rendering mode template, but can be changed at any time. More information can be found on the MSDN website.

As a general rule, Profiles created using any of the templates will set the UA string values to the minimum supported platform for the Internet Explorer release on which that rendering mode is designed. For Example, the UA string values for an Emulate IE8 Profile will be set as Windows NT 5.1 (Windows XP version number) as IE8 minimum support starts with Windows XP.Platform token value.

Java Version — Displays the version of Java used in this Profile. The default value is “System Default”, the most current version of Java installed on client PCs. To override the default version of Java with an earlier version, you must change the value in the Java Version Manager.

Java Platform — Displays the architecture for the selected version of Java, either 32-bit or 64-bit.

64-bit Java requires Internet Explorer to be run in a special 64-bit tab process mode. Ion automatically puts Internet Explorer (10 or 11) into this mode when a Profile using a 64-bit version of Java is invoked. However, no 32-bit browser add-ons can be used when in this mode and Ion does not support 64-bit Java in IE8 or IE9. It is therefore recommended that you only use 64-bit Java for applications that have a specific 64-bit requirement.

Browser Platform — Specifies the Browser Platform to be used for rendering sites using this Profile. Options include Auto, Internet Explorer, and Edge Internet Explorer Mode. Choosing the Auto option will load the Profile in the same browser the user originated the request. Selecting Internet Explorer or Edge Internet Explorer Mode will force the Profile to open in the specified browser.

Profiles created with a previous version of Browsium Ion will have Internet Explorer pre-selected as the Browser Platform.

Ion only supports Internet Explorer and Microsoft Edge, so the originating browser for these rules must be Internet Explorer, Edge or Edge IE Mode. Customers looking to redirect to Edge IE Mode from other browsers will need to purchase and deploy Browsium Catalyst. Contact support or your client account manager for more information.

Java Version Manager

By default, Internet Explorer uses the most recent version of Java installed on the system. But many enterprise applications require an older version of Java to run properly. The Java Version Manager automates the remediation of Java versions within an Ion Profile, enabling Ion to swap in the selected version of Java on client systems at runtime.

Java Version Manager provides a dropdown list of all versions of Java installed on the system running Ion Configuration Manager. The System Default choice at the top of the list is the default value in every full Ion Profile. Leaving this value unchanged instructs Ion to ignore Java and allow Internet Explorer to use the default (most recent) version when the Profile is invoked.

Selecting any other version will kick off the process of adding a Java remediation to the Ion configuration, displaying the selected version in the Java Version field in the Profile Properties page. The Java selection can be changed by running the Java Version Manager again.

Running Java Version Manager in a project that contains a legacy Custom Files-based Java remediation will automatically delete the legacy Custom Files entry. You can then select the same version of Java from Java Version Manager to create the new remediation. You will see the following prompt before the Custom Files entry is deleted. Selecting Cancel will keep your legacy Custom Files entry unchanged. Browsium recommends selecting OK and deleting the legacy entry, followed by the Java version selection in Java Version Manager.

Projects with a legacy Custom Files-based Java remediation that has not yet been migrated using the new Java Version Manager will display System Default in the Java Version field in Profile Properties, even though the project will remediate Java using the entry in Custom Files Manager. It is recommended that all legacy Java remediations (for Java 1.4 and later) be migrated to the new remediation architecture using Java Version Manager.

Client PCs must be running the selected 32-bit or 64-bit version of the Java Runtime Environment (JRE) for the Profile to function as intended. A best practice is to install (and keep up to date) the most current version of the JRE on each client PC, along with the JRE versions required for the applications accessed by the user of that PC. Many organizations will install all legacy JRE versions required by applications used within the organization, along with the most current version, in a single Windows image that is then managed by Ion Profiles and rules.

Java Version Manager can also be used to “lock in” a modern version of Java for all business applications that require Java and work well with recent versions. This can be done alongside Profiles that use legacy versions of Java. So, for example, a Profile and rule combination can be created that always uses Java 8 update 73 for all sites in the intranet zone, even when newer releases of Java are installed. This allows the organization to avoid retesting all internal Java-dependent applications every time Oracle releases a security update for Java, yet still get the benefit of those security improvements for Internet sites.

Use Java Version Manager to lock in a Java version for all internal applications, yet still get the benefit of those security improvements for Internet sites.

Systems running Ion Configuration Manager have an additional requirement when using the Java Version Manager. These systems must run a recent 32-bit version of the Java Development Kit (JDK), as it is used by the Java Version Manager. The specific version of the JDK is not critical, as long as it’s newer than Java 7 update 40, and newer than the JRE versions needed in your Ion Profiles. Java 8 update 73 is the most recent version of the JDK as of the publication date of this guide, and is an excellent choice for use with Java Version Manager.

Running Java Version Manager without the JDK installed will result in the following error. If you experience this error, visit the Oracle Java SE download site to download and install the free JDK and then run Java Version Manager again. Note that you will also see a similar error if you have installed the 64-bit JDK. Ion supports both 32-bit and 64-bit versions of JRE, but Ion Configuration Manager requires the 32-bit JDK to run Java Version Manager.

Java Version Manager also supports custom Java configurations, allowing direct editing of the XML to enable custom permissions or remediate multiple Java versions in one Profile. Contact Browsium Support for assistance in working with Custom Java configurations.

The Java Version Manager also provides for ‘plugin-based’ Java swaps to ensure a more broad range of scenarios. For some versions of Java, swaps can be performed by swapping out the Internet Explorer add-on rather than by using Java’s internal Deployment Ruleset system. The “force plugin-based swap” option should be selected if there are compatibility issues precluding the use of standard Java swaps. Note that if this option is selected, security settings may have to be adjusted for the application to run.

Custom Files Manager

Ion allows you to create specific file system entries and define custom ActiveX controls for a Profile. Ion manages these items using a private memory address space, so nothing is applied or modified on the default Windows system running Browsium Client. These entries can reference a file on disk (available locally on the PC running Browsium Client or accessible via a server) or a text string (of arbitrary length) or binary file that is included in the Ion configuration.

This screen displays all configured custom file and custom ActiveX mappings. To add a value, use the link in the Actions Pane on the right-hand side. To edit a value, highlight the item in the Content Pane and use the ‘Edit’ link in the Actions Pane. The Custom Files Manager supports the Delete, Copy, Cut and Paste items as well.

Custom Files Editor

Use this screen to add or edit Custom File mappings. You may either type the file path or use the ellipses to browse the local file system and select the desired Source and Target files. It is a good practice to use environment variables, such as %ProgramFiles%, to ensure the file paths are properly resolved on both 32-bit and 64-bit editions of Windows.

The following fields are available in the Custom Files Editor:

Description — Allows for a more complete explanation of the Custom Files entry.

Custom File Type — Specifies the type of custom file swap being performed. Local (the default) specifies a Source File to replace a Target File. The Source File must be located on or accessible from the client PC running this Ion configuration. The Target File is typically already present on the client PC (e.g., a text-based settings file) or even installed on the client PC (e.g., a DLL).

Binary also specifies a Source File to be swapped for a Target File, but the Source File does not need to be present on the client PC. It will be included with the Ion configuration, embedded in the .BCX file. Text provides even more flexibility, with the Source File created on the fly in the Ion project in the Custom File Content field, as shown below.

Source File — Path to the file to replace the Target File.

Target File — Path to the file already on the client PC that will be replaced by the Source File.

Register ActiveX/COM? — This field is disabled by default. When enabled, the Source File will be added to a virtual registry in memory on the client system, but only while Ion is active. Once the Ion-managed instance has closed, the virtual registry is removed from memory.

Custom Registry Manager

This screen allows you to create specific registry entries for a Profile. Ion provides an environment to host these items in memory, so nothing modified on the client system.

To add a value, use the link in the Actions Pane on the right-hand side and select the ‘Add’ item. To edit a value, highlight the item in the Content Pane and use the ‘Edit’ item in the Actions Pane. The Custom Registry Manager supports the Delete, Copy, Cut and Paste items as well.

Custom Registry Value Editor

Any type of Registry entry can be created using this interface. Simply choose the Hive location and entry values, and then click OK.

HTTP Header Manager

This screen displays the list of defined Custom HTTP headers. HTTP header fields are components of the message header of requests and responses and some web applications rely on these headers to trigger certain behaviors and functionality. Ion enables easy creation and management of HTTP Headers.

A list of available HTTP Header fields can be found in this Wikipedia article. To add an HTTP Header, use the link in the Actions Pane on the right-hand side and select the ‘Add’ item. To edit a value, highlight the item in the Content Pane and use the ‘Edit’ item in the Actions Pane. The HTTP Header Manager supports the Delete, Copy, Cut and Paste items as well.

Content Override Manager

Some older web applications may include content (JavaScript, HTML, CSS, images, etc.) resulting in compatibility issues with newer browser rendering engines that cause the application to work incorrectly. These issues can be as simple as layout issues, more complex coding related issues that prevent the site from loading or even serious issues that cause the web browser to crash when loading specific content.

Ion provides the ability to replace or block inline or linked content for a given web page to help solve these compatibility issues.

Content Override Editor

Start by defining the Target URI — even though these settings are part of a Profile which would be triggered by a rule, Content Overrides have an additional layer of granularity and work with content regardless of the location so the Target URI must be specified for the content being replaced.

The Content Override feature provides the ability to control the loading behavior taken by the browser for the specified content. The available actions are:

• Block: Stops the content from being downloaded.

• URL (Default): Redirects the request for the content at the specified URI to the URL specified in the Data field.

• File — Body Only: Loads content from the file specified in the Data field.

• File — Header and Body: Loads content from headers and file specified in the Data field.

• Content: Replaces content from the specified URI with the content in the Data field.

The Data field will contain content based on the selected action.

In addition to application compatibility needs, the Content Override feature can be used to augment security and prevent downloading known malicious or restricted content. For example, using the Regex match method an organization can build a complex matching string to prevent downloading any exe, dll or other data types.

String Replacement Manager

Some older web applications need simple, targeted fixes to make an application work exactly right. Often the issues can be as simple as resizing an image or changing a word in some JavaScript. Changing the web application source code is a great way to go — but many organizations are using ‘off the shelf’ applications for which they don’t have source code access to change what is needed. Some commercial applications have license agreements that prohibit any modification to their source code or binaries. In addition, changing the source code is impractical for enterprise deployments where some users will remain on older browsers while some users get the latest versions.

Ion offers the ability to edit text ‘inline’ before the browser rendering begins, enabling an organization to fix virtually any issue without touching the server-side source code. These changes are highly targeted and can be used to make pinpoint changes to the affected area of the web application.

Making a string replacement is easy. It all starts with the Target URI — even though these settings are part of a Profile which would be triggered by a rule, String Replacements are designed to work with content regardless of the location so the Target URI must be specified for the strings being replaced.

String Replacement Editor

Browsium has worked with dozens of customers to resolve highly complex web application compatibility issues. Many of the more complex issues require a series of String Replacements. Since any given replacement can be targeted at a highly specific area, Ion includes data fields to define a Name and Description of each string replacement.

This metadata information is not used by Ion but provides administrators or developers an easy and convenient place to read notes about each item that could be used to convey history on that issue and avoid others from having to troubleshoot from scratch.

String Replacements can be easily enabled or disabled via the Enable checkbox, easing configuration development and troubleshooting.

The core of a String Replacement is the string to find — the pattern match can be Simple or RegEx depending on the Match Method property selected.

Advanced Profile Settings

Since web applications can utilize a combination of different development technologies, some Profiles may need additional advanced configurations to accommodate the varied technologies. For example, a web application can integrate JavaScript (interpreted) code while also calling an ActiveX control that runs outside the Internet Explorer process model. By offering an array of options to developers with which to build their applications, web development is an extremely powerful discipline. Those same benefits can also mean a specific application has unique and specific requirements which can complicate remediation.

To help accommodate the unique scenarios that may be required, Ion offers additional behavioral and environmental controls using Advanced Profile Settings. As a rule, most web applications will work properly without modifying any of the entries or values in this area.

Content-type Whitelist

The Content-type Whitelist feature is provided to address complex and unique web application scenarios that require uncommon data types. By default, Ion is designed to handle only those data types listed here. Any Content-type not included on this lit will be ignored by Ion and passed along to Internet Explorer for handling by the IE MIME type handler function.

In the case where some environmental, string manipulation or other modification is required of a given Content-type, the value should be added here. Adding additional Content-types is easy. Simply find the ‘Click to add a new item…’ line, select that entry and begin adding the required value. The values in the Content-type Whitelist are freeform text, not selected from a list, so care should be taken to ensure spelling and syntax are correct or Ion will not function as expected.

Customers are encouraged to avoid changing or deleting any of the pre-defined Content-type Whitelist entries. Incorrect modifications or deletions may result in Ion behaving unexpectedly.

Ion Profile Flags

Ion Profile Flags provide a mechanism to add additional functionality, logging, and management capabilities without the need to update the Ion binaries. The feature is designed mainly for use in complex web application debugging scenarios. Certain Ion Profile Flags values can also be used to extend Ion functionality to meet an array of unique and specific edge-case scenarios. This version of Ion supports the following Ion Profile Flags.

---

Ion Profile Flag Description

---

Ion.LauncherWaitForProcessExit=true Causes the BrowsiumIonLauncher.exe process to wait for the Internet Explorer frame process. The Launcher process ends only when Internet Explorer frame process is closed. This flag is typically used by the Siebel Offline client.

Ion.IEAddonDetectRedirects=true When this flag is set, Internet Explorer will detect 30x redirection (typically a 302 redirect) and evaluate rules on the redirected URL. By default, 30x redirected URLs are ignored by Ion.

Ion.EnvShareAllowProc=‘value’ Enables sharing BoxedApp execution environment with specified processes. Multiple processes can be defined by appending .n to the Profile flag. E.g., Ion.EnvShareAllowProc.1=javaw.exe; Ion.EnvShareAllowProc.2=javaws.exe;

Ion.EnvShareWithAllChildren=true Enables sharing BoxedApp execution environment with all child processes.

Ion.SessionIsolation=true Forces session isolation between Ion-invoked Internet Explorer processes belonging to the same Ion Profile. This flag guarantees new Internet Explorer session creation only when launched using BrowsiumIonLauncher.exe.

Ion.SkipAutoAuth—fiddler=true Enforces Ion to skip Fiddler Core auto-authentication and provides flexibility for Internet Explorer to authenticate with a server.

Ion.SkipBuffering.n=‘string’ Ion, by default, buffers HTTP sessions originating from managed Internet Explorer instances. This could lead to experience problems when loading mp4 video, or any other binary content that typically is consumed via streaming. Ion.SkipBuffering.n will match URL patterns that should not be buffered. E.g., Ion.SkipBuffering.1 = \.mp4; Ion.SkipBuffering.2 = \.wav. Regex is used to match the string.

Examine Web Requests

Examine Web Requests determines when to send web requests and responses through the internal proxy for examination and content modification. ‘Always’ bypasses the routing logic and forces all traffic through the internal proxy. Auto allows Ion to decide and reduces proxy routing where possible. By default, Profiles are set to use ‘Always Examine Web Requests’ to ensure consistent application handling.[]{#_The_Rules_Manager .anchor}

Run As Administrator

Some web applications require Internet Explorer to be launched with Administrator privilege to function properly. While this is a rare scenario, Ion supports these applications via the Run As Administrator flag. The default value for this flag is ‘Disabled’. When set to ‘Enabled’, the Ion-managed instances of Internet Explorer will be launched with Administrator privilege for this Profile. This field is not applicable on Windows XP or Windows Server 2003. All newer versions of Windows support Run As Administrator.

Global Java Profiles

Global Java Profiles are Ion Profiles that can solely remediate Java for specific web applications. A Global Java Profile cannot contain any other configuration settings, such as String Replacements or Custom Files.

Global Java Profiles build on Oracle Java Deployment Rule Sets (DRS) and control the version of Java within the native instance of Internet Explorer. Because Ion uses Oracle DRS for the Java remediation in Global Java Profiles, they can only be used with Java 6 update 10 and later. Java remediation for earlier versions of Java requires a full Ion Profile.

Ion Global Java Profiles have two key advantage over native Oracle DRS:

First, creating and deploying an Ion Global Java Profile is simple, as you’ll see in the sections that follow. Ion Configuration Manager provides a GUI, wizard-based approach to creating the remediation. And the Ion XML project file deployed to client systems handles all the overhead of creating and signing the DRS JAR files.

Second, client systems can be upgraded to the latest version of the Java Runtime Environment (JRE) and Ion Global Java Profiles will continue to work as originally created. The Browsium Client Controller maintains the integrity of the DRS files on each client system, ensuring Java swaps, and Java blocks, always work as expected.

Contrast these Ion advantages with Oracle DRS which requires manual editing of XML files, manual certificate-based signing of JAR files, and repackaging/redeployment of the DRS JAR file every time a new JRE is released.

Creating a Global Java Profile

To create a Global Java Profile, select Add from the Profiles Manager and select the Global Java Profile option.

Clicking ‘Next>’ launches the Java Version Manager, where you must select the version of Java required for the web application. Next the Profile Properties page is displayed, where you can edit two fields: Name and Description. The two other fields, Java Version and Java Platform are uneditable. The Java Platform value is always 32-bit for Global Java Profiles. (You’ll need to use a full Ion Profile for 64-bit Java, as described in section 3.3.2.2.) You’ll notice that the Profile name defaults to Global Java Profile, with the selected Java version in parenthesis. You may want to change this to a more descriptive name, especially if you’re creating multiple Global Java Profiles, each setting a different version of Java.

The Java version defaults to the default version of Java on the system you’re using to create the Profile — in this case Java 8 update 301. It cannot be manually edited. It must be edited via the Java Version Manager. Select the Java Version Manager in the Profile Actions Pane to set the desired version of Java for your Profile.

Only 32-bit Java versions newer than Java 6 update 10 will appear in Java Version Manager for a Global Java Profile. If you need an older version of Java, or 64-bit Java, you’ll need a full Ion Profile. See section 3.3.2.2 for complete documentation of the Java Version Manager for full Ion Profiles.

Once you have selected your desired version of Java, click OK to return to the Profile Properties page. Now would be a good time to edit the Profile name to match the Java version selected.