Global remote output setup
It is possible to print on other networks, that are protected by a firewall. For that you need a remote client in the remote network, that is able to access the InterFormNG server.
To do that you first need to enable this feature globally in InterFormNG2 as described below.
The setup of the remote client is covered here.
In order to setup InterFormNG2, you first need to sign in as described here.
Then you click Remote output on the left below Workflow:
- and then you will see this:
Output Notifications
By default, the remote output client will use a poll method to check for available outputs. In this mode the client will poll for outputs every 30 seconds.
In notification mode, the remote client will not be polling, but instead wait for notifications from the main application that new output is available, the process it immediately. I.e. less delay on output than the poll method. This mode also puts less load on the main application, as it does not need to process constant poll requests.
To enable notification mode on the main application, flip the switch "Enable remote output socket-based notification".
The notification system requires a constant socket connection from the client to the main application. On the settings you need to specify the port on which the client will connect, as well as the keystore for encrypted communication. The default "internal:remoteoutput.jks" means that the embedded keystore is used. This can be replaced with the file system path of another keystore. (Note that no customer data is sent in the notifications, so it is not strictly necessary to replace the keystore).
Sends notifications from the remote output server to the remote output client. The notification includes the ID of the output item as well as its associated metadata.
The actual notification technology is configurable, so it could be a message queue like Amazon SQS or a permanently open socket connection between client and server.
Notice, that any change is activated only after a restart of the InterFormNG2 service.
After a restart of the service you should consider to check the system log to verify, that the keystore and matching password could be used.
Related Articles
Remote output
If you want InterFormNG2 to allow a remote client to connect the current tenant, then you need to configure the remote output as below. A requirement is, that remote output is activated in the global settings. In order to setup remote output ...Workflow global settings
This section lists all global settings for the workflow. More settings can be setup per tenant. You can set these global workflow settings: 1.Email server. This is the email server to use for system messages, that are to be sent as emails e.g. to ...Output via remote clients
This section describes how to use remote clients in the InterFormNG2 workflow. The remote client can be used for these kinds of output in the workflow: 1.Print on remote printers, that are only reachable via the remote client(s) 2.Email via email ...Global email server setup
You need to setup a global email server order to be able to send system emails from InterFormNG2 e.g. to reset emails. Notice a similar email configuration for each tenant is normally also required. In order to setup the global email server, you ...Global Active MQ setup
If you want to use ActiveMQ, then you can use the embedded ActiveMQ of InterFormNG2. In order to setup the global email server, you first need to sign in as described here. Then you click Message Queue on the left below Workflow: Now you can enable ...