Important Installation Notes

By default, the Healthcare Pack Installer checks whether any of the artifacts listed above exists, and makes modifications to the MySQL installation or to the runtime environment based on whether they are found. If the artifacts already exist, the installer updates your environment as follows:

• If a database schema named midm or arrdb exists in MySQL, it is dropped and replaced.

• If a database user named mdm or arr exists in MySQL, it is dropped and replaced.

• If a connection pool named cpPatientXA, cpPatientSequenceXA, or MyArrdbPool exists, the installer will not create the new connections pool nor will it update the existing one. The same goes for their corresponding JDBC resources.

• If a JMS destination named PatientTopic, tHL7V3, tHL7V2, tSUNXDS, or tXDSMerge exist, the installer will not create the new destination nor will it update the existing one. The same goes for their corresponding JMS resources.

• If a user named mdm, atna, or pixadmin exist in the GlassFish file realm, the user is updated by the installer.