Tutorial 2: Starting the PointBase Development Database
This tutorial describes how to start the PointBase database management system so that the MedRec application can use it to store application data.
In particular, the tutorial shows how to:
Start the PointBase database.
Use the PointBase console to view the tables in the database used by the MedRec application.
Note: The installation of PointBase shipped with WebLogic Server is already set up with the database tables and data used by the MedRec application. For information on viewing the already-created tables, see Step 2: Use the PointBase console to view the MedRec tables and data.
Step 2: Use the PointBase console to view the MedRec tables and data.
The installation of PointBase shipped with WebLogic Server is already set up with the database tables and data used by the MedRec application. To view these already-created tables, use the PointBase Console.
Use the scripts in the PointBase tools directory to start the database and invoke its console. See:
c:\bea\weblogic81\common\eval\pointbase\tools
The Big Picture
The MedRec application uses the PointBase database management system:
To store information about patients, physicians, and administrators who manage the workflow of the MedRec application.
As the JMS JDBC store that contains persistent JMS messages.
Patient, Physician, and Administrator Data
The MedRec application uses container-managed entity EJBs to automatically persist information about patients, physicians, and administrators in the PointBase database. The following table lists these entity EJBs and the PointBase tables in which the information is persisted.
Entity EJB
Application That Uses the EJB
Corresponding PointBase Table
Description
AdminEJB
Administration
ADMIN
Information about the administrators that manage the workflow of the MedRec application. Administrators handle patient requests.
AddressEJB
Administration, Patient
ADDRESS
Used by the PATIENT, PHYSICIAN, and ADMIN tables to store their respective addresses.
PatientEJB
Administration, Patient
PATIENT
Information about patients, such as name, address reference to the ADDRESS table, SSN, and so on.
PhysicianEJB
Administration
PHYSICIAN
Information about physicians, such as name, address reference to the ADDRESS table, phone, and email.
PrescriptionEJB
Patient
PRESCRIPTION
Describes a prescription, such as the prescribed drug, the dosage, frequency, instructions, and so on. Also includes the patient ID, the ID of the prescribing physician, and the particular visit that instigated the prescription.
RecordEJB
Patient
RECORD
Describes a single patient visit to a physician. Includes the patient ID, the physician ID, the date, the symptoms, diagnosis, and the vital signs of the patient.
UserEJB
Administration, Patient, Physician
USER
Lists all users (patients, physicians, and administrators) who are authorized to log into the MedRec application. After a user is authenticated, the application retrieves additional information from the appropriate table (PATIENT, PHYSICIAN, OR ADMIN).
VitalSignsEJB
Patient
VITALSIGNS
Describes the vital signs of a patient for a particular visit. Vital signs include temperature, blood pressure, height, weight, and so on.
Persistent JMS Message Storage
The MedRec application uses persistent JMS messaging, which means that any JMS messages that are put in a queue are also stored in a database so that the messages can be retrieved in case a problem occurs (such as a server crash) before the message-driven bean is able to process them. The messages are stored in the following two PointBase tables:
MEDRECJMSSTATE
MEDRECJMSSTORE
These tables are generated automatically when you create the JMS JDBC store using the Administration Console and are used internally by JMS.