Demo Servers - tsgrp/hpi GitHub Wiki

TSG has the following demo servers to use:

• Documentum Release - http://release1.tsgrp.com
  • Built from trunk, approximately twice a month
• Alfresco Release - http://release2.tsgrp.com
  • Built from trunk, approximately twice a month

These servers should be used for most of our demos. They are stable, reliable, and have been demoed many times. If you are looking to do a demo of cutting edge features, consider using one of the Edge Servers. These servers are built nightly from the latest and greatest codebases.

Please keep the configs located at /hpi/default/configs pristine in the release environment. This means that No client specific objects types or other OCMS configs should be placed here.

Do not change any of the configs in the release environments without talking to the OCMS Product Manager.

If you have a client specific demo, it's completely fine to use the release or edge environment provided that you are not adding any code to the application. Your demo must be config-only. If you need to update code to fake out a feature for a demo, use a different environment.

Client demo configs should be in /hpi/my-client-demo/configs

To create your configs, follow these steps:

1. Login to OCMS on release1 or release2 (or edge if you're feeling brave) as an hpi_administrator
2. Navigate to the Config Archiver in the admin. Export the application configs. It's up to you if you want user preferences to come along. This will download a default.zip
3. Rename default.zip to something like myclient-demo.zip. Use the Import tool to import the new configs.
4. Navigate to the config root folder /hpi in either DA or Share to make sure the /hpi/myclient-demo folder was created successfully and /hpi/default is untouched.
5. Delete all the content templates in /hpi/myclient-demo/hpiTemplates. Do not delete any AW Word Templates. Content templates are currently stored within the appId folder, but are application wide. If you don't do this step, all templates will be duplicated when viewing them in Bulk Upload.
6. Update permissions on the subfolders under /hpi/myclient-demo appropriately as described here. View the permissions under /hpi/default/... for examples.

Now, copy the entire /ocms webapp root folder to a separate /myclient-demo webapp folder to create the new webapp.

• In assets\ocms-require-{hash}.js
  • Update the app id by searching for {appId:" (release2) or "appId": " (edge2) and change the value from default to whatever your new application ID is
  • Update the "root" property (look about 50 chars back from the appId) to modify the root URL to whatever you copied the wabapp to (myclient-demo in the case above)
  • (Optional) - add a separate admin group to the allowedHpiAdminGroups configuration. If adding a new group, be sure to enable the group in the admin so that users can see [Admin] button in the header.
• In /assets/css/index.css
  • Update the appId for any style URLs that utilize &appId=default. Change default to your target app id.
• In /WEB-INF/jsp/index.jsp
  • Update the base URL in the <base> tag as well as in the CKEDITOR_BASEPATH and any <script> tags

Note - when going through this process, it's helpful to use the tomcat /manager/html application to start and stop individual applications vs. stopping the entire tomcat server. This way, you can work on your client demo app without disturbing the core app.

IMPORTANT - Before configuring, make a small change to something (ex: App Config) using /myclient-demo and make sure the modified date changes on the expected object (your demo config, not the config in /hpi/default/configs) just to be sure the app ID change has taken effect.

Note - The dmadmin (Documentum) and admin (Alfresco) passwords are not available for general use. You should NOT be logging in as these users for demos or edge testing!

The users below are already configured for use in the demo environments. Feel free to use any of the "fake" users (like jhalpert and dschrute, etc). Use your real TSG username if you're doing extensive testing. Talk to the OCMS product manager to create new users. If everyone logs in as 'gsteimer', issues can arise!

Talk to the OCMS Product Manager if you need passwords for the users below.

Demo Type	Group	Users
OCMS Admin	OCMS Administrators	ballen, gsteimer, eryan, jhof, tparzgnat
Active Wizard / Compliance Solution	Wizard Administrators	ballen, gsteimer, eryan, tparzgnat, qdadmin1, qdadmin2
Wizard Contributors & Doc Editors	ballen, dschrute, eryan, gsteimer, jhalpert, jhof, tparzgnat, qdadmin1, qdadmin2, qdauthor1, qdauthor2
No Group (Consumers)	Any non wizard contributor or doc editor, including: jconsumer, qdconsumer1, qdconsumer2
Insurance	OCMS Insurance (can create content)	ballen, eadjuster, gsteimer, jsupervisor, jhof
No Group (Consumers)	any non OCMS Insurance user or wizard administrator, including: eryan, jconsumer, tparzgnat, etc.

Demo Type	Group	Users
OCMS Admin	OCMS Administrators	gsteimer, ballen, jhof, tparzgnat
Active Wizard / Compliance Solution	Wizard Administrators	gsteimer, ballen, tparzgnat, qdadmin1, qdadmin2
Wizard Contributors & Doc Editors	abeecher, ballen, cobrien, dgrumieaux, dhartman, dschrute, gsteimer, jhalpert, mjackson, qdauthor1, qdauthor2
No Group (Consumers)	jconsumer, qdconsumer1, qdconsumer2
Insurance	OCMS Insurance (can create content)	ballen, dhartman, dgiordano, gsteimer, jhof
No Group (Consumers)	any non OCMS Insurance user
Engineering	OCMS Engineering (can create content)	ballen, gsteimer
No Group (Consumers)	any non OCMS Engineering user

AW / Compliance Solution

• Use any form if you're doing a generic demo
• For the Compliance solution, I use the TSG-### documents. Just search for Document Number = 'TSG' and Status = 'Effective' and that should get you off to a good start. Use the Simple CR form.

Insurance Demo

• Search for policies based on policy ID or Policy Year
• Good generic folders to use
  • Claim 8675309 (Dave's auto claim)
  • Claim with Claimant Name = Ron Swanson
  • The 121212 policy and it's associated claims is good for client demos

When doing demos involving permanent redactions, delete the documents after you're finished and replace them with the unredacted content for the next demo.

Engineering Solution

• Check to see what template folders exist by searching template folders for '*'
• If you want to create a template folder, make sure it doesn't already exist. The code will fail if it does.
• Typically, this demo involves creating a new folder to show how the project starts. Some notes:
  • Use the header action and choose engineering, project folder
  • Make sure the project type has an associated templates folder
  • Set the client to whatever you want
  • Set the project number to something unique.
  • The resulting folder will be named with the above three attributes. If your combo isn't unique the create folder process will fail.

The alfresco project has the ability to mock out a rolling migration from an external system. To demonstrate this feature, the user will fill out a static html page that will find or create the specified claim in the repository, and migrate a handful of medical claim documents, tagging them appropriately upon ingestion. Follow these steps to recreate the demo:

1. Open the file at {OCMS_trunk}\demo-setup\alfresco\claims-form\insurance-claims-form.html
   • Optionally change the logo displayed on the form
   • Fill out the form with the properties that will be displayed on the claim folder (and propagated to the migrated claim documents)
2. Upon form submission, you will be redirected to the /ocms/claim route. This will find or create a claim folder with the specified information, and kick off the rolling migration.
3. The rolling migration will move documents in the directory specified by the OC property insurance.documents.rootFolder. Documents in this folder will be processed alphabetically and tagged according to the values defined by the OC property insurance.documents.tags.
4. Once the folder creation and migration resolve, you will be taken to the new folder's properties and the documents will be visible via VAD.