Forums/Documentation
FAQ - Documentation
Kris Stephen
posted this on August 09, 2010 01:51 pm
- In general if you are having trouble finding specific documentation that is not included in the Contour User Guide, please request or express your concerns by posting a comment and/or submitting a support ticket.
Comments
Hi Kris,
I used the database schema quite a bit... do you have a link for that available?
Thanks,
Mike
Mike: The database schema is located here: http://www.jamasoftware.com/schema/
Hello,
I'm searching for a hint, WHEN exactly Contour will send an email, if I select "daily" in my profile after subsribing. I don't think this time is configurable.
Thanks,
Martina
Martina: The cron expression for the Daily Job that creates the notifications is: "0 0 13 ? * SUN-SAT" which means every day at 1 PM (server time) notifications are sent out. This value is located in the jobschedule table of the database.
Thank you for posting the database schema previously.
Something else I have not yet found but would be very useful is details on what is passed to the various notifications (batchNotificationBody.vm, batchUpdateNotificationEmail.vm, etc) so that we can take full advantage of formatting the notifications to our needs. For instance, batchNotificationBody.vm is passed a $notificationList variable, but I could not find any information about the parameters included (other than the .message, .action, .date, .comments, and .url portions already included within the .vm file).
Thanks,
Mike
Mike: Unfortunately we don't have any documentation on email parameters at the moment. I don't believe there are any additional parameters then what are currently presented in the existing templates either.
Please Note: This is an area we are looking to improve and expand upon.
Server Migration Tips:
Migrating servers is very similar to the upgrade process of Contour. There are certainly areas of concern to consider but this post should give you a general idea of what to expect.
1. Backup Existing Data
- Create a backup XML file by logging in as the 'root' user in Contour.
- Create a copy of your database.
- Create a backup of your contour_home directory.
- Backup any customized files located in the contour webapp folder. (server.xml, web.xml, custom report files).
2. Install your new Java JDK, new Tomcat, and/or new Database.
- If you are planning on upgrading and migrating Contour at the same time, it is suggested to do one 1st and then the other. i.e. if you are moving Contour to a new server or want to point to a new database and upgrade Contour to the latest version at the same time, you would upgrade Contour and then migrate or vice versa.
Note: if you're server is changing hostnames, you will need to take some additional steps.
- You will have to update the URL's of existing attachments and images in the database. We will provide a query to perform this action upon request.
- After your migration is complete, change your BASE URL configured in the Organization details of Contour to match your new hostname.
- See the Contour User Guide or Installation/Upgrade Guide for additional information on configuring Java, Tomcat, or your database. You should also consult our general guidelines on performance and/or recommended server setup.
3. Move Contour data over
- Move the contour webapp folder into the new Tomcat installation.
- Move the contour_home directory into the new server.
- Delete {tomcat}\work directory to remove any Tomcat cache.
- Delete contour_home\search directory to remove existing indexing data from Contour.
- Delete {tomcat}\webapps\contour\WEB_INF\init.properties file to remove the location that Contour looks for contour_home.
- Delete contour_home\database.properties file to remove the database connection properties.
4. Start Tomcat Service and Re-Configure Contour
- Select Other Configuration
- Select the Re-configuring Contour option and paste the location of your new contour_home directory in the text box at the bottom of the page.
- Enter the details of your new or original database.
- If you prefer to configure Contour using a backup XML file. Point Contour to a clean database and click next. At the next screen you can select a backup XML file which will upload its information into your database.
- If you want a new database with the default data simply click use default data.
- Because this guide is for migration and we suggest to do a migration separate from an upgrade you should not have to apply any patches or be directed to apply any data updates.
- Index your items and wait for this to complete. Depending on the size of your database, this may take an extended period of time.
- Configuration should now be done. Remember to update your Organization BASE URL if your new server contains a different hostname as well as manually updating existing attachments URL's in the database.
Hi,
I searched across all projects for a certain expression and found it within an attachment (Contour 2.9.7).
How can I find out which item this attachment is added to?
The attachment's lists of the projects doesn't help very much.
I couldn't find anything within the Documentation...
Martina
Hello Martina -
There is not currently an easy way to get the item information from an attachment as you're doing.
If you must find the item associated with the attachment:
1. search for the attachment in the search box.
2. Add the API-ID column to the list view.
3. Run the following query on your database:
"select document.id as API_ID, document.documentKey, document.name as Name
from document_docattach dattach
inner join document
on dattach.documentId = document.id
where docattachId = 223;" <--attachment API-ID