RemoteRepositorySchema is the schema representation of remote content system. It
defines the set of properties (not values) in the form of attributes definitions for
the system admin or workspace admins to create configurable s
in order to create . The following properties are defined whenever
a remote repository schema is created:
Host - location at which the remote content server is residing
Port - port to connect to the Host
Parent - the location at which the remote share has to be hosted (current implementation only
supports workspace)
RepositoryType - type of the repository
Protocol - type of the protocol to talk to remote system
All the above properties are to be mandatory attributes and the corresponding arribute templates
in the RemoteRepository will be defined implicity. No need for the admins to define these
attributes explicitly. Again RepositoryType and Protocol are defined in the schema are neither
modified at the RemoteRepository or at the RemoteShare.
In essence for each external repository type and protocol there will be corresponding schema.
Following are the attributes that the admins can define and will be interpreted
by the beehive system :
RemoteUser - user in the remote system for the beehive system to connect in behalf.
RemoteUserPassword - password of the remote user.
If these two properties are not defined by the admin then the beehive user will prompted
whenever s/he browses through the remote repositories for credentials(for the first time).
Rest of the properties which are specific to the remote repositories or
protocol can be defined in the form of attribute definitions. Those properties names MUST not
match with the above standard properties.
Below are examples in JSON and XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.