On systems used productively it is required to change the passwords of the
applications listed below. Afterwards these applications need to be
restarted. In the examples below, default
is used as the
instance name. Replace this name by the name of the instance actually
concerned.
Change to the NPS/instance/default/bin
directory and
execute the Content Management Server in an operating system shell using
the command ./CM -single
(UNIX) or CM.bat -single
(Windows).
Now change the password of the root
user by executing the
command
user withLogin root set password newPassword
at the server’s prompt, replacing newPassword
with
the password to be used from now on. Then log-off from the Content
Management Server using exit
.
Please make sure that only authorized persons log-in to the Content
Management Server directly, i. e. using the command line argument
-single
.
For the Content Management Server to be able to send updated content to the Template Engine, a user name and a password need to be set in the Template Engine.
This log-in data can be modified by editing the export.xml
file contained in the NPS/instance/default/config
directory
using a text editor. Change the log-in data contained in the section
<incrementalUpdate> <isActive>false</isActive> <login>root</login> <password>changeme</password> </incrementalUpdate>
and save the modified file.
For the CMS applications to be able to communicate with each other, a
secret
phrase common to all three applications is required.
Please set the value of the following configuration keys to this
secret
:
GUI
Version 6.0.x: instanceSecret
in the
NPS/instance/default/webapps/GUI/WEB-INF/config/basicConfig.properties
file.
From version 6.5.0: instanceSecret
in the
NPS/instance/default/webapps/GUI/WEB-INF/basicConfig.properties
file.
secret
in the tokenManager
bean included in the
NPS/instance/default/webapps/GUI/WEB-INF/pm.xml
file.
Portal Manager
secret
in the tokenManager
bean included in the
NPS/instance/default/webapps/PM/WEB-INF/pm.xml
file.
Content Management Server
instanceSecret
in the NPS/instance/default/config/server.xml
file.
Afterwards, the web applications must be deployed. Use the script command
rc.npsd deploy
(up to version 6.0.x Unix only) or
deployWebapps.bat
(Windows, only up to version 6.0.x) for this.
These commands can be found in the bin
directory of the default
instance.
Trifork Application Server initially is protected by a default user
name and password. This log-in data can be used to log-in to the
administration console which can be accessed via the URL
http://localhost:8090/console
. The user name is
administrator
and the password is trifork
.
The password can be changed in the Security -> Realms -> default section of the administration console. Alternatively, it can be changed via an operating system shell using the command:
trifork realm updateuser administrator "myPassword"
myPassword
represents the new password. It is also required
to specify the new password in the file rc.npsd.conf
(up to version 6.0.x only Unix) or setInstanceEnv.bat
(Windows, only up to version 6.0.x), which is located in the
directory NPS/instance/default/bin
, by modifying the value of
the respective variables in this file.