Summary:

• The code for CAWIS external and internal is in one repos (CAWIS-SWIMN)

• There are separate URLs for CAWIS External and Internal.

  • CAWIS External has the Admin functionality down because it is accessible outside TC.

  • Administration of CAWIS is done via CAWIS Internal.

    • Until Spring, we did not have a separate development environment for CAWIS external. It only existed for acc and prod. At the moment, the profile info outlined below also applies to the development servers for CAWIS external and CAWIS internal.

Profiles:

• When publishing, we have to use the correct profiles. Using the incorrect profile for CAWIS External will expose administrative functionality to users outside TC.

To publish CAWIS External use the “Staging” profile

Publish to the server path for the “long-form”.

1. Login using the TC Login option.

2. Select Code Tables from the menu.

3. The screen should be per below for CAWIS External on Development, Acc and Prod.

Open

To publish CAWIS Internal use the “Acc” profile.

Use the “ACC” profile.

1. Login using the TC Login option.

2. Select Code Tables from the menu.

3. The admin functionality is available.

Post two separate files to the staging location. One for CAWIS External and the other for CAWIS External.

• See Change Request: CRQ 4466: CAWIS Production: Fix letter distribution bug. Refer to the install plan.6.

Some general recommendations for publishing:

• change the publish location to your local drive. Publishing directly to the servers is a problem because if the connection is interrupted what you deployed could be “corrupt”.

• Make a backup of the existing files on the server first. The backup locations for each environment are provided in Confluence.

• Delete the web.config from the local output folder you published the package to. The purpose is to prevent accidentally overwriting the server’s web.config.

  • For CAWIS, there is no need to update the modified date in the web.config as it is based on the date when the app was built/published.