Configure the FileAct and InterAct Adapter

Article
02/02/2021

Configure the different artifacts used by the BizTalk FileAct and InterAct Adapters runtime.

Prerequisites

Install the BizTalk FileAct and InterAct Adapters
Sign in as a member of the BizTalk Server Administrators group
Confirm SQL Server is running

Step 1: Configure the FileAct and InterAct adapter

In the Microsoft BizTalk FileAct and InterAct Adapter Configuration wizard, go to Overview. In the left pane, select Runtime to configure the runtime components of the adapters.
In Runtime Configuration, under Account, select the ellipsis […] to enter the COM plus configuration for the Store and Forward mode.
In User Credentials, enter the user name (in the domain\user name format) and password for the account used in the COM plus configuration. Select OK.

Note

A User Credentials warning appears if the account you entered has higher privileges than are recommended. Select Yes to continue.
Select Apply configuration to apply the COM plus configuration to the FileAct and InterAct Adapter.
In the Summary, review, and select Next.
When the configuration completes, review the list of components. A check mark means that the component is configured successfully. An "X" means that there is a problem with that component.

Note

Use the Logfile link to view the configuration events.
Select Finish to complete the configuration. The Overview shows the current configuration status for the Runtime components.

Next, create the host and host instances to run these adapters.

Step 2: Create the host and host instances

We recommend that you create a dedicated host for the FileAct adapter and a separate dedicated host for the InterAct adapter. For each adapter, create at least one host instance.

Managing BizTalk Hosts and Host Instances list the steps to create hosts and host instances.

Once created, the next step is to add the send handler, and use the Client Message Partner you created in the SWIFT Alliance Gateway (SAG).

Step 3: Create the send handler

You use the FileAct and InterAct send handler properties as the send port configuration values, if the properties are not set on the individual FileAct or InterAct send port.

In the BizTalk Server Administration console, expand BizTalk Server Administration, expand BizTalk Group, expand Platform Settings, and then expand Adapters.
Select the FileAct or InterAct adapter. In the right pane, double-click the send handler.
In the Host name drop-down list, select the host you created in the previous section. Then select Properties.
In the Transport Properties, select the Argument property, and enter the following argument as:

-SagMessagePartner <Client Message Partner created in SAG\>

Note

Replace <Client Message Partner created in SAG> with the name of the client message partner. Leave the default values for the Crypto Mode, FACrypto Mode, and LogMessages properties.
Select OK to save your changes, and then to close the properties window.
Under Platform Settings, select Host Instances.
Restart the host instances:
- Right-click the FileAct host instance, and Restart
- Right-click the InterAct host instance, and Restart.

Next, enter the server message partners in the SWIFTNet paramfile to enable the FileAct and InterAct receive adapters.

Step 4: Configure the SWIFTNet param file

To enable the FileAct and InterAct receive adapters to initialize with the values, the Server message partners created in SAG must be entered in the SWIFTNet paramfile. The paramfile is typically located in c:\SWIFTAlliance\RA\<remote access instance name\>\cfg\paramfile. After you configure the paramfile, start SnlReceiver.exe.

Open the SWIFTNet paramfile. In the location marked with "***" add the following. Note that the AdapterType value can be Interact or Fileact.

spawn "snlreceiver -SagMessagePartner <Server MessagePartnerName\> -AdapterMode <AdapterType\>"

 username:snlowner
 subsystem_name:SampleSubsystem
 #subsystem_group: SampleSubsystem
 #subsystem_dependency:Support,Swarm
 subsystem_nature:critical
 subsystem_start:
 ***
 *END
 subsystem_stop:
 *KILL9:snlreceiver
 *END
 subsystem_status:
 *NB:1:snlreceiver
 *END
 start_event:SNL001:subsystem SampleSubsystem is up
 stop_event:SNL002:subsystem SampleSubsystem is down

Note

Before you start SNLreceiver, enable the receive ports for the adapter you are using (FileAct or InterAct).

Start and stop SnlReceiver.exe:
1. On the desktop, select the Remote API icon to open the Remote API command prompt.
2. At the command prompt, type Swiftnet start. Select ENTER to start SnlReceiver.exe.
At the command prompt, type Swiftnet stop. Select ENTER to stop SnlReceiver.exe.

Next, update the file autoexec.bat to set the SWIFT environment variables.

Step 5: Update autoexec.bat to configure the receive adapters

Update the autoexec.bat file to set the SWIFT environment variables on the computer where you installed the BizTalk FileAct and InterAct Adapters receive adapters. The environment variables are generated from the system that has the receive adapter installed in the path c:\SWIFTAlliance with an instance of the receive adapter named Ra1. Update the SWIFT environment variables appropriately for your configuration.

The following is a sample of the autoexe.bat file:

SET COMPUTERNAME=<Machine Name>
SET GENLOG_DIR=C:\SWIFTAlliance\RA\Ra1\log
SET GENUTIL_DIR=C:\SWIFTAlliance\RA\bin
SET HOMEDRIVE=C:
SET LOGONSERVER=\\SERVERNAME
SET OSA_DIR=C:\SWIFTAlliance\RA\Ra1\log
SET OSA_INSTANCE=Ra1
SET PKIEXECDIR=C:\SWIFTAlliance\RA
SET SAGRA_HOME=C:\SWIFTAlliance\RA
SET SESSIONNAME=RDP-Tcp#1
SET SLP_ENV=DEFAULT
SET SLP_FILE=server.slp
SET SNL_DOMAIN_NAME=Ra1
SET SPK_DATA_DIR=C:\SWIFTAlliance\RA\data\pki
SET SWNET_BIN_PATH=C:\SWIFTAlliance\RA\Ra1\bin
SET SWNET_CFG_PATH=C:\SWIFTAlliance\RA\Ra1\cfg
SET SWNET_HOME=C:\SWIFTAlliance\RA
SET SWNET_HOST=HOSTNAME
SET SWNET_INST=Ra1
SET SWNET_LOG_PATH=C:\SWIFTAlliance\RA\Ra1\log
SET SWNET_SLP_PATH=C:\SWIFTAlliance\RA\data\
SET SWNET_VERSION=5.0.20
SET SWTRACE=C:\SWIFTAlliance\RA\Ra1\log
SET Path=%PATH%;C:\SWIFTAlliance\RA\bin
SET Path=%PATH%;C:\SWIFTAlliance\RA\lib

See some examples

For examples of FileAct and InterAct messages, see Sample InterAct and FileAct Messages.

Share via