Pats 0 Systems Management Guide

2.0 Java Enterprise Developer Workstation

PATS Java enterprise developer workstations are dependent on remote and local services. All VA Java service dependencies are deployed locally while Business Objects Enterprise and Oracle were utilized remotely.

2.1 Development Platform

The following infrastructure developed PATS on Windows workstations:

Application	Description
WebLogic Server (WLS) 8.1 sp 4 (or higher)	All service dependencies are required to be setup on a local WebLogic server.
Eclipse 3.2.2 and MyEclipse 5.1.1	Integration of Eclipse and WebLogic 8.1 allowed hot deployment and hotswap debugging.
Dreamweaver MX	HTML and JSP files were aligned and cleaned in Dreamweaver.
Microsoft Visual Source Safe	Source control management
Oracle 11g and TOAD	TOAD was used to develop Oracle objects (tables, procedures, etc.). Oracle 11g is where the data is stored.
Business Objects Enterprise XI sp1	For developing and deploying standard and ad hoc reports.

2.2 Development Projects

PATS’ development structure is comprised of multiple dependent projects in the eclipse interactive development environment. These projects are:

Project	Description
etc	Base project containing master build scripts, runtime libraries, development libraries, deployment descriptors and configuration files
patscommon	PATS domain object archive and generic utilities, depends on etc
patsdao	PATS data access object archive, depends on patscommon
patsejb	PATS ejb and notification archive, depends on patsdao
patsreport	PATS reporting archive, depends on etc
patsdelegate	PATS delegate archive, depends on patsejb
patsweb	PATS web user interface archive and PAD servlet, depends on patsejb and patsreport
patstest	PATS cactus tests, depends on patsdelegate
patstestclient	Junit helper classes for running cactus tests from a remote client, depends on patstest
patsreporttest	Junit tests for PATS reporting, depends on patsreport

2.3 Development Tools

During development, deployment of PATS is done using the ANT build file in etc (for building PATS without unit tests) or patstest (for building PATS with unit tests). PATS can be deployed in two basic ways on Weblogic:

• 
  as an uncompiled EAR (see the PATS-WLS-EAR target in etc/build.xml)
  

or

• 
  a WebLogic application compiled exploded directory structure (see the zip-compiled target in etc/build.xml.)
  

2.3.1 ANT

ANT 1.7 is the build tool for PATS. Each project contains a build file in the root directory named build.xml and where applicable an xdoclet-build.xml.

2.3.2 XDoclet

All Java enterprise deployment descriptors are generated by XDoclet 1.2. The following Xdoclet files are merged together with XDoclet Annotations from Servlets, taglibs, filters and EJBs. Xdoclet merge files are contained in the etc/merge directory for a given project.

2.3.3 Log4j

Apache Log4j 1.2 is PATS logging framework.

2.3.4 Libraries

Additional libraries (located in the Java project etc’s lib directory) necessary for development and/or building of PATS are:

