1. Short dashboard administration panel introduction.
After the installation finished successfully you can start to work with Cyklotron2 system.
Administrator account comes in default initial data. Login is root and password is 12345.
Remember to change default administrator password shortly after you login to application for the first time.
Start tomcat and login to dashboard view as an administrator, you should see screen as follows:
On the picture below you can see almost fully expanded dashboard navigation tree.
Adminstrator can see following nodes on the first level of dashboard tree:
- Access control - the security mangement node
- My sites - display sites that you belong to
- Organizations - groups all organizations registered in system, displays organizations you belong to.
- Pending organizations - lists all organization proposals waiting for moderation.
- Preferences
- Users
- Virtual servers
Other registered user (if created) can see only "MySites" and "Organizations".
System in its default installation delivers 1 central organization and 1 organization template ready to use.
Changing profile
On the right top in breadcrumb navigation bar you can see the information about current logged user i.e logged in as Administrator.
You can change your personal preferences by clicking current user login link. Choose prefered locale and click Update button to store data.
Setting system preferences
Change current selected node to Preferences. On the right following available operations appear:
- Change Password - Here you can change your password
- My Profile - Her you can change your personal preferences (only prefered locale ATM)
- Application Map - Here you can change whether application can be installed in Organization or Site. Also you can force to install application by selecting required option.
- User accounts - Here you can choose policy of user's account creation - allow to self creation by everybody or limit it to administrator.
User account creation policy options:
- Open to visitors - that means new coming user can create an account on his own.
- By system administrator - account creating is reserved only for administrator.
Managing users
Change current selected node to Users. This section groups user management tools.
- Create an user's account - Here you can add new user to system, provide user login, password, first name, last name and e-mail address. Only login and password are required.
- Manage users - Here you can list all the users accounts in the system and edit user's personal data.
1. Managing organizations
Getting closer to Host organization
If you change current selected node to Organizations you can see that you're member of one Organization - titled Host organization.
There is nothing special in this organization. It is simple predefined organization that comes within initial data to help you setup your system. You have the possibility to delete this predefined organization and build your organization from the scratch.
The only application installed in Host organization is WWW sites in addition to Access control node which is required for all High level resource's.
Expanding Host organization node and it's children show us one predefined Site - titled Host central site. This site appears also in My sites node on the first level of dashbaord navigation tree.
Explore Host central site to see what preinstalled applications it offers you to use:
- Access control - as mentioned above.
- Appearance - to control the appearance of your site.
- Files repository - simple files container.
- Home page - the main page of your site with tools to manage site structure.
It is the minimal set of applications that is required for Site.
You can add more applications to your High level resource from additional set of optional applications i.e. Calendar, Polls, Forum. Select High level resource and choose Add/remove applications link from available operation list.
Explore Home page node see the default structure of Host central site. As you can see there is one main page are 5 subpages.
Select Home page and click Preview the page link to see the public view of your site.
Setting security to turn on the site for public.
Your site is not visible for other users. You can change it by assigning some privileges to selected users, user's groups or for all registered and/or unregistered users. Before you do it decide which part of your resoures you want to publish and what do you want to hide from public view. This short tutorial shows you how to selectively publish your pages.
The assumptions are:
- anonymous can see only Main page and Create new account pages
- registered user can see all pages except Create new account page - which means that registered user does not need to create new account.
The solution:
- select Main page node, click Manage priviledges, then create Pages local visitor, repeat it for all sub pages.
- expand Access control -> Privileges node. For each page select Pages local visitor privilege and Assign priviledge to appropriate user's group:
- Main page local visitor assign to both registered and unregistered users.
- Create new account local visitor priviledge assign only to unregistered users.
- The rest of local visitor priviledges assing only to registered users.
Go to you main page, click Preview the page and logout - you should see only 2 pages.
Add virtual site to your service.
If you look at Preview the page link url you can see that it contains the default host name i.e. "localhost" and displayed page is identified by docId parameter. This is the single server name configuration.
Also you can identify page in system by relative path which looks much better than some non-informative identifier.
To do this you have to distinguish your pages from other pages by replacing default host name with
another virtual host name:
- go to Virtual servers node
- fill blank form with new domain server name, from site list choose your site i.e. Host organization/Host central site and click add button.
- go back to Home Page node and click Preview the page link
Now you can see url looks like: http://<virtual_name>/<app-context>/doc or http://<virtual_name>/<app-context>/doc/system-node-user-profile if you go deeper into service.
Advanced Apache users we strongly encurage to read more about Using mod_rewrite to polish your urls.