Publication: SecureTransport 5.3.0 Developer Guide

The code for an in-process agent can be either a java class (.class) file or contained within a .jar file. This .jar or .class file must be installed on the same machine as the SecureTransport Server which contains the Transaction...

Publication: SecureTransport 5.3.0 Developer Guide

This agent, triggered by the Outgoing end event, shows how to delete a transferred file after you finish downloading it. The example also shows how to implement logging using log4j. Log entries are created and stored in the tm.log file...

Publication: SecureTransport 5.3.0 Developer Guide

This agent, triggered by the Incoming Start event, prevents uploading of files with an .exe extension.

Publication: SecureTransport 5.3.0 Developer Guide

The following topics provide information about implementing in-process agents:

Publication: SecureTransport 5.3.0 Developer Guide

The Events class in the package com.tumbleweed.st.server.api contains definitions related to the content of events. Included are definitions of event types, as well as event environment variables and values. Environment variable names are particularly useful when writing agents to make...

Publication: SecureTransport 5.3.0 Developer Guide

The following topics provide a few examples to illustrate how agents can be installed and used:

Publication: SecureTransport 5.3.0 Developer Guide

When Transaction Manager executes an agent, input data is passed to the agent, and the agent returns a set of results. The following topics describe how the in-process agent receives the input data and produces the results:

Publication: SecureTransport 5.3.0 Developer Guide

After developing an in-process agent, you must install it in order to use the agent. You can install multiple agents in one jar file or install each agent in a separate class file. If you have additional jar files that...

Publication: SecureTransport 5.3.0 Developer Guide

Each example is accompanied by a README text file containing a detailed description of building, installing, and testing the agent. Each example has an XML file for the rules package and the .java source files.

Publication: SecureTransport 5.3.0 Developer Guide

In-process agents can use the log4j framework for flexible logging. Transaction Manager uses the log4j configuration file /conf/tm-log4j.xml. Agents that don't require flexible logging can use the method IAgentAccess.logAgentError. This method places an error entry in the Transaction Manager log...

Publication: SecureTransport 5.3.0 Developer Guide

In the Transaction Manager, rules are used to trigger actions that are performed when certain conditions are met. Each action calls one or more agents. Multiple actions can be triggered as a result of a single condition.

Publication: SecureTransport 5.3.0 Developer Guide

Axway SecureTransport is part of the Axway family of managed file transfer (MFT) products. SecureTransport allows organizations to adeptly control and manage the transfer of files inside and outside of the corporate firewall in support of mission-critical business processes, while...

Publication: SecureTransport 5.3.6 Developer Guide

Axway strives to create accessible documentation for users. The following describes the accessibility features of SecureTransport documentation.

Publication: SecureTransport 5.3.0 Developer Guide

Related topics:

Publication: SecureTransport 5.3.0 Developer Guide

The AccountManager is a programmatic method of manipulating users and accounts that allows customized management of accounts in SecureTransport. It provides methods to create, retrieve, update, and delete accounts and their associated authentication information. There are also methods to authenticate...

Publication: SecureTransport 5.3.0 Developer Guide

Clustered Manager provides a facility for making remote procedure calls (RPC) from one node of a standard cluster to another. Although this functionality is not limited, it is most useful for keeping database objects synchronized. The solution is ad-hoc, so...

Publication: SecureTransport 5.3.0 Developer Guide

Using the Configuration Manager API you can manipulate server configuration options (also called parameters) and export rules that enable synchronization between the system configuration and configuration files. Class ConfigurationManager depends on st-server-api.jar.

Publication: SecureTransport 5.3.0 Developer Guide

Using the Invocation Manager API you can execute a task on all servers in a large enterprise cluster. All classes depend only on st_server_api.jar.

Publication: SecureTransport 5.3.0 Developer Guide

You can use the Navigation Manager API to manipulate objects related to navigation entities. Class NavigationManagerDevGuide depends on st-server-api.jar.

Publication: SecureTransport 5.3.0 Developer Guide

You can use the Service Check API to check if a SecureTransport service is functional or not. Class ServiceCheckDevGuide depends on st-server-api.jar.