The server provides services such as the user interface used to configure application
deployments, the security service, and the artifact repository, among others. Installing the
server involves specifying configuration information for the server, such as the ports that
the server uses.
Before you begin
The following table addresses some build-specific
information that you must know while installing a specific version.
Affected Build |
Consideration |
8.0.0 |
- FIPS non-compliance
- If you are upgrading a server that is using Java 8 with FIPS
enabled, the installation is aborted and displays an error
stating that FIPS mode is currently not supported. Deploy does not support Java 8. Running a server with Java 11 in
FIPS mode is not supported in this release.
|
7.3.2 |
- Mandatory requirement for starting the Deploy server with SQL server database
- It is mandatory that before starting the server, the
READ_COMMITTED_SNAPSHOT SQL server parameter must be enabled. If
not enabled, the server startup aborts with a
message:
com.urbancode.ds.UDeployServer - Micrsoft SQL Server setting READ_COMMITTED_SNAPSHOT is not ON
2023-05-17 13:23:48,333 IST INFO main
com.urbancode.ds.UDeployServer - Before the application can start, READ_COMMITTED_SNAPSHOT must set to ON by
your database administrator. To do this, they must execute this statement while there are no other clients connected to the named database:
alter database [test] set read_committed_snapshot on
The statement will not complete until all other clients disconnect. This is a restriction imposed by Microsoft SQL Server.
- Removal of old plug-in versions stored by the agent
- When you upgrade and start an agent, the agent communicates with
the server and looks for any old downloaded plug-ins. If any
such plug-ins are found, they are removed from the system, and
new version of those plug-ins are downloaded
automatically.
With this change, security vulnerabilities
may be removed from agents which had old insecure versions
of plug-ins on them.
|
7.3.0 |
- Changes in Keystore format
- V7.3.0 includes some changes in the encryption keystore. It is
advised that you create a backup before upgrading to this
version.
The 3DES keys are not supported because of a Java
limitation. Eliminate any 3DES keys using the key rotation
tool. Note that when upgrading to V7.3.0, the upgrade will
abort if such keys are detected. Also, a key alias must be
set.
- Upgrade with Java 11
- If the current server is using Java 8, the upgrade prompts you
to specify Java 11. Note that you must change the JAVA_HOME
enviroment variable first to complete the upgrade.
|
7.2.3 |
- About 7.2.3.0.ifix01 and 7.2.3.1.ifix01
- As part of Deploy v7.2.3 and v7.2.3.1, the Windows service names for agents
are no longer customisable by end-users. The names are
auto-generated by the Deploy server. We recently discovered that the naming convention
of auto-generated Windows service names does not follow the
IBM naming convention standards. We are providing
7.2.3.0.ifix01 and 7.2.3.1.ifix01 that generates the Windows
service names correctly.
Note that the ifixes does not
provide the ability for users to define the service
name. The name is auto-generated with the correct
format. We strongly discourage customers from
upgrading Windows agents with the now pulled back 7.2.3
and 7.2.3.1 versions. Please use the ifix releases only.
If you have already upgraded your Windows agents with
original releases, reach out to support to find how to
remediate it.
Note the following changes when you upgrade to this version:
- Removed
$productName/java.home from agent
- The
$productName/java.home property is removed
from agent properties file. Upgraded agents are compact agents
that does not require Java home property.
- Updated the
sshInstallAgent/installNewAgent CLI endpoint as POST
request
- For security purposes, the sshInstallAgent/installNewAgent CLI
endpoint is updated to post the install agent informaton without
the sshPassword.
|
7.1.2.10 |
- Server/agent version mismatch
- You will notice the inconsistency between the versions of Deploy server and agent installation files. Know that the version
mismatch, server v7.1.2.10 and agent v7.1.2.9, will not cause
any installation or upgrade problems.
|
7.1.2.7 |
- Updated the sshInstallAgent/installNewAgent CLI endpoint as POST
request
- For security purposes, the sshInstallAgent/installNewAgent CLI
endpoint is updated to post the install agent informaton without
the sshPassword.
|
7.1.1.2 |
- Running an application process
- The CLI endpoint
/cli/applicationProcessRequest/request has
been corrected from PUT to a more appropriate method POST. The
PUT method is obsolete, but it is still allowed in the newer Deploy versions. Note that the HTTP POST should be utilized starting
version 7.1.1.2 and the scripts should be updated from PUT to
POST to avoid running into issues.An example documentation can
be found here:
- Run an application process in v7.1.1.1 and
before
(obsolete):
PUT https: // {hostname} : {port} /cli/applicationProcessRequest/request
-
Run an application process in v7.1.1.2 and
later:
POST https: // {hostname} : {port} /cli/applicationProcessRequest/request
|
7.1.1 |
- Migration of JMS agents
- JMS agents when connected to the server in your environment, a
warning message is displayed.
- You are prompted to begin the migration of JMS agents to a web
format. See Migrating Agents to
Web for more information.
- Hibernate v5.4.20
- A new version of Hibernate; V5.4.20. Hibernate V5.4.20 may
require newer versions of the JDBC driver in order to function
properly. Ensure that you have a driver version that works with
your database and is compatible with Hibernate v5.4.20. This
upgrade also removes the hibernate.dialect property from
the installed.properties as the new Hibernate version itself
determines the dialect.
|
7.1.0 |
Logging information is now written to deployserver.out
instead of the stdout file. |
About this task
You can install the server in interactive mode or in silent
mode.