You can configure a new MCS project on your machine to enable you to collaborate with other users on editing policies, layouts and themes. In a project configured this way, MCS uses a JDBC repository to refresh XML project files on local machines, and allows team members to hold locks on policy and variants attributes.
You can configure a new MCS project on your machine to enable you to collaborate with other users on editing policies, layouts and themes. In a project configured this way, MCS uses a JDBC repository to refresh XML project files on local machines, and allows team members to hold locks on policy and variants attributes.
You specify a connection to a database repository, and provide a display name that can be used to view your own locks, and so that other users can contact you if they need you to unlock a resource. MCS downloads the project policies, and updates the policies at regular intervals.
You should contact your administrator for information on database access, and for the conventions on display names.
The display name that identifies users must be unique in order to sensibly identify locks on resources. MCS associates this name with a specific project on a single user's machine. It is not bound to any other system of user naming.
In the Project Settings page of the New Project wizard, check the Enable collaborative working option to enable the remaining controls. The Database project name contains the project name
Enter the required name of the policy repository Database
Fill in the Host, Port, Username, and Password for the database, based on the information you received from the administrator
Enter an identifier in My display name. Usually this will be an e-mail or instant messenger address that uniquely identifies you.
Click Finish. MCS displays a dialog while it copies the project files to the XML repository on your machine.
The new project icon appears in the Navigator pane. Any existing project resources will be displayed in folders under it.
Once you have created a collaborative project there is no way to change either the database, or the policy source directory. You can change to another device repository using the project Properties dialog, though it is advisable that everyone collaborating on a project use the same device policies. Other controls will be read only.
If you no longer want the policy files to be part of a collaborative project, you must create a new project, and either copy the XML policy folders to it, or export them from the database.
You should not change the names of any project folders. If you do so it is possible that the policy files will not be recognized as part of the project.