Go-Live
Your first eform is essential for kicking off the implementation into its critical first stage of delivery - launch.
We encourage you to pick a form that provides the business value - but is not so complex (with sophisticated integrations for example) that it sets up risk of failure, because at the moment the platform is new. Chose the first eform wisely!
In almost all implementations, a certified services partner or the Jadu Customer Success team (depending on who you have engaged to deliver your implementation) will help you deliver your first form. As well as helping your project be successful and deliver value early - we also walk you through the process of forms design and how the platform handles things like notifications and any potential workflows you might be creating in an ECM system for example.
Go Live Process
We strongly recommend that a backup routine be put in place before the site is made live (and even before content is started to published to the site).
We also recommend that you establish a regular Release update (at least every 3 months) - where you are patching your Content Portal platform for new updates and releases.
The most important data to back up is the database, the image directory, the downloads directory and the logs directory. There may be further data to back up if you have any additional Jadu Modules.
The following checklists may be helpful to your project team during the Go Live process:
To make your new site live you need to change the DNS for your domain to point to the new server. There are two common ways that this is done, depending on your infrastructure. Your IT department should be able to advise which is applicable.
Internally: This usually applies when your new site is hosted on a server on the same network as your old site. In this instance your IT department should be able to make the necessary change to make the site live and the change will happen instantaneously.
Externally: This usually applies when the new site is located on a server in a different location than the old server. In this instance you will need to make a request to somebody who can make amendments to the name server for the domain. They will need to make a change in the name server so that the address of the site points to the new server. This can take up to 48 hours to filter through to the whole Internet. To help reduce this time we recommend that you request the time to live (TTL) for your domain is reduced to 5 minutes.
You will need to redirect your site to an offline page and then, at an agreed time of go live, you will need to request that the A record (and only the A record) be changed to the new server IP address.
Setup already on live domain: In many cases where the customer is set up under a brand new domain as part of the installation, there should be no further domain changes required as the records would already be in place. We recommend the time to live (TTL) for your domain is reduced to 5 minutes a week before the launch.
Content Portal is a continuously released software. You will need to build capability in your team to implement patches to remain supported. We recommend patching quarterly as a minimum. Also, please note the requirement to "Warm Cache" after every patch.