Open topic with navigation
Once you’ve created and deployed your JAR file, it is ready for use in a JSP or Java application. The machine used by the Java developer must be properly configured. See Setting up your environment for development.
If you are using Java connection pooling, follow the steps in Using your JAR file with connection pooling instead of the steps in this topic.
|1.||Associate the component with your project|
Before using the JAR file, you’ll need to associate it with your project in your development environment. The method for doing this depends on the environment. If you are using Workbench, first make sure your project is the active project. Then, select Project > Project Properties. On the Files tab, click the Add Files button, navigate to the JAR file, and add it.
You can view the methods in the JAR file using the object/class browser supplied with your development environment. In Workbench, go to the Symbols tab in the project toolbar and expand the Packages/Namespaces node under the Workspace node. You’ll see a node for your JAR file. Expand it to see the classes in your JAR file. Expand the classes to view your own methods, along with the xfNetLink Java utility methods. The utility methods enable you to establish a connection with xfServerPlus, disconnect from xfServerPlus, and perform other utility functions, such as setting properties and running a debug session. See the Method reference for a complete list of utility methods.
|2.||Import the necessary packages|
The import statement enables you to more easily access the classes in the imported package.
For Java applications, include an import statement for your package so that you can easily access the classes in your JAR file. For JSP applications, you do not need to import your package.
For example, in a Java application:
|3.||Instantiate an instance of a procedural class|
There are two constructors included in procedural classes: the default constructor and the “ini file” constructor.
The default constructor takes no parameters. Use it in the following circumstances:
For example, to use the default constructor in a Java application:
AppLogin appLog = new AppLogin();
Or, in a JSP page:
<jsp:useBean id="appLog" scope="session" class="ConsultIt.AppLogin">
The “ini file” constructor enables you to pass a Java String naming a specific properties file. Use it when your properties file is not named xfNetLnk.ini.
For example, to use the ini file constructor:
AppLogin appLog = new AppLogin("myPropFile.ini");
|4.||Set properties for the client|
If you are not using a properties file, use the set methods in the class to set the properties for xfServerPlus host name and port and logging options. If you are using a properties file, you can override individual settings in it by using the set methods. See the Method reference for a complete list of the set methods.
You must specify the host name and port either with the set methods or in a properties file. The other properties are optional.
appLog.setxfHost("elmo"); appLog.setxfPort(2356); appLog.setxfLogging(true); appLog.setxfLogfile("c:\\temp\\consult.log");
|5.||Connect to xfServerPlus|
There are several ways to establish the connection with xfServerPlus.
When you use connect(), you are instantiating an SWPConnect object, which then becomes a property of your object. The SWPConnect object is the actual connection to your xfServerPlus machine.
In the example below, we instantiate two new procedural classes and use the connect() method to establish a connection for one of them. We then instantiate the xyz object to hold the connection, and use the getConnect() method to get it. Finally, we call the shareConnect() method of the consult object and pass the xyz object. You can pass the same xyz object multiple times to share the connection among several objects.
AppLogin appLog = new AppLogin(); Consultant consult = new Consultant(); appLog.connect(); java.lang.Object xyz = null; xyz = appLog.getConnect(); consult.shareConnect(xyz);
In the example below, the consult object is instantiated, and then the postCharge() method is called, without first calling the connect() method.
Consultant consult = new Consultant(); consult.postCharge(charge, return_msg);
|6.||Invoke methods in the component|
Make calls to your Synergy methods and pass the parameters. If you generated Javadoc for your JAR file, it will include the information necessary to use the methods, such as the parameter data types.
Parameters that were not flagged as required in the SMC were converted to required parameters when you generated the Java class wrappers because you must always pass all parameters in Java.
For example, to invoke the login() method in the AppLogin class:
String id = new String("MFranklin"); String password = new String("123abc"); appLog.login(id, password);
|7.||Disconnect from xfServerPlus|
If you connected to xfServerPlus using the connect() method, you must disconnect using the disconnect() method. If you have multiple objects sharing a connection, xfServerPlus will not completely close the connection and release the license until all objects are disconnected.
See Appendix E: xfNetLink Java Sample Code for a complete JSP code sample.