Allows you to administer users and groups. You can set access rights and view system logs.
Users, groups and access rights are all specific to the domain using which you have logged in. You will not be able to login nor use these access rights on another domain.
The screen displays the list of users and the groups to which they belong.
To enable or disable a user, toggle the Enabled checkbox.
To make or remove an user as an administrator, toggle the Administrator checkbox.
The user name cannot be edited. To edit the other details, click the user name from the Users
screen and follow the process as described in the section called “Adding a User”.
The group name cannot be edited. To edit the users in a group, click the group name from the Groups
screen and follow the process as described in the section called “Adding a Group”.
Allows you to set the access rights for each user. The access rights are:
AdhocDashboardEdit: Allows the user to create, edit and delete dashboards.
AdhocDashboardView: Allows the user to only view dashboards. The user cannot create, edit and delete dashboards.
AdhocReportEdit: Allows the user to create, edit and delete reports.
AdhocReportView: Allows the user to only view reports. The user cannot create, edit and delete reports.
SignIn: Allows the user to sign in to the Ambience Web Interface.
SSOAuthentication: Allows the user to sign in to the Ambience Web Interface using Single Sign On.
The Select All
and Deselect All
options toggle the selection of the access right for all users.
For enhanced security:
anon
user.anon
user.You can view logs of everything that takes place on the system. All user logs are displayed for you to view as an administrator, and take the appropriate actions.
This page lists the JDBC driver configuration for databases that have been configured on the system.
To enable or disable a driver configuration, toggle the Enabled checkbox.
To delete a driver configuration, click Delete.
These driver configurations are displayed as driver suggestions in various other screens where JDBC drivers are used. For example, the Connection Pool wizard displays these driver suggestions as shown in Figure 2.41, “JDBC Driver Suggestions”:
Download the appropriate driver files from the respective database vendors.
Place them in the /lib
directory and restart the server to have them loaded.
Calendars allow you to define the period when your scheduled jobs should NOT run. You define the schedule when you want to run your jobs, using the Scheduler as described in the section called “Schedule”. If you want to define periods when you do not want your jobs to run (for example on weekends or public holidays), you define them in a calendar and then use the calendar in the scheduler.
For example, assume you want to generate a sales report every day, automatically, but do NOT want to generate the sales report on weekends (as the staff are on holiday). You perform the following steps to achieve this:
The sales report will now be generated every day, except on weekends.
There are four built-in calendars as shown in Figure 2.42, “Built-in Web Calendars”
To add a new calendar, click Add.
The Web Calendar screen appears as shown in Figure 2.43, “Web Calendars”.
To create a calendar:
Select the periods when the job will NOT run. Usually, you want to run your jobs periodically, except on certain days or times - for example, on holidays, weekends or at certain times when backups are running. Hence, it is more convenient to select the periods when your jobs should NOT run.
You can select ANY of the following criteria - days of week, days of month, particular times of the day and specific dates.
For example, if you select Sunday, and the time period as between 10 PM and 11 PM, the job will NOT run every Sunday, AND between 10 PM and 11 PM each day.
Example 1: Your job should NOT run between 10 PM and 11 PM Singapore time, each day, as that is the time when your data is being backed up.
The relevant selection for this calendar is shown in Figure 2.44, “Web Calendars - Example 1”.
Example 2: Your job should NOT run on Saturday and Sunday and 2 Public holidays - for example, 1 Jan 2015 and 25 Dec 2015, as the staff are on holiday.
The relevant selection for this calendar is shown in Figure 2.45, “Web Calendars - Example 2”.
Example 2 shows you how to define your weekends, as well as public holidays, when your job should NOT run, as the staff may be on holiday.
Example 3: Using CRON, your job should NOT run on the 31st of March, each year, as the system may be processing financial year end activities.
The relevant selection for this calendar is shown in Figure 2.46, “Web Calendars - Example 3”.
After you create and save a calendar, you can use it in the scheduler as described in the section called “Schedule”.
The Universe section allows you to map a Universe to a specified universe name and then export the Universe in a format suitable for use by Ad-hoc Dashboard and Ad-Hoc Report.
To add a Universe mapping:
To publish the Universe in a format suitable for use by Ad-Hoc Dashboard and Ad-Hoc Report, enter a name for the template in Publish Ad-hoc Template as
.
Then, click Dashboard or Report respectively.
By default, everyone can access the Universe provided it is saved in a publicly accessible folder, i.e. not in any User folder.
Optionally, to set restrict the users and groups who can access the Universe:
Click the Add icon () next to the user or group to move it
from the Available
section to the Access Granted
section, as shown: