Make sure CAM/DAOP Tools has a check next to
it, and press Finish.
Expand the CAM/DAOP Tools tree, and check the release named
Architecture Repository. See
Click Next >, and Eclipse will ask you if you agree to the licensing terms of
Application Architecture Repository.
If you agree, select I accept the terms in the license agreement, and press
Eclipse will show you a list of features it is going to install. See
2. Press Finish to start
After all the features have been downloaded, Eclipse will prompt if you want to install each feature.
The quickest way to install everything is to press the
Install All button.
At the end of the installation, you will be prompted to restart Eclipse. Click
Figure 1. Update site.
Figure 2. List of features to install.
2. LDAP Server
Application Architecture Repository can use the file system or a LDAP Server to store the application
architectures and load components and aspects, but the serialized architectures
can only be saved in a LDAP server. This section describes how a LDAP Netscape Directory Server
version 4.1 must be configured. You can find the current version of
LDAP server in the page http://home.netscape.com/eng/server/directory/,
or download the version 4.1 for Windows and Solaris
The documentation about LDAP server can be found
If you decide to save the architectures in
local file system, your election folder will be used as root folders. Don't use
the same folder for Application Architecture Repository and Component &
After the beginning of
LDAP server, we will have to form it so that it can handle the necessary structures of data for our
This can be obtained of two forms. Manually creating the necessary
entrys or by means of a file LDIF.
The required basic structure is
simple. Our directory of application architectures estimates that the directory of user
entrys denominates “people” (the value by defect) and that is located under the root
entry of LDAP server. Three directory entrys of type “organizationalUnit”
must be added in any entry of LDAP server, though it is recommended to add them to the
These entrys can be named with any name, but don't forget names and
location of directories to give it to Application Architecture Repository. The
first of these entrys will contain all the structure of directories that our
Application Architecture Repository needs to store the architectures, the second
will store the component and aspect entries to import (see
and Aspect Repository), and the third entry will contain the serialized
Figure 3: Basic structure of LDAP server
This process of entry creation can be automated, importing to LDAP directory a file LDIF with the structure.
Besides to create the basic structure of the directory, all the permissions of access
must be given to the users of LDAP directory for this entrys. For it we will use the attribute “aci” (Access Control List) of the
entry. We must add to this entry the
multivaluated attribute aci indicated next:
This allows the authenticated users to add, modify and erase
entrys within the entries. Also must be granted leave of writing and reading by means of
“aci” on the
entry “people” of the directory. The value to add is the following one:
entry allows any user who are authenticated to recover information on his entry and those of other users of the system, and to the users of administrator
type to modify the contents of the entrys of other users.
The following step, is to add to the scheme of
LDAP server the objects and attributes that the repositories define. For it, the first step is to stop
LDAP server (not the administrative server) by means of the commandos available in its graphical console.
Once stopped the
server, we will copy the files “slapd.user_oc.conf” and
“slapd.user_at.conf” in the directory “config” of
LDAP server. If, we suppose that our LDAP server is called sun26 and the root directory of
its installation is “/usr/netscape/server4/,” the directory where we must copy the files, would be in “/usr/netscape/server4/slapd-sun26/config”. If
LDAP server was created and is used for other things, we must copy the content of these
files within the existing ones (they are text files) and have well-taken care of
the duplication of names of objects or attributes.
Finalized the copy, we will come to initiate
LDAP server from its graphical console and will have available the objects and
attributes for creation. From this point, we will be able to begin to use the