appmt: Appointments

Eclipse development environment:

1. follow the Installation guide (maven)

2. Clone the following repos

fabric-r01f
fabric-aspect
fabric-r01fBusinessServices
fabric-r01fCOREServices

3. Import projects in [eclipse]
   Tips:

   • use [maven] > [update project] a few times until the projects compile
   • start with [r01fProperties]
   • next [r01fBase]
   • next all projects
   • Usually [r01fXXAspectClasses] need an independent build: just select the projects manually and issue manual build: [project] > [clean] (only selected projects)

4. Clone appointment repos

appointments-appmt00
appointments-appmt01
appointments-appmt00ConfigByEnv

5. Configure a hotdeploy tomcat

Configure a hotswap jdk
Configure a [tomcat] server using the previously configured [hotswap jdk]
... do NOT forget to set the [tomcat] jvm argument that enable [aspectj weaving]:

-javaagent:c:/develop/local-libs/aspectj/lib/aspectjweaver.jar -Daj.weaving.verbose=true -DR01_Home=c:/develop -DR01-ENV=default

6. Configure the DB connection

Look for aa14b.appointments.dbpersistence.properties.xml file and review the [db connection] properties and the [schema generation] property

When started, the [db tables] will be automatically created

7. Configure the notifier properties

Look for aa14b.appointments.notifier.properties.xmlfile

Properties

Properties are splitted in TWO parts

• Environment independent properties: located at [appmt00/appmt00Config]
• Environment dependent properties: located at [appmt00ConfigByEnv]

Usually the [env INdependent] properties contains properties that DO NOT change within environments while the [env dependent] properties contains those properties specific to a certain environment (say, dev, test or prod): things like paths, users, passwords, etc

When started, the system mixes the [env INdependent] files with the [env dependent] files to create a single file

The [env INdependent] properties layout is like

[xxConfig]
	+ properties

Then [env dependent] properties are stored in a single repo and splitted by [env id] like:

[xxConfigByEnv]
	+ default
		+ properties
	+ des
		+ properties
	+ test
		+ properties
	+ prod
		+ properties

All properties files are bundled as JARs inside the app so there will exist TWO properties JARs

+ xxConfig.jar 
+ xxConfigByEnv.jar

... so the app artifact will contain properties for ALL environments and a clue to know which environment properties to use is needed. Use a JVM argument named R01-ENV={env name} when starting the appserver ie: -DR01-ENV=des

DB connection

The DB connection is usually configured at the aa14b.appointments.dbpersistence.properties properties file. The [env-INdependent] file usually does NOT need to be modified; set the [db connection] at the [env-dependent] file: {env}/aa14b.appointments.dbpersistence.properties

Set the connection type: DRIVER MANAGER or DATASOURCE (only for app servers like weblogic)

<persistence unitType='DRIVER_MANAGER / DATASOURCE' ...>

Depending on the configured unitType look for the corresponding <unit type=> section

For example, for a DRIVER_MANAGER MySQL the connection properties are:

<unit type='DRIVER_MANAGER'
	  targetDB='MySQL 8.0'		<-- ie Oracle 11.0 or MySQL 8.0

	<connection vendor='MySQL'>
		<javax.persistence.jdbc.user>pci</javax.persistence.jdbc.user>
		<javax.persistence.jdbc.password>pci</javax.persistence.jdbc.password>
		<javax.persistence.jdbc.driver>com.mysql.cj.jdbc.Driver</javax.persistence.jdbc.driver>
		<javax.persistence.jdbc.url><![CDATA[jdbc:mysql://localhost:3306/pci?useUnicode=true&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC]]></javax.persistence.jdbc.url>
	</connection>
</unit>

BEWARE that the db-tables are auto-created / extended; use the schema/generationMode property:

<generationMode>CREATE_OR_EXTEND_TABLES</generationMode>	<!-- NONE / DROP_AND_CREATE_TABLES / CREATE_OR_EXTEND_TABLES / DROP_TABLES / CREATE_TABLES -->

When tables are created, a file with the ddl-script is created at {dev-home}/db/ddl-scripts/aa14b so ensure this folder exists or the tables will not be created

web resource files (images / scripts / styles...)

Web resource files are splitted in TWO projects:

• appmt00/appmt00UI/appmt00UIWebContent: initiative INdependent files
• appmt01/appmt01UI/appmt01UIWebContent: initiativa dependent files

the [web content] is at a folder named aa14aAppointments that is exposed as an alias appcont/aa14aAppointments so:

a. Copy the content of both appmt00UIWebContent and appmt01UIWebContent to a web-server folder and set an alias named appcont/aa14aAppointments

b. create a proxy to the tomcat server

Alias /appcont/aa14aAppointments ${projects-root}/aa14aWebContent/aa14aAppointments
<Directory "${projects-root}/aa14aWebContent/aa14aAppointments">
	Options Indexes FollowSymLinks MultiViews
	AllowOverride None
	Require all granted
</Directory>

# Proxies
# Send everything for context /examples to worker named [localhost_tomcat] (ajp13)
# and defined at conf/pci/workers.properties
#JkMount  /appmt01UIWar/* localhost_tomcat

# Use mod_proxy instead of tomcat ajp13
<Location /appmt01UIWar>
	ProxyPass http://localhost:8080/appmt01UIWar
	ProxyPassReverse http://localhost:8080/appmt01UIWar
</Location>