SPSS Collaboration and Deployment Services 8.4 Release Notes

Content

• System requirements
• Installing
• Updates, limitations, and known problems

System requirements

For the most up-to-date system requirements information, use the software product compatibility reports under Support Resources on the IBM Technical Support site.

Installing IBM SPSS Collaboration and Deployment Services 8.4

For information on downloading the product, see the Download Document.

For information on installation, see the installation documents.

Information about IBM SPSS Collaboration and Deployment Services can also be accessed in the the IBM Documentation.

Updates, limitations, and known problems

Documentation updates, limitations, and known problems are documented as individual entries in an online knowledge base. As problems are discovered and resolved, IBM Software Support updates the knowledge base. By searching the knowledge base, you can find workarounds or solutions to problems. The following link starts a customized query of the knowledge base:

View all known problems for IBM SPSS Collaboration and Deployment Services

At the time of publication, the following issues were known:

• Due to a limitation with Liberty, if the installation path is too long, the Liberty Server might fail to start. We suggest using the default installation path or one of similar or shorter length.
• Analytic Data View functions may have some issues on Liberty Server when using JRE 11. As a workaround, you can downgrade it IBM JRE 11. To do this, you should first migrate the keystore file from IBM Semeru JRE 11 to IBM JRE 1, then replace the contents of the "jre" folder in the Collaboration and Deployment Services installation directory.
• You may encounter a random issue that causes the log for the Repository Server or Remote Scoring Server to be missing content when daily rolling occurs. The log generated on the previous day might be overwritten by the log for the current day. To work around this issue, add an integer counter "%i" to filePattern in log4j2.xml. For example, a typical "RollingFile" section for a log4j2.xml configuration looks like:
  <RollingFile name=“RollingFile” fileName=“./logs/cds.log” filePattern=“./logs/cds-%d{yyyy-MM-dd}-%i.log” append=“true” >
      <PatternLayout>
          <Pattern charset=“UTF-8”>
              %d{MMM dd HH:mm:ss} %-5p [%c] - %m%n
          </Pattern>
      </PatternLayout>
      <Policies>
          <TimeBasedTriggeringPolicy interval=“1" />
      </Policies>
  </RollingFile>
  For details about log4j 2.x configurations, see the log4j documentation. The location of the log4j2.xml file is set by the log4j.configurationFile property. For example, for the Repository Server or Remote Scoring Server which is deployed to WebSphere Traditional, this value is available in the Administration Console under Application servers > [server-name] > Process definition > Java Virtual Machine > Custom properties, where [server-name] is the WebSphere server where SPSS Collaboration and Deployment Services is installed. For a Remote Scoring Server deployed to WebSphere Liberty, this value is set in <remote scoring server installation directory>\wlp\usr\servers\cdsScoringServer\jvm.options.
• The single sign-on functionality doesn't work on JBoss EAP 7.3 with IBM JRE. This is an IBM JRE issue and we suggest switching to Oracle JRE if you encounter this problem.