7.8  Getting run time server info 

The server applications are logged. The easiest way to extract this info at run time is to load 

serverinfo.jsp

  with a web browser. The JSP file is included in 

fixit42_j_tools.zip

 (see chapter 3.2). 

Note that you have to load the JSP file 

as a web document

, not directly from a local disk. 

The serverinfo.jsp provides run time information about: 

Users that are logged in  

Users that have logged out 

e FixIT application server uptime 

IP addresses of users 

The JSP file also provides information about Web Service objects that are built using 

xfij.webserver.WebServiceBase

 classes. See more information about these services in chapter 10. 

8.  Deployment phase 

The easiest way to distribute an e FixIT application is to copy all your class & JSP files to the server and 

set up an environment needed to run the applications (XFIJ component packages etc.). Do not forget to 

include the actual application's class files to J2EE_CLASSPATH variable (chapter 3.3) if you are using 

J2EE Reference Implementation. 

Another way to distribute the application is to use a tool such as JBuilder's 

Archive Builder

 and use it to 

create a WAR (Web ARchive) containing all the needed class files. This way you only need to distribute a 

single file. By default, the 

Web Start Application

 type of archive also builds a WAR file of all the 

project's files (see chapter 6.3.2). You will need JBuilder5 Professional or higher to do this. 

If you are using J2EE, you can also use the 

J2EE Application deployment tool

 to both create and 

deploy a WAR (Web ARchive) file. J2EE documentation contains more information about creating & 

distributing WAR files and can be downloaded with the J2EE package. Also JBuilder Pro or Enterprise 

can build WAR files from your project. 

8.1  Environment parameters in WAR files. 

You can  also include your M server's address (

server

 and 

port

)

as environment parameters in your 

applications WAR file if you are using a J2EE compliant server or your WWW server supports Java 

Naming and Directory Interface (JNDI). For example, if your applicationName property is set to 

DemoLabTest

, you  set  can parameters  DemoLabTest/Server  and  DemoLabTest/Port . Below is a 

picture of such using J2EE Deployment tool from Sun's J2EE reference implementation. 

30