- 57 -
69. At this point you have to restart the
managed server in the WebCenter instance.
When WebCenter Spaces restarts, the auto-configure scripts will connect the Content Server and
check if the root folder and the required security settings already exist, as defined by the root folder
and application name parameters of the Content Repository connection. If both exist, WebCenter
Spaces assumes that the content server is properly configured. If none of them exists, the auto-
configure script will create all the necessary artifacts in the Content Server. If only the folder or the
security group exists, an error is reported in the log file and Content Server will not be accessible
from WebCenter Spaces. Consequently, if you want to change the details in the content repository
connection, make sure to change both the root folder and the application name.
70. After WebCenter Spaces is started, you can test the Content Server. For example, log in to Spaces,
create a new space, select the Documents page of the space, and upload documents.
Detailed instructions to test whether WebCenter Spaces and Content Server work together correctly
is beyond the scope of this document. However we suggest a few quick tests to see if the auto-
configuration wizard created the necessary settings in the Content Server.
Access the Content Server Web interface, typically at
and log in as administrator user,
. If you were already logged in to Content
Server, log out and log in again.
Expand the Browse Content node. Note that there are two new folders created. In our example,
This is the root folder for all of the space-related content. The name is the same that you
specified with the Content Server connection. Later, as each new space is created, each space
will have its own subfolder here.
This is the root folder for all documents stored in users’ home spaces. Each user will have a
subfolder corresponding to the username.