12
SABB e FX Client Requirement /Version 3.0 SABB eFX Client Requirements 11-Nov-2016 1 Version 3.0

SABB eFX Client Requirements v3 · CLIENT SOFTWARE ... SABB e FX Client Requirement /Version 3.0 Order Management Functionality When using Order Management functionality, particularly

Embed Size (px)

Citation preview

SABB e FX Client Requirement /Version 3.0

SABB eFX Client Requirements 11-Nov-2016

1 Version 3.0

SABB e FX Client Requirement /Version 3.0

Table of Contents

ABOUT THIS DOCUMENT .................................................................................................................... 1

CLIENT SOFTWARE ............................................................................................................................. 2

OPERATINGSYSTEMS………………………………………………………………………………………………………………..……..……2

Browsers and Javms……………………………………………………………………………………………………….………………………2

Microsoft Internet Explorer……………………………………………………………………………………………………………………2

Supported Version of Microsoft Internet Exlorer .............................................................................. 3

Sun Java Plugins .................................................................................................................................. 4

Order Management Functionality ........................................................................................................ 5

ActiveX Browser Permission (While download the Spread Sheet) ................................................ 6

Steps to Activate Java Log ................................................................................................................. 7

SABB e FX Client Requirement /Version 3.0

About this document

1.1 Intended readership: This document is intended for anyone using the SABB eFX.

1.2 In this document The main purpose of this document is to provide information for clients about the system configuration

needed within their operating environment. It does not, however, address issues such as security that could dictate configurations with a higher specification, depending upon individual clients’ internal standards.

We give here details of the Recommended, Supported and Minimum specifications for the hardware and software that you need to run in these environments.

• Recommended means this is the version that the system has been targeted at. It will usually give the best performance and have the most testing. It will be used internally for development and support.

• Supported means these releases do not present known problems; however performance or functionality may be degraded in some areas.

• Minimum means prior versions lack required functionality or adequate performance.

For all three categories, we give brief details of known issues with particular third-party products or product combinations that could have an impact upon system performance.

This is a live document. It will be updated on a regular basis to provide definitive guidelines for use by allclients for all supported operating environments.

SABB e FX Client Requirement /Version 3.0

Client Software

This section describes the additional software required to run a client

Operating Systems

MS Windows is the Desktop Operating system. Supported versions are:

Windows Version Minimum/ Recommended/ Supported

Comments

2000 Supported But only with Service Pack 2 or above

XP Supported But only with Service Pack 1 or above

7 Supported

Browsers and JVMs

A known Sun JRE window painting issue can in some cases cause poor applet performance and applet crashes. This issue affects machines with multiple physical or logical CPUs, including those featuring hyper-threading and multiple cores. The recommended workaround is to use the Windows Task Manager to bind the iexplore process to one logical CPU before loading the applet. Third-party software which automates this configuration is also available.

Popup blockers are detrimental to some SABB eFX functionality; therefore it is important that such software is either disabled, or configured to allow popups from SABB eFX system.

Microsoft Internet Explorer

It is important that each applet instance is launched in its own instance of Internet Explorer. There are known issues in the JVM that cause problems with applets if they share an instance of Internet Explorer.

Notes : It is important that the “Reuse windows for launching shortcuts” checkbox is unchecked in Internet Explorer. Select Tools > Internet Options. Click the Advanced tab, go to the Browsing section.

SABB e FX Client Requirement /Version 3.0

Instructions for adding Section Numbering

1.2.1 Supported Version of Microsoft Internet Exlorer (MS-IE) are shown in the below table:

Note: RET and ET applets no longer support Chrome.

SABB e FX Client Requirement /Version 3.0

Sun Java Plugins

The recommended and supported versions of Sun JVM tested for use with SABB eFX client applets is dependent on the IE browser version:

Note: When restarting an applet, please ensure it is started from a new browser window. Any browser windows

previously used to launch the applets should be closed when the applet is closed.

SABB e FX Client Requirement /Version 3.0

Order Management Functionality

When using Order Management functionality, particularly in the trader applet, memory allocations should be adjusted to account for the size of the bank order book and thus the amount of orders displayed in the applet.

It is recommended that memory allocation is increased from the default with the following Java Runtime Parameter:

-Xms128m –Xmx512m

To set this parameter:

1. Go to Start ► Control Panel ► Java

The Java Control Panel is displayed:

2. Click the Java tab.

3. Click the View button.

4. Type the following into the Java Runtime Parameters field for the JVM version you use:

-Xms128m –Xmx512m

SABB eFX Client Requirements | 11-Nov-2016

Page 1 of 5

5. Click OK.

6. Click OK again on main window.

The new settings take effect for the next applet that is launched from your browser.

Note: These settings should be checked whenever you upgrade or re-install a JVM.

SABB eFX Client Requirements | 11-Nov-2016

Page 2 of 5

ActiveX Browser Permission (While download the Spread Sheet)

The error message below will appear when the Spread Sheet button has been clicked and Internet Explorer

ActiveX security settings are configured correctly.

Follow the procedure below to ensure Internet Explorer allows ActiveX controls to be activated from your

domain.

ActiveX configuration procedure

i. Logout of the client applet and close the applet and browser instance. ii. Open a new instance of Internet Explorer. iii. Select Tools > Internet Options and click the Security tab. iv. Click the Custom Level button. The Security Settings window opens. v. Ensure all the all the items under ActiveX controls and plug-ins are either set to

Enable or Prompt. vi. Click the OK button, the Security Settings window closes. vii. Remain in the Internet Options window, Security tab and select Trusted sites. The

Trusted sites icon highlights. viii. Click the Sites button. The Trusted Sites window opens. Add the name of the

domain to the Web sites box. Only activate the Require server verification (https:) for all sites in this zone checkbox if the domain has a valid certificate.

ix. Click the OK button. the Trusted Sites window closes. x. Click the OK button. the Internet Options window closes.

You can now browse to the html location and start a new applet.

SABB eFX Client Requirements | 11-Nov-2016

Page 3 of 5

Steps to Activate Java Log

1) Open Java control panel as shown below.

2) From java control panel activate the Java log recording and click OK.

3) Logout of the applet ( if already login)

SABB eFX Client Requirements | 11-Nov-2016

Page 4 of 5

4) - Click on the About button

4) Set the 'Application Debug Level' to Maximum and click OK

5) - Login as usual and replicate the issue, ( This time a new window “Java console” will also popup. 6) Copy the content of “Java console” into one notepad file save it and sent to us for investigation.

SABB eFX Client Requirements | 11-Nov-2016

Page 5 of 5

7) - Logout of the applet, Restore the debug level to none for normal usage. If not required then stop Java log from Java control panel.