How to Seamlessly Integrate the 2X Client with Third Party Applications By Giorgio Bonuccelli on | 0
It is normal practice for an organisation to integrate the functionality provided by the 2X Client into existing software. This may be needed to control the flow of how applications are started (e.g. a VPN tunnel that needs to be started) or to hide the application launcher and make it simple for the user to deploy the application he/she would need.
Since there are different platform versions of the 2X Client the approach to this will vary depending on the target operating system.
|Windows 2000 and higher||Command Line|
|Linux Desktop||Command Line|
|MAC Desktop||Command Line|
|iPad and iPhone||URL Schemes|
|Web Portal||iFrame / WebServices|
|Java Client||Java Applets|
Windows 2000 and higher
We will start with the Windows Client which is the first client 2X released way back in 2006. The method provided for this operating system is the command line approach where the user can start any application or desktop. It can also be used for the Windows CE edition. Please note that when the command line interface is used and a connection matching the server is already configured the settings are merged.
The Linux client uses a similar approach to the Windows Client, with one difference; all required arguments need to be passed on the command line, no configured connection matching is done. Please note that the command line options vary as well.
The MAC client again uses a command line approach.
The Android client exposes a programmable interface with which any application can deploy a connection to any application or desktop. This interface allows also the third party application to disconnect the connection.
iPad and iPhone
On an iOS platform the user can link to 2X connections by using a URL.
The Web Portal provides two different ways to make use of the system in other web sites; iFrames and Web Services.
The iFrame approach is very easy, you simply embed the Cloud Portal into an iFrame as demonstrated here in our Facebook App. Also supported is a Web service programmatic interface.
The Java Client is deployed as an applet in a web page, therefore it can be embedded in any web site. You can even provide your username and password as an argument to the applet and so provide a simple way to integrate a holistic Single Sign On for the entire site.
Please note that this information may change in the future.