Why Fat Clients and EJBs nils wallandervolvo com

Why Fat Clients and EJB’s nils. wallander@volvo. com

Agenda • • • Background System overview Development techniques Technical arhitechture Things to think about using CFB Converter Live demonstration

Background • Volvo Logistic’s had an old system based on – Microsoft NT server – Microsoft Access as the data source – Computers placed at the Planners office • Requirements for a more robust system

The Business

The Business

TPS Workflow Chart

Overview of special Features and support technologies TPS Ø Graphical Representation of Information Ø Drag and Drop Capabilities Ø Right Click Menu Ø XML Reporting Ø Workflow control

TPS MAIN SCREEN

Navigation Diagram

TPS ARCHITECTURE WINDOWS TPS WEBSPHERE Application Model Component Model Client Logic idep OLE Controls XML Reporting cdep idep mdep cdep DB 2 Database Server Logic FLT PC TIR mdep INTEGRATION S E-VMS Workflow Rules SECURITY SYSTEM QAT MHS Message Handling System

Overview of special Features and support technologies OCX OLE CONTROLS Graphic Control Graphical Representation Drag and Drop Capabilities Popup Menu Right Click Menu Help Balloon Configurable Logic XML & QAT Functions Help Balloon Workflow control XML Reporting control Planner Movements Refresh Routines on Planning View of Overview, Planning views Designer Movements and Layout Painter Tool on Layout Tool Right Click Menu Options Help Balloons Workflow Driven Database of Planning view of Overview, Planning views Changing at Planning view Reporting and HTML presenting

TPS Integration PLANNER UNITS TIR SYSTEM UNITS V-EMS SYSTEM New Jobs Login/Layout Accept/Reject Job Progress FLT – PC Application

Design Layers Graphical Framework Layer User Events Metadraw Control User Events Graphical Action Blocks Detecting/Handling Graphic Preparing/specific Action Blocks Interpreters React Process Refresh Process Client Procedures Database OBJECT_LIST_SERVERS UPDATE/WORKFLOW SERVER Database

TPS Workflow Engine REFRESH User Events EVENT + Graphical Element Business Object ? Business Object Data Workflow Step ? Object + Workflow Step Actions Options Possible Actions ? Selected Option Database Updates ? WORKFLOW STRUCTURED RULES Database Update Actions (by depot area / Routine) DB

What is a Depot Planning System? • Goods arrive to the Volvo Logistic Depot – With trucks or with boat • The trucks have to be directed to an empty area where a fork lift truck can unload the truck • Notification has to be sent to the Fork Lift Truck driver to drive to the area • And much more….

Fake Demonstation • This demonstration will show you how the Depot Terminal system works when a truck arrives to the Depot

Development Techiques • All. Fusion Gen 6. 5 – Servers are EJB’s – Clients Gen C clients – Com proxy for Web. Services • Handwritten Web. Services – For the communication with Fork Lift terminals

Development Techniques • Why EJB’s as Servers and not IMS – Refresh technique of the Depot area should be cheaper within an Application Server – Several components available in jar files Why Fat clients – The requirement for drag and drop • Why Web. Services – Easy way to communicate with the Fork Lift terminal

Technical Architechture Windows XP Workstation TCP/IP Fork lift terminal Web. Sphere 5. 1 CFBC Server RMI over IOOP EJB JDBC Web Server HTML Windows 2003 Server DB 2

Configure the CFBC Server • When you run Deploy (Assembly) in the Build tool a <ear-name>_dpy. jar is created for each EJB – Contains the portable interface definitions for the EJB – Is used by the clients to call the EJB • All _dpy. jar must be copied from the build machine to the CFBC Server and placed in the classpath

Configure the CFBC Server • Depending upon what Application Server your EJB is running on you need to copy – Runtime jar files from your Application Server to the CFBC Server. • Which one you need to copy is not documented • Trial and terror work – Must be in the classpath of the CFBC Server

Configure the CFBC Server • It looks like the JSDK must be installed and in the classpath for the CFBC Server

Configure the CFBC Server • We should like to have prefix on our EJB’s – Like ejb/T 425/Customer_read_s • Where ejb/T 425/ is the prefix • Customer_read_s is the procedure name and is always set by All. Fusion Gen as the EJB JNDI name – In All. Fusion Gen 6. 5 you can not set this but we a custom build function to add the prefix at deploy time • We can not get it to work with the CFBC server