Oracle library

Different versions of the Oracle library are required for running some applications locally vs deploying them to development, acceptance and prod.

Projects we know this applies to:

• eMER

• CAMIS (need to check)

• Others?

Refer to Selecting the correct oracle library for the steps.

Once code has passed testing in your local development environment:

• create a PR for review.

• deploy the code to development. Currently there is no pipeline for this so the deployment has to be done manually.

• Ask another developer to test your code in development.

Identifying the development environment path to deploy to:

1. Go to Applications and selecting the page for the project that you are deploying.

   1. For example, if deploying eMER to the development environment, select the eMER page

2. The location to deploy to is listed in the Environment Access Information section.

3. The path to deploy to is listed under “UNC”.

   1. Some projects might have more than one development environment environment.

      1. For example, eMER is deployed to:

         1. an unsecure instance where authorized users are automatically logged in when they click the URL.

         2. a secure location such as GCKey.

Deploying your code:

1. Navigate to the target path.

   1. For example, navigate to the path for the eMER unsecure development environment

2. Copy the content of the folder to a temporary location on your local machine.

   1. Important: you will need the web config that you have copied as the last step of your deployment process.

3. Publish your changes locally

   1. Create publish settings in visual studio

   2. create a different folder - don’t use the one from step 2.

   3. create a new custom profile

   4. Keep the default location bin\app.publish

   5. Finish

   6. Save

   7. Publish

4. Update the development location with your changes:

   1. Go to the deployment location for the project

   2. delete everything

   3. copy the files (except web config) from the folder you created in step 3 and paste them in the deployment location.

   4. copy the web config from the backup made in step 2 and paste it into the deployment location

      1. This will trigger the update of the deployment.

5. wait 5 or 10 minutes.

6. Test that the project you deployed is working.