File Name	Description/Source Project
Aspectjrt-1.2.1.jar	Aspectj
Boconfig.jar	BOEXI
cactus-1.7.jar	Apache Jakarta Cactus
cactus-ant-1.7.jar	Apache Jakarta Cactus
cdzlet.jar	BOEXI
cecore.jar	BOEXI
celib.jar	BOEXI
ceplugins.jar	BOEXI
cereports.jar	BOEXI
cesession.jar	BOEXI
ceutils.jar	BOEXI
cexsd.jar	BOEXI
classes12dms.jar	Oracle
commons-beanutils.jar	Apache Jakarta Commons
File Name	Description/Source Project
commons-collections-3.0.jar	Apache Jakarta Commons
commons-collections.jar	Apache Jakarta Commons
commons-digester.jar	Apache Jakarta Commons
commons-discovery.jar	Apache Jakarta Commons
commons-httpclient-2.0.1.jar	Apache Jakarta Commons
commons-httpclient-2.0.2.jar	Apache Jakarta Commons
commons-logging-1.0.4.jar	Apache Jakarta Commons
commons-logging.jar	Apache Jakarta Commons
commons-resources.jar	Apache Jakarta Commons
commons-validator.jar	Apache Jakarta Commons
CorbaIDL.jar	BOEXI
ebus405.jar	BOEXI
Httpunit-1.6.jar	BOEXI
j2ee-1.3.jar	Sun
jasper-compiler-4.1.30.jar	Apache Jakarta
jasper-runtime-4.1.30.jar	Apache Jakarta
jrcerom.jar	BOEXI
junit-3.8.1.jar	Junit
kaajee_1.0.1.003.jar	KAAJEE
keycodeDecoder.jar	BOEXI
log4j-1.2.8.jar	Apache Logging
MetafileRenderer.jar	BOEXI
nekohtml-0.9.1.jar	Apache
nls_charset12.jar	Oracle
org.mortbay.jetty-4.2.17.jar	Mortbay
rasapp.jar	BOEXI
rascore.jar	BOEXI
ReportPrinter.jar	BOEXI
ReportTemplate.jar	BOEXI
rpoifs.jar	BOEXI
Serialization.jar	BOEXI
servletapi-2.3.jar	Sun
u211java.jar	BOEXI
vljConnector-1.5.1.002.jar	VLJ
vljFoundationsLib-1.5.1.002.jar	VLJ
File Name	Description/Source Project
webi.jar	BOEXI
webreporting-advanced.jar	BOEXI
webreporting-core.jar	BOEXI
webreporting-jsf.jar	BOEXI
webreporting.jar	BOEXI
WebReportWizard.jar	BOEXI
wilog.jar	BOEXI
xdoclet-1.2.jar	Xdoclet
xdoclet-bea-module-1.2.jar	Xdoclet
xdoclet-ejb-module-1.2.jar	Xdoclet
xdoclet-Java-module-1.2.jar	Xdoclet
xdoclet-web-module-1.2.jar	Xdoclet
xdoclet-xdoclet-module-1.2.jar	Xdoclet
xercesImpl-2.7.1.jar	Apache
xml-apis-2.7.1.jar	Apache

2.3.5 Junit and Cactus

Junit 3.8 and Cactus 1.7 are PATS unit testing tools.

2.3.6 Rational XDE

All Rational XDE model files are stored in the root of each PATS project.

2.3.7 Maven

Maven can be used for running Junit tests in PATS and to generate site reports. A project.xml is located in the root of each Java project.

2.3.8 PAD Tools

The PAD servlet API is driven through SOAP XML requests sent from an external system. To facilitate local development and testing, the following classes and jsp pages were developed to simulate the external service consumer since both service endpoints cannot be reasonably expected to be available in all development environments.

• 
  /public_html/jsp/pad/PadServletTool.jsp
  
  • 
    Utilizes gov.va.med.pats.pad.tools.PadServletTestTool.java
    
  • 
    This page and backing java class act as the service consumer and allows the developer to input direct XML messages to send to the PAD servlet.
    
  • 
    This page also will collect the response XML data sent back from the PAD servlet after ROC creation and mimic the behavior of the consuming system upon receiving the response.
    
  • 
    To access this tool, deploy PATS to your local weblogic instance and navigate to http://localhost:7001/PATS/pad.servletTool
    
• 
  /public_html/jsp/pad/PadTool.jsp
  
  • 
    Utilizes gov.va.med.pats.pad.tools.PadTestToolServlet.java
    
  • 
    This page and backing java class acts as a wrapper around the PAD interface in order to directly invoke the ROC parser. The interface will display actual XML received by the PAD servlet and actual XML response data sent back after ROC creation.
    
  • 
    To access this tool, deploy PATS to your local weblogic instance and navigate to http://localhost:7001/PATS/pad.padTool
    
• 
  To enable the PAD development tools, set ‘enable.pad.tools=true’ in the patsweb.properties file.
  

In lieu of using the built in servlet test tools, developers may also utilize external SOAP testing tools such as SOAPUI to send XML to a local PAD instance.