Application program interface.
A collection of files, which is the primary unit of deployment with the .NET Framework. An assembly is self‑describing. It is used to build applications (but is not an application itself).
A feature of Synergy DBL that enables you to automate the population and maintenance of the Synergy Method Catalog. There are two attributes, xfMethod and xfParameter, each of which has a number of properties, which are used to specify metadata about your Synergy routines.
A prototype for an object. A class defines the variables and methods common to all objects in that class.
An ordered list of directories and JAR files that specifies the location of class files used by Java applications.
A non‑default data type that the Synergy data type is converted to on the client side.
An enhanced version of Microsoft’s Component Object Model (an interoperability standard that allows component objects developed in different languages to call one another). Among other improvements, COM+ handles many resource management tasks that developers previously had to program. COM+ enables you to implement pooling for xfNetLink .NET.
Not an application in the traditional sense, but rather a set of administrative data that contains information about a collection of components. To implement pooling for xfNetLink .NET, you must create a COM+ application and then add components to it.
See Synergy component.
The utility used to parse the attribute information in Synergy code and output an XML file that can be imported into the SMC.
In Java or .NET, an error.
Global assembly cache. A directory structure in which a .NET application will look for assemblies. Assemblies placed in the GAC are considered “public”, enabling a single copy of the assembly to be used by multiple applications.
A utility that generates an XML file from method definitions in the SMC and structure definitions in the repository.
Refers to the machine on which xfServerPlus is running.
Hypertext Transfer Protocol. The client/server TCP/IP protocol used on the World Wide Web for transferring HTML documents.
The process used to create an instance of a class (i.e., an object). A class is a prototype; when you instantiate a class, you create an object with the attributes of that class.
Methods are grouped into interfaces for inclusion in a Synergy component. The interface name becomes the class name in the generated component.
A Java archive file. A JAR file is a collection of compressed Java class files, similar to a ZIP file. JAR files provide a way to distribute numerous class files together. The classes in a JAR file can be used by a JSP or Java application without unpacking the archive.
An interpreted language used to write applications, applets, and JavaServer Pages.
A stand‑alone program written in Java that can run outside a browser.
JavaServer Pages (JSP)
A webpage that combines HTML and code written in
Java. When a browser requests a JavaServer Page, the web server executes
the embedded code, allowing the webpage to interact with databases and
other programs. For more information about JSP, see www.oracle.com/technetwork/
java/javaee/jsp/index.html in the Java section of the Oracle website.
Java Runtime Environment (JRE)
The runtime for Java applications. The JRE includes the JVM, the Java core classes, and supporting files.
Java Virtual Machine (JVM)
The Java interpreter. A web browser must contain the JVM (i.e., must be Java‑enabled or Java‑compliant) to run applets or JavaServer Pages.
Method Definition Utility. The application used to add, modify, and delete information in the Synergy Method Catalog. The MDU also has facilities for importing and exporting methods from the SMC.
A unique, 31‑character value in the Synergy Method Catalog. xfServerPlus uses this value to look up the routine to call. On xfNetLink Synergy, this value is also used in the client code to reference the Synergy routine.
A 50‑character value that you create to reference the Synergy routine. On xfNetLink Java and xfNetLink .NET, this value is used in the client code to invoke the Synergy routine.
A programming technique that requires code to be an isolated functional unit with a well‑defined, published interface (i.e., an argument list).
An assembly that has been pre‑compiled for the particular platform it is running on. An assembly installed as a native image is installed in the GAC with the ngen.exe utility.
Network connection ID. See below.
The ID returned by %RX_START_REMOTE. The network connection ID is a handle to a memory structure containing information that describes the location and state of the xfServerPlus session that was created. Used by xfNetLink Synergy.
A class that has methods. Procedural classes are created from the interfaces in the SMC. Compare with structure class.
A server that substitutes for another server. It intercepts messages and routes them where they need to go. Proxies are usually used for security reasons. For example, in xfNetLink Java, the SynergyWebProxy receives requests from Java and negotiates with xfServerPlus.
Routine call block. See below.
routine call block
A block of memory that contains the information necessary—routine name, ELB, and arguments—to make a routine call. You can use a routine call block to make remote calls with xfNetLink Synergy.
Methods included in the generated JAR file, which can be used to set properties used by xfNetLink Java, such as the host name and port, log filename, and time‑out values.
Synergy Method Catalog. Identifies the Synergy routines that you have prepared for remote calling. The SMC includes information such as the function or subroutine name, the ELB or shared image it is stored in, and the type and length of its parameters.
strong name key file
A file used to sign a .NET assembly, which usually includes a public and a private key that are subsequently embedded into the assembly.
A class that has only properties, which represent fields in a structure. Structure classes are built from structures in the repository, which are referenced in the SMC. Compare with procedural class.
An array of structures with a variable number of elements.
Refers to a .NET assembly that references Synergy methods.
A general term that can refer to a Synergy JAR file or assembly.
A Synergy function or subroutine that has been made available for use with xfNetLink. Synergy methods must be contained in an ELB or shared image and must be defined in the Synergy Method Catalog. Not to be confused with Synergy object‑oriented methods.
An xfNetLink Java class that is instantiated in order to establish a connection between xfNetLink and xfServerPlus and to make calls to Synergy routines via xfServerPlus.
See coerced type.
Refers to the standard methods that are included in every Synergy JAR file and assembly. These methods enable you to perform utility functions such as connecting, setting a time‑out value, and running a debug session.
Extensible Markup Language. XML is a syntax, developed by the World Wide Web Consortium, for creating your own markup language. It is a simple text stream that contains text and markup codes (tags).