In Content Server 16.2.6 the Cluster Manager is gone.
Whenever you try to open the Admin pages, you see this:
Install the System Center Software
First, you have to download and install the System Center Software. Clicking on the Link “Download Software” directly connects you the the Knowledge Center. After logging into this Knowledge Center, you’ll arrive at the Landing Page for the System Center.
The System Center(s) are avaliable for Windows and for Linux servers. Select the proper version for your system and download it.
You’ll find the System Center directly in the list of programs, like here in Windows Server 2012
Double Click to start. Next, you’ll see the System Center Home Page
Like in the cluster management, you’ll need to download an agent per Content Server system and install that agent at that particular system – Click on Download and Install Agent.
(dont forget your local system!).
Next, you have to register the systems, onto which you just unstalled the agents. Go back to the “Home” of the System Center and click on “Register Systems”
Under “Managed Systems”, you see all systems already registered, under “Pendig systems” there are all systems with agents recognized by the System Center.
Click on the entry in the column “Actions” on the system pending, and you can register the agent. A Click will give you the detail view (here the system is already registered)
So you are nearly done!
Click on “Discover Products” for this particular system at the bottom of the page and the system is checked for all supported products and those installed are listed.
How to check for patches and install them?
Easy. Until now, you did the setup.
This has to be done only once.
Go back to the “Home” and click on “Check for Updates”
This will lead you to the “Products” tab with Updates for the registered product.
Either expand the “Avaliable Patches” entry and select the patches you want to install or select all by checking the checkbox at “Avaliable Patches”. Then click on “Download Selected” and see the system working.
First you need to login into Knowledge Center
Press Close and you see the download window. As the download is done async, you see green marks (downloaded and installed) and also the moving circles (waiting for download or still in progress)
It also provides a list of supported products by clicking “Catalog” from the “Home” page of the system Center
The latest releases are listed directly in the calalog overview.
So the System center is much better then the Cluster Management doing updates.
From time to time, you need a test email server on a VM or on a test environment to configure the Content Server elink capabilities. Or maybe a Exchange is too powerful for you?
Then Mercury as an email server and Pegasus as email client may be a good choice for you. You can download this at http://www.pmail.com/ .
But having a mail server up and running is only half of the price. You still have to configure elink and the mail server.
elink is a Content Server mechanism, which allows you to store documents via email or post replies to to discussions or send documents also via email.
Setting up elink is simple.
You have to imagine, that elink has to have a mailbox on the mail server, which is used to retrieve messages to the content server. This means, a mail to this mailbox is processed by the content server. The mail server must be configured that all mails from a domain will be stored in this mailbox.
for example the message
<123BeDessfdj>@elink.net must be stored in the elink mailbox to be processed by the content server.
First, lets configure the Mercury Server. First, we need to setup a Content Server used. Lets call it elink.
Second, we need to setup the Domain for this mailbox. If we enter the DM=user with the username just defined and an Internet Name (here elink.net) for our mails to the content server, we define that all mails from the Domain elink.net will be stored in the elink mailbox.
Next, we need to configure elink. This must be done on the Content Server admin pages.
Virtual Hostname is the name of the Domain, from which we want to store all messages in the elink mailbox.
Username/Password is the name of out mailbox user (elink) and its password. You can test the connection by pressing the “Test Connection” button.
If everything runs, you’ll see mails like these in the Pegasus mail client.
If you are thinking on using Content Server Webservices (CWS´) you may wonder how to activate this on a standard Content Server Installation. Normally, right out of the box, CWS is not active or installed, although you got the license to use it in your basic license.
As Administrator, you have to do a couple of things to activate CWS.
Decide which architecture you will use.
CWS can be used inside of the Microsoft Internet Information Server or inside a Java Application Server like Tomcat. Both ways to activate will be described here.
Locate the CWS Software
Look in your install directory of the content server. There, you will find a directory named “webservices”.
Here, there are three entries:
dotnet contains all CWS service definitions for use inside the Microsoft IIS
java contains all webapps for use inside the Tomcat application server
java6 contains the same thing as in 2. but for use with java 6.
Installing CWS inside the Microsoft Internet Information Server IIS
First, let’s examine how to install CWS inside IIS. Switch to the dotnet subdirectory, then to cws (do not use les-services, this is an old version supporting legacy clients)
Locate the .svc files you wish to install and use in CWS.
Open the IIS Manager. Create a new Application at the default web site
Enter the path to the dotnet\cws directory , enter for example CWS as alias.
Remark: IIS must be configured to
execute .NET 2.0 apps
allow “Read” and “Script” rights to the new app
execute WCF (can be ensured for example by “%SystemRoot%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe -i” (check, if something changed, if you are using newer versions)
allow “Read” and “Execute” rights for the ID of the Application pool on $OTHOME/webservices/dotnet
And (don’t forget), ensure that your webservides will use the same port as your content server uses. If you use a nonstandard port (not 2099) you need to change the port in the file $OTHOME\webservices\dotnet\cws\web.conf
If you use the standard port, there is nothing for you to do.
Installing CWS in Tomcat
Alternatively, you can use Tomcat as a base for CWS.
In this case, go to the java6 base directory in the webservices dir.
In this dir, you’ll find the war (web application archive) files, which you need to deploy.
Deploy the cws.war file either to the TOMCAT\webapps directory or use the Tomcat service manager to deploy this file.
Don’t forget, if you changed your port number of your content server from 2099 to something else, change also the value in the web.xml of the unpacked cws web app.
If you don’t use the same port numbers, the whole system will listen to different ports and will do nothing.
Test your installation
Your installation is correct, if a browser, pointing to
http://127.0.0.1:8080/cws/services/DocumentManagement (Tomcat) or