Installation of the Launcher Service

Installing the Launcher Service on a PC & Registering Windows Service

The launcher service is registered and operated as a Windows service. To use the launcher, the Windows service must first be registered.

TPLSvc_Setup.exe /VERYSILENT
TPLSvc_Setup.exe /SILENT

You can check that the registered service is operating by going to [Control Panel > System and Security > Administrative Tools > Service]. The service can be stopped or restarted from that window.

Deleting the Launcher Service from PC

Specifying the Service to Run on a Specific Port

The launcher service has its port specified. If you want to change this, then you can run the service by specifying parameters directly through the command prompt.

C:\Program Files (x86)\TPLSvc\TPLSvc.exe

TPLSvc_Setup.exe –r false

TPLSvc_Setup.exe –r true

The launcher uses one of the specified ports depending on its communication method. If another service is already using the port on the system where the launcher is running, the port can be changed and used. .. In this case, specify additional parameters (-p port number 1, -p port number 2 ... -p port number n) to designate the port when registering the service.

For example, if you want to use ports 8080 and 8888 for HTTP communication, register the service as follows.

TPLSvc_Setup.exe –r true –p 8080 –p 8888

Operating Method

A brief explanation of the operating method between the launcher service and the web browser is described in the table below.

• In order to run the launcher service in the web browser, the data that fits the format must be transmitted.

• Data is transmitted as text written in JSON format and the result is in the same format.

• The id value is essential information for the launcher execution. You must send the new id request (operation numbers 1 and 2).

• Required property information must be set (operation numbers 3 and 4).

• Please keep in mind that the input is case-sensitive.

Basic Settings

Address Setting

The address setting is divided into required and additional parts. Combine the additional part with the required part to use.

http://127.0.0.1:7895/launcher/nexacro/123456789
http://127.0.0.1:7895/launcher/xplatform/123456789
http://127.0.0.1:7895/launcher/miplatform/123456789

• Local address (127.0.0.1) and reserved word (launcher) cannot be modified.

• If a specific port is opened during installation, then the corresponding port number can be used.

• Timestamp prevents communication failure due to web browser cache operation.

Basic Element Setting

Elements to be set by default are platform, action, id, and value. They are to be set according to each application.

platform

These are character strings that represent the platform. You can specify one of the 3 options below, depending on the product.

nexacro, xplatform, miplatform

action

This specifies the action string to request from the launcher service. You can specify the following actions.

id

This is the character string assigned from the launcher service, and it must be requested upon initial operation.

value

This is information in the JSON format specific to the operation, and the configuration varies depending on the operation.

$r_title(JSON for receiving the initial id assignment: No value, id is delivered as the result)
var objNexacro = new Object(); 
objNexacro.platform = 'nexacro';
objNexacro.action = 'create';
//objXP.id = ''; // It can be omitted as the information is filled if the communication is successful.

$r_title(JSON for setting related properties)
var objNexacro = new Object(); 
objNexacro.platform = 'nexacro';
objNexacro.action = 'setproperty';
objNexacro.value = {"property name" : property value, ... };

$r_title(JSON for checking the set property value)
var objNexacro = new Object(); 
objNexacro.platform = 'nexacro';
objNexacro.action = 'getproperty';
objNexacro.value = {"property name" : "", ... };

$r_title(JSON for method invocation)
var objNexacro = new Object(); 
objNexacro.platform = 'nexacro';
objNexacro.action = 'method';
objNexacro.value = {"method name": {"param": method parameter array, "result": }};

$r_title(JSON for checking event information)
var objNexacro = new Object(); 
objNexacro.platform = 'nexacro';
objNexacro.action = 'event';
objNexacro.value = {"event name" : {...}};

$r_title(JSON for checking the launcher service version information)
var objNexacro = new Object(); 
objNexacro.platform = 'nexacro';
objNexacro.action = 'check';
objNexacro.value = {"getlauncherversion": {}};

Data Transmission

Data transfer is sorted into HTTP/HTTPS communication (GET, POST) and WebSocket communication.

$r_title(In the GET method, the ? and the character string in JSON format are appended to the address)
var objNexacro = new Object();
var xhrObject = new XMLHttpRequest();
xhrObject.onreadystatechange = resultProcess;
var jsonData = JSON.stringify(objNexacro);
var openurl = "http://127.0.0.1/launcher/nexacro/"+new Date().getTime();
xhrObject.open("GET", openurl+"?"+jsonData, "true");
xhrObject.send(null);

$r_title(In the POST method, the character string in the JSON format is appended to the send method parameter)
var objNexacro = new Object();
var xhrObject = new XMLHttpRequest();
xhrObject.onreadystatechange = resultProcess;
var jsonData = JSON.stringify(objNexacro);
var openurl = "http://127.0.0.1:80/launcher/nexacro/"+new Date().getTime();
xhrObject.open("POST", openurl, "true");
xhrObject.send(jsonData);

$r_title(Data transmission during WebSocket communication)
var objNexacro = new Object();
var openurl = "ws://127.0.0.1:7970/launcher/nexacro/"+new Date().getTime();
var objWebSocket = new WebSocket(openurl);
var jsonData = jsonData = JSON.stringify(objNexacro);
if (objWebSocket != null) {
	objWebSocket.send(jsonData);
} else {
	return null;
}

Data transmission can be processed in any way by configuring the character string in the JSON format. If the stringify method cannot be supported, or if you want to set it yourself, then create the character string in the following format to process it.

create
'{"platform":"nexacro","action":"create"}'

launch method
The id value must be replaced with the value received from create.
'{"platform":"nexacro","id":"12345678","action":"method", "value":{ "launch":
null }}'

Processing Communication Result

String data in the JSON format should be appropriately converted and processed.

$r_title(HTTP/HTTPS communication result processing)

var result = xhrObject.responseText; // xhrObject is XMLHttpRequest
var objResult = eval('(' + result + ')');

$r_title(WebSocket communication result processing)
function onMessage(evt) {
	var data = evt.data;
	var objResult = eval('(' + result + ')');
...
}

If the processing result is successful, then the result string is processed as 'success'.

if(objResult.result == "success" && objResult.id.length > 0)
{
    objNexacro = objResult; // objXP is an object that contained transmission information
}    else    {
    window.console.log("error!!!");
}

Using TPLSvcAgent

When the launcher service is executed in a specific environment, some user information required for service execution cannot be verified due to security limitations of the Windows operating system. To circumvent this, a separate agent file (TPLSvcAgent.exe) is provided, and the agent file is executed to check information when user information is required according to the multisession property settings.

Supported features

The multisession property value is set to true and the following functions are supported when the agent is running.

• Execute nexacro.exe as the administrator

• Supports download of shortcut image files when using a proxy server

• Verifies the user information in a virtual environment (citrix, vmware, windows remote desktop)

How to use

To enable agent execution, set the multisession property value to true in the setproperty function for launcher service startup.

objNexacro.action = 'setproperty';
objNexacro.value = {
...
	"multisession": true,
...
};

When verifying the user information in a virtual environment, the id value must be set as the title property value of the document in the callback function when the id is first assigned (create action).

function createProcess() {
...
	if (bMultiSession == true)
	{
		top.document.title = objNexacro.id;
	}
...
}