×
Discuss about OFS, Temenos Connectors, Various OFS modes, OFS with Versions, OFS performance, Logging, EB.PHANTOM, OFS.SOURCE etc…
Document for BFL, OFS loading using TCSerever.xml?
- revinath
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 17
- Thank you received: 0
12 years 4 months ago - 12 years 4 months ago #11899
by revinath
Document for BFL, OFS loading using TCSerever.xml? was created by revinath
Hi All,
May you please share any document related to BFL, OFS loading using changing in TCServer.xml?
Thanks in Advance...
Revinath G
May you please share any document related to BFL, OFS loading using changing in TCServer.xml?
Thanks in Advance...
Revinath G
Last edit: 12 years 4 months ago by revinath.
Please Log in or Create an account to join the conversation.
- jpb
-
- Offline
- Moderator
-
- retired
Less
More
- Posts: 2859
- Thank you received: 649
12 years 4 months ago #11939
by jpb
Replied by jpb on topic Re: Document for BFL, OFS loading using TCSerever.xml?
Don't know what you want to set up... Find below the documentation we received from HD for setup of SWIFT:
Setup of tcserver.xml:
To process the clearing strings through TCSERVER we have to edit the tcserver.xml file as suggested in below.
1.
2. We have to add a new T24 Adapter in tcserver.xml. In this example adapter name is SWIFTIN. And we have to specify the PARAMETER tag with a valid OFS.SOURCE record id which has source type is either SESSION or TELNET. In this example we had given PARAMETER tag as TELNET.
3. We have to add a new listener with type as batchfilelistener as shown in below
a) In the above listener <ADAPTERID> tag represents the value of the adapter which was used to this listener in this example we specified SWIFTIN.
b) The <DIR_IN> tag indicates the input directory, where to find the files to process. This tag is mandatory and the directory must exist.
c) The <DIR_OUT> tag indicates the output directory, where the plug-in write the responses. This tag is mandatory and the directory must exist.
d) The <DIR_ERR> tag indicates the error directory, where the plug-in write the processing errors. This tag is mandatory and the directory must exist.
e) The <EXTENSION_TOPROCESS> tag indicates the file extension for files to be processed. By default, it is set to tpr. In this example we will set it to txt. It means that in this example this listener process the files which are present in the path C:\Localhost\TCSWIFTIN\IN with file extension as txt.
f) The <REQ_SEPARATOR> tag indicates the character(s) used to separate requests. Special separators are: cr for carriage return, lf for line feed, crlf for carriage return/line feed, tab for tabulation key. By default, it is set to crlf for Windows and cr for other OS. In this example we used the <REQ_SEPARATOR> as $.
Setup of tcserver.xml:
To process the clearing strings through TCSERVER we have to edit the tcserver.xml file as suggested in below.
1.
<MESSAGEFORMATTER Id="my_appender" type="appender">
<PREFIX>DECARRIER=SWIFT,</PREFIX>
</MESSAGEFORMATTER>
<MESSAGEFORMATTER Id="crlf" type="crlfformatter">
<CRTAG><Cr></CRTAG>
<LFTAG><Lf></LFTAG>
</MESSAGEFORMATTER>2. We have to add a new T24 Adapter in tcserver.xml. In this example adapter name is SWIFTIN. And we have to specify the PARAMETER tag with a valid OFS.SOURCE record id which has source type is either SESSION or TELNET. In this example we had given PARAMETER tag as TELNET.
<!--================================================
Default T24 Adapter
=================================================-->
<ADAPTER id="SWIFTIN">
<!--
<REQUEST_FORMATTER>Thai2UTF, OFSML, UTF2Thai</REQUEST_FORMATTER>
<RESPONSE_FORMATTER>Thai2UTF, OFSML, UTF2Thai</RESPONSE_FORMATTER>
-->
<MAX_SESSION> 5 </MAX_SESSION>
<MIN_SESSION> 1 </MIN_SESSION>
<TIMEOUT>600</TIMEOUT>
<LOGIN_CONTEXT></LOGIN_CONTEXT>
<STARTIN>C:\localhost\R11\Temenos\R09\bnk\bnk.run</STARTIN>
<JBASEPATH>C:\TAFC\R11</JBASEPATH>
<PROGRAM>C:\localhost\R11\Temenos\R09\bnk\bnk.run\t24bin\eb_interface\tSS</PROGRAM>
<PARAMETER>TELNET</PARAMETER>
<LOGIN_CONTEXT></LOGIN_CONTEXT>
</ADAPTER><LISTENER Id="BFL" type="batchfilelistener" active="true">
<ADAPTERID>SWIFTIN</ADAPTERID>
<DIR_IN>C:\Temenos\R11\bnk\bnk.interface\SWIFTIN</DIR_IN>
<DIR_OUT>C:\Temenos\R11\bnk\bnk.interface\SWIFTLOG</DIR_OUT>
<DIR_ERR>C:\Temenos\R11\bnk\bnk.interface\SWIFTLOG</DIR_ERR>
<EXTENSION_TOPROCESS>txt</EXTENSION_TOPROCESS>
<MAX_PROCESS>500</MAX_PROCESS>
<REQ_SEPARATOR>$</REQ_SEPARATOR>
<!-- <DELETE_SOURCE>@</DELETE_SOURCE> -->
</LISTENER>a) In the above listener <ADAPTERID> tag represents the value of the adapter which was used to this listener in this example we specified SWIFTIN.
b) The <DIR_IN> tag indicates the input directory, where to find the files to process. This tag is mandatory and the directory must exist.
c) The <DIR_OUT> tag indicates the output directory, where the plug-in write the responses. This tag is mandatory and the directory must exist.
d) The <DIR_ERR> tag indicates the error directory, where the plug-in write the processing errors. This tag is mandatory and the directory must exist.
e) The <EXTENSION_TOPROCESS> tag indicates the file extension for files to be processed. By default, it is set to tpr. In this example we will set it to txt. It means that in this example this listener process the files which are present in the path C:\Localhost\TCSWIFTIN\IN with file extension as txt.
f) The <REQ_SEPARATOR> tag indicates the character(s) used to separate requests. Special separators are: cr for carriage return, lf for line feed, crlf for carriage return/line feed, tab for tabulation key. By default, it is set to crlf for Windows and cr for other OS. In this example we used the <REQ_SEPARATOR> as $.
The following user(s) said Thank You: revinath
Please Log in or Create an account to join the conversation.
Time to create page: 0.076 seconds