System Installation and Configuration
All infrastructure setup and installation of Jadu products (Central and Connect) are carried out by Jadu DevOps engineers.
Both Jadu Central and Connect are hosted as cloud solutions at Amazon Web Services (AWS).
Jadu DevOps will be required to create the servers for Central. The Jadu Connect team will be responsible for setting up the Connect accounts.
Typically, a UAT and LIVE environment will be set up for both Central and Connect.
UAT is a critical system used to patch and test releases. It is also used for building and testing new forms and workflows. Both forms and workflow are exported from UAT and imported to LIVE before retesting.
A development environment can also be purchased should you want to carry out your own in-house custom developments.
Prerequisites
- Your internal IPs to whitelist on the server during the project (this ensure the server can not be publicly accessed while development is taking place)
- Confirm DNS records for:
- Central environment - this could be replacing an existing site domain or a brand new domain.
- Connect accounts - generally we follow the convention as https://myaccount.yourdomain.com/uk/gov etc. The UAT url would generally be running under a Jadu domain as https://customername.q.jadu.net/q/login
- Confirm who your initial user will be so that they can be set up and sent an invitation to access the Connect Control Center
- Confirmation of any payment integration required. Jadu has a number of payment service providers that it integrates with. The relevant payment adapter will need deploying to the server. Once deployed, this will need configuring
Note for Partners: These items are covered in the PSM slides.
DNS Records
Once the infrastructure has been created, Jadu DevOps engineers will provide your network team / project manager with the DNS records. These will need to be added by your network administrator / those responsible for updating DNS records. They will typically comprise of;
- A Records - to point the domain to the newly created server and
- SSL Verification Records - to allow Jadu to generate and apply and SSL certificate to the sites.
Visit the Control Center and creating users
Once installation is completed, you can navigate to the Jadu Central Control Center by visiting http://yourdomain.com/jadu in your browser.
The Jadu Control Center is entirely browser based and can be accessed from any internet connection (depending on the IP restrictions in place / individual access privileges). To login you can enter the username / password provided by either the Jadu team or your reseller.
Once you have access, you can browse around and begin setting up your platform. We will discuss creating content later in this guide, beginning with creating users and administrators and building your first category list.
Similarly the Jadu Connect Control Center can be found by accessing the url the Connect account was created on( i.e. https://myaccount.yourdomain.com/uk/gov etc.)
You will be able to start creating new users and sending invites once you have access. You may also find it a good idea to link your Central users to your Connect users to facilitate single sign on.
Visit the Jadu integrations hub
Once you have logged into the control you can access both the Jadu Central and Jadu Connect Integrations hub (where all the magic happens!).
In the integrations hub you will need to set the required integration configurations to enable Confirm. A number of different configurations need to be added. These include:
The template deployment package will contain your templates, a new Confirm integration page (within the integration hub) and also the Confirm Map widget. The Confirm Map widget will need configuring and adding to your homepage(s).
Please also ensure at this stage your integrations for ESRI and selected Address solution are configured in the Control Center.
Within the Connect integrations hub you will also need to setup and configure:
- Address lookup service e.g. Singlepoint
- Brightly Confirm
- Email Service
You may also choose to configure additional integrations such as GOV.UK Notify and/or Click to Call.
Once all the required integrations are configured, you can start building your services as explained in the Training and Content Population section of this guide.
Email and Meta Configuration
Community Central sends out system emails e.g. password reset. For these emails to be sent we need to set a default email address. The default email fields can be updated by accessing the Jadu constants page at /jadu/install/set_constants.php.
The following fields will require updating:
- CC_FORGOT_PASSWORD_FROM_EMAIL_ADDRESS
- DEFAULT_EMAIL_ADDRESS
- DEFAULT_BULK_MAIL_ADDRESS
- GENERIC_FORMS_EMAIL_ADDRESS
The system also sets default metadata which can be updated at /jadu/install/set_constants.php.
The following fields will require updating:
- METADATA_ACCESSIBILITY
- METADATA_COVERAGE
- METADATA_ENABLE_EGMS
- METADATA_GENERIC_DESCRIPTION
- METADATA_GENERIC_KEYWORDS
- METADATA_GENERIC_NAME
- METADATA_PUBLISHER
- METADATA_PUBLISHER_EMAIL
- METADATA_RIGHTS
- METADATA_STATUS
Please note, the constant area of the Control Center is a sensitive area and values should not be updated without knowing the impacts.
You can use the ‘find’ command on your browser to search for the variable you wish to change.
Search Implementation
A search solution will require configuring especially if searching is a feature of your website templates.
Jadu offers out the box integration with a number of search solution providers:
Payment Integration in Jadu Paybridge
If you are building services that need to take a payment, you will need to use the Jadu Paybridge module to configure your payment adapter once it’s deployed (usually done as part of the build stage). Once configured, you can create rules in your forms to take a payment.
More information around Paybridge is covered as one of the online training courses offered.