Download
Release Date
25 June 2019
Abstract
This page describes how to download and install IBM SPSS Analytic Server 3.2.1 Fix Pack 1.
Download Description
IBM® SPSS® Analytic Server 3.2.1.1 is a solution for big data analytics that combines IBM SPSS technology with big data systems and allows you to work with familiar IBM SPSS user interfaces to solve problems on a previously unattainable scale.
Complete user documentation is available in the IBM SPSS Analytic Server Knowledge Center.
This is a brief description of Fix Pack 1 for IBM SPSS Analytic Server 3.2.1 ("Software").
BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, OR OTHERWISE USING THE SOFTWARE, YOU AGREE TO THE
TERMS OF THE IBM LICENSE AGREEMENT UNDER WHICH YOU ACQUIRED IBM SPSS ANALYTIC SERVER.
BY AGREEING, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO ACCEPT THESE TERMS. IF YOU
DO NOT AGREE TO THESE TERMS,
- DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE SOFTWARE; AND
- PROMPTLY RETURN THE UNUSED MEDIA AND DOCUMENTATION TO THE PARTY FROM WHOM IT WAS OBTAINED. IF
THE SOFTWARE WAS DOWNLOADED, DESTROY ALL COPIES OF THE SOFTWARE.
TERMS OF THE IBM LICENSE AGREEMENT UNDER WHICH YOU ACQUIRED IBM SPSS ANALYTIC SERVER.
BY AGREEING, YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO ACCEPT THESE TERMS. IF YOU
DO NOT AGREE TO THESE TERMS,
- DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, OR USE THE SOFTWARE; AND
- PROMPTLY RETURN THE UNUSED MEDIA AND DOCUMENTATION TO THE PARTY FROM WHOM IT WAS OBTAINED. IF
THE SOFTWARE WAS DOWNLOADED, DESTROY ALL COPIES OF THE SOFTWARE.
IBM SPSS Analytic Server 3.2.1 Fix Pack 1, to be applied with IBM SPSS Analytic Server 3.2.1.
Prerequisites
The system requirements for the product are available from the IBM Software Product Compatibility Site
Cloudera prerequisites
--------------
--------------
1. IBM SPSS Analytic Server 3.2.1
2. Create the required accounts. If you have done these steps during the installation of AS 3.2.1, please skip them.
a. Create all users you plan to give access to Analytic Server on the LDAP server.
a. Create all users you plan to give access to Analytic Server on the LDAP server.
b. Create an OS user account for each of the users created in the previous step on each and every Analytic Server node and Hadoop node.
c. Create a user home folder on HDFS for the Analytic Server administrator user. The folder permission must be set to 755, the owner must be defined as admin, and the user group must be set as hdfs. See the following example after created the "admin" account:
drwxr-xr-x - admin hdfs 0 2019-04-26 03:02 /user/admin
drwxr-xr-x - qauser1 hdfs 0 2019-05-27 23:47 /user/qauser1
drwxr-xr-x - qauser1 hdfs 0 2019-05-27 23:47 /user/qauser1
d. Create a user home folder on HDFS for the Analytic Server standard user (e.g qauser1). The folder owner is the user itself, and the user group must be set as hdfs.
HDP prerequisites
--------------
1. IBM SPSS Analytic Server 3.2.1
--------------
1. IBM SPSS Analytic Server 3.2.1
2. Create the required accounts. If you have already done these steps during the installation of Analytic Server 3.2.1, please skip them.
a. Create all users you plan to give access to Analytic Server on the LDAP server.
b. Create an OS user account for each of the users created in the previous step on each and every Analytic Server node and Hadoop node.
c. Create a user home folder on HDFS for the Analytic Server administrator user. The home folder permission must be set to 755, the owner must be defined as admin, and the user group must be set as hdfs. See
the following example after creating the "admin" account:
[root@xxxxx configuration]# hadoop fs -ls /user
drwxr-xr-x - admin hdfs 0 2019-06-14 01:30 /user/admin
drwxr-xr-x - user1 hdfs 0 2019-06-14 02:12 /user/user1
the following example after creating the "admin" account:
[root@xxxxx configuration]# hadoop fs -ls /user
drwxr-xr-x - admin hdfs 0 2019-06-14 01:30 /user/admin
drwxr-xr-x - user1 hdfs 0 2019-06-14 02:12 /user/user1
d. Create a user home folder on HDFS for the Analytic Server standard user (e.g user1). The folder owner is the user itself and the user group must be set as hdfs.
3. Install the "createrepo" package on all Analytic Server and Analytic Metastore nodes in your cluster. (For Ubuntu, please install package "dpkg-dev")
Installation Instructions
Cloudera installation instructions
--------------------------
Install 3.2.1.1, restore analytic root and installation configuration settings
--------------------------
Upgrading from Analytic Server 3.2.1 to 3.2.1.1 - Cloudera
If you have an existing installation of Analytic Server 3.2.1, you can upgrade the installation to 3.2.1.1 (3.2.1 Fix Pack 1).
Backup Analytic Server 3.2.1 analytic root and installation configuration settings
Note: {AS_ROOT} refers to the location where Analytic Server 3.2.1 is deployed; for example, /opt/cloudera/parcels/AnalyticServer-3.2.1.0.
Note: {AS_ROOT} refers to the location where Analytic Server 3.2.1 is deployed; for example, /opt/cloudera/parcels/AnalyticServer-3.2.1.0.
1. In the Cloudera Manager console, stop the Analytic Server service.
2. Backup the analytic root of Analytic Server 3.2.1.
a. If you are unsure of the location of the analytic root, run hadoop fs -ls. The path to the analytic root is in the form /user/as_user/analytic-root, where as_user is the user ID that owns the analytic root.
b. Log in to the Analytic Server host and run the following copy script.
sudo -u as_user hadoop distcp hdfs://{host of 3.2.1 namenode}/user/as_user/analytic-root hdfs://{host of 3.2.1 namenode}/user/as_user/analytic-root_v321
3. If you use the embedded Apache Directory Server, backup the current user/group configuration with a 3rd-party LDAP client tool.
Note: This step can be skipped if you use an external LDAP server.
4. Backup the configuration settings of Analytic Server 3.2.1.
a. Extract the configcollector.zip in {AS_ROOT}/tools. This creates a new configcollector subdirectory in the {AS_ROOT}/tools folder.
cd /opt/cloudera/parcels/AnalyticServer-3.2.1.0/tools
unzip configcollector.zip
unzip configcollector.zip
b. Run the configuration collector tool by executing the configcollector script ({AS_ROOT}/tools/configcollector/configcollector.sh). Copy the resulting compressed (ZIP) file to the server where you will start a new Cloudera installation.
cd /opt/cloudera/parcels/AnalyticServer-3.2.1.0/tools/configcollector
chmod +x configcollector.sh
./configcollector.sh
A file named ASConfiguration_3.2.1.0.34.zip is created in the current directory. Copy this zip file to a backup folder, for example, /3.2.1_bak/ASConfiguration_3.2.1.0.34.zip.
chmod +x configcollector.sh
./configcollector.sh
A file named ASConfiguration_3.2.1.0.34.zip is created in the current directory. Copy this zip file to a backup folder, for example, /3.2.1_bak/ASConfiguration_3.2.1.0.34.zip.
5. In Cloudera Manager, delete the Analytic Server service.
6. In Cloudera Manager, Deactivate, Remove From Hosts, and Delete the Analytic Server.
Install 3.2.1.1, restore analytic root and installation configuration settings
Note: Before installing Analytic Server 3.2.1.1 on Cloudera, you must first cleanup any remnants of the Analytic Server 3.2.1 installation package. This is accomplished by deleting the following:
a. any existing 3.2.1 files (csd, parcels, parcel-cache and parcel-repo folder)
b. the Analytic Server user directory in HDFS. The default location is /user/as_user/analytic-root.
sudo -u as_user hadoop fs -rm -r -skipTrash /user/as_user/analytic-root
b. the Analytic Server user directory in HDFS. The default location is /user/as_user/analytic-root.
sudo -u as_user hadoop fs -rm -r -skipTrash /user/as_user/analytic-root
1. Install Analytic Server 3.2.1.1.
Copy the AnalyticServer-3.2.1.1.jar to the default CSD installation directory. The default path is /opt/cloudera/csd.
Copy the AnalyticServer-3.2.1.1.jar to the default CSD installation directory. The default path is /opt/cloudera/csd.
2. Restart Cloudera Manager. (Also restart Cloudera Management Service if you are prompt in Cloudera Manager Console)
service cloudera-scm-server restart
service cloudera-scm-server restart
3. Copy the required parcel and metadata files to your local Cloudera repo path on the Cloudera Manager master cluster node. The default path is /opt/cloudera/parcel-repo (the path is configurable in the Cloudera Manager user interface).
Select the parcel files and metadata that are appropriate for your particular operating system.
Select the parcel files and metadata that are appropriate for your particular operating system.
RedHat Linux requires the following files:
AnalyticServer-3.2.1.1-el7.parcel
AnalyticServer-3.2.1.1-el7.parcel.sha
SuSE Linux 11 requires the following files:
AnalyticServer-3.2.1.1-el7.parcel.sha
SuSE Linux 11 requires the following files:
AnalyticServer-3.2.1.1-sles11.parcel
AnalyticServer-3.2.1.1-sles11.parcel.sha
AnalyticServer-3.2.1.1-sles11.parcel.sha
SuSE Linux 12 requires the following files:
AnalyticServer-3.2.1.1-sles12.parcel
AnalyticServer-3.2.1.1-sles12.parcel.sha
AnalyticServer-3.2.1.1-sles12.parcel.sha
Ubuntu Linux 14.04 requires the following files:
AnalyticServer-3.2.1.1-trusty.parcel
AnalyticServer-3.2.1.1-trusty.parcel.sha
Ubuntu Linux 16.04 requires the following files:
AnalyticServer-3.2.1.1-trusty.parcel.sha
Ubuntu Linux 16.04 requires the following files:
AnalyticServer-3.2.1.1-xenial.parcel
AnalyticServer-3.2.1.1-xenial.parcel.sha
AnalyticServer-3.2.1.1-xenial.parcel.sha
The AnalyticServer parcel shows as downloaded after Cloudera Manager refreshes the parcel. You can click Check for New Parcels to force a refresh.
4. In Cloudera Manager Parcels page, select Distribute > Activate for AnalyticServer.
4. In Cloudera Manager Parcels page, select Distribute > Activate for AnalyticServer.
The AnalyticServer parcel shows as distributed and activated.
5. In Cloudera Manager, add Analytic Server as a service and decide where to place the Analytic Server.
Please refer to the IBM SPSS Analytic Server 3.2.1 Installation and Configuration Guide for details.
Please refer to the IBM SPSS Analytic Server 3.2.1 Installation and Configuration Guide for details.
You need to provide the following information in the Add Service Wizard:
Analytic Server metastore host name
Analytic Server metastore database name
Analytic Server metastore user name
Analytic Server metastore password
Analytic Server Spark Version
LDAP configuration
Analytic Server metastore database name
Analytic Server metastore user name
Analytic Server metastore password
Analytic Server Spark Version
LDAP configuration
The Add Service Wizard shows the overall progress during each phase of the service creation process, and provides a final confirmation message when the service is successfully installed and configured on the cluster.
Note: After successfully installing Analytic Server, do not click Create Analytic Server Metastore in the Actions list on the Analytic Server services page in Cloudera Manager. Creating a metastore overwrites the existing metadata repository. If you want to change the "Analytic Server Spark Version" value, you must uninstall Analytic Server and then reinstall with the correct Spark version.
6. After the Analytic Server service is installed and added in Cloudera Manager, stop the Analytic Server service in Cloudera Manager.
7. Clear the Zookeeper state. In the Zookeeper server host's bin directory (for example, /opt/cloudera/parcels/CDH/lib/zookeeper/bin on Cloudera), run the following command:
./zkCli.sh rmr /AnalyticServer
Note: An exception may occur if the amount of data being written to Zookeeper is too large.
"unexpected error, closing socket connection and attempting reconnect
java.io.IOException: Packet len21555633 is out of range!"
In Cloudera Manager, navigate to the Zookeeper service Configuration tab and raise the value to "Jute Max Buffer" (the default value is 4 MB), then restart the Zookeeper service.
Modify zkCli.sh and add JVM property, for example, "-Djute.maxbuffer=41943040".
"unexpected error, closing socket connection and attempting reconnect
java.io.IOException: Packet len21555633 is out of range!"
In Cloudera Manager, navigate to the Zookeeper service Configuration tab and raise the value to "Jute Max Buffer" (the default value is 4 MB), then restart the Zookeeper service.
Modify zkCli.sh and add JVM property, for example, "-Djute.maxbuffer=41943040".
8. Restore the analytic root from the Analytic Server 3.2.1 installation.
a. Log into the new Analytic Server host and delete the hdfs directory /user/as_user/analytic-root.
sudo -u as_user hadoop fs -rm -r -skipTrash /user/as_user/analytic-root
sudo -u as_user hadoop fs -rm -r -skipTrash /user/as_user/analytic-root
b. Run the following copy script.
sudo -u as_user hadoop distcp hdfs://{host of 3.2.1 namenode}/user/as_user/analytic-root_v321 hdfs://{host of 3.2.1 namenode}/user/as_user/analytic-root
9. If you use the embedded Apache Directory Server, import the backup user/group configuration to the Apache Directory Server.
Note: This step can be skipped if you use an external LDAP server.
10. Restore the configuration settings from the Analytic Server 3.2.1 installation.
a. Run the migration tool in your new installation by executing the migrationtool script (located in the /opt/cloudera/parcels/AnalyticServer-3.2.1.1/bin directory) and passing the path of the compressed file, that was created by the configuration collector, as an argument.
For example:
cd /opt/cloudera/parcels/AnalyticServer-3.2.1.1/bin
./migrationtool.sh /3.2.1_bak/ASConfiguration_3.2.1.0.34.zip
./migrationtool.sh /3.2.1_bak/ASConfiguration_3.2.1.0.34.zip
11. Run the following command from a command shell on the Analytic Server node:
sudo -u as_user hadoop fs -chmod -R 755 /user/as_user/analytic-root/analytic-workspace
sudo -u as_user hadoop fs -chmod -R 755 /user/as_user/analytic-root/analytic-workspace
12. In Cloudera Manager, run "Refresh Analytic Server Binaries" and start the Analytic Server service. Analytic Server 3.2.1.1 is now ready for use.
Cloudera uninstallation instructions
--------------------------
For uninstall information, please refer to the IBM SPSS Analytic Server 3.2.1 Installation and Configuration Guide.
HDP installation instructions
--------------------------
Upgrading from Analytic Server 3.2.1 to 3.2.1.1 - RedHat/Suse
Analytic Server allows you to migrate data and configuration settings from an existing Analytic Server installation to a new installation. If you have an existing installation of Analytic Server 3.2.1, you can upgrade the installation in place to version 3.2.1.1.
1. In the Ambari console, stop the Analytic Server service.
2. On the Analytic Server node, rename "IBM-SPSS-AnalyticServer-3.2.1.0.repo" to "IBM-SPSS-AnalyticServer-3.2.1.1.repo" (/etc/yum.repos.d for RHEL or /etc/zypp/repos.d for SLES).
Note: If the file "IBM-SPSS-AnalyticServer-3.2.1.0.repo" does not exist (often occurs on HDP 3.0 and above), please create one new repo file with the name "IBM-SPSS-AnalyticServer-3.2.1.1.repo".
3. Create a new directory (similar to the following example) that will serve as the repository for the Analytic Server 3.2.1.1 RPM files.
For example.
a. mkdir -p /root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/
b. Copy the necessary Analytic Server 3.2.1.1 RPM files to this directory. The RPM files you need depend on your distribution, version, and architecture.
For HDP 2.5 and 2.6, 3.0, 3.1:
IBM-SPSS-AnalyticServer-3.2.1.1-1.x86_64.rpm
c. Update the content of IBM-SPSS-AnalyticServer-3.2.1.1.repo to the following
[IBM-SPSS-AnalyticServer]
name=IBM-SPSS-AnalyticServer-3.2.1.1
baseurl={path to local repository} (e.g file:///root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/)
path=/
enabled=1
gpgcheck=0
name=IBM-SPSS-AnalyticServer-3.2.1.1
baseurl={path to local repository} (e.g file:///root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/)
path=/
enabled=1
gpgcheck=0
4. Clean the Ambari metadata from your local cache. For example, to clean the cache on RHEL, run the following command:
sudo yum clean all
On SLES, the command changes as follows:
sudo zypper refresh
5. Create the local Yum repository, similar to the following example:
createrepo /root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/
6. On each Analytic Server host, upgrade the RPMs. For example, to upgrade on RHEL, run the following commands:
sudo yum upgrade IBM-SPSS-AnalyticServer
On SLES, the command changes as follows:
sudo zypper up IBM-SPSS-AnalyticServer
chown -R as_user:hadoop /opt/ibm/spss/analyticserver/3.2
7. Navigate to the folder: /opt/ibm/spss/analyticserver/3.2/ae_wlpserver/usr/servers/aeserver/modules/spark/, and then run the following command:
rm -rf com.ibm.spss.sparkmapreduce-3.2.1.1.jar
8. Remove the folder /opt/ibm/spss/analyticserver/3.2/lib/as-spark-lib-backup
9. Repeat the previous steps on all the Analytic Server and Analytic Metastore nodes in your cluster.
10. On the Ambari master node, update your Ambari repository file "repoinfo.xml (typically located in /var/lib/ambari-server/resources/stacks/HDP/<stackVersion>/repos/) to use the local Yum repository. (<stackVersion> is your HDP version)
10. On the Ambari master node, update your Ambari repository file "repoinfo.xml (typically located in /var/lib/ambari-server/resources/stacks/HDP/<stackVersion>/repos/) to use the local Yum repository. (<stackVersion> is your HDP version)
a. In the repoinfo.xml, locate to the section that matches your OS type (for example, <os family="redhat7">)
b. Within this section, change the <baseurl> and <reponame> values:
<os family="{host_os_type}">
......
<repo>
<baseurl>{path to local repository} (e.g file:///root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/)</baseurl>
<repoid>IBM-SPSS-AnalyticServer</repoid>
<reponame>IBM-SPSS-AnalyticServer-3.2.1.1</reponame>
</repo>
......
</os>
......
<repo>
<baseurl>{path to local repository} (e.g file:///root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/)</baseurl>
<repoid>IBM-SPSS-AnalyticServer</repoid>
<reponame>IBM-SPSS-AnalyticServer-3.2.1.1</reponame>
</repo>
......
</os>
11. On the Ambari master node, edit the file "server.env.j2".
For HDP 3.x series:
/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ANALYTICSERVER/package/templates/server.env.j2
/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ANALYTICSERVER/package/templates/server.env.j2
For HDP 2.x series:
/var/lib/ambari-server/resources/stacks/HDP/2.5/services/ANALYTICSERVER/package/templates/server.env.j2
/var/lib/ambari-server/resources/stacks/HDP/2.5/services/ANALYTICSERVER/package/templates/server.env.j2
Change the HDP_VERSION value as follows:
HDP_VERSION={{fully_qualified_stack_version}}
HDP_VERSION={{fully_qualified_stack_version}}
Change the SPARK_HOME value as below:
{% elif spark_current_ver==2 %}
SPARK_HOME=/usr/hdp/current/spark2-client
{% endif %}
{% elif spark_current_ver==2 %}
SPARK_HOME=/usr/hdp/current/spark2-client
{% endif %}
12. On the Ambari master node, run the "ambari-server restart" command on your cluster.
13. In the Ambari console, run the Refresh action on the SPSS Analytic Server service.
14. In the Ambari console, start the Analytic Server service.
15. On the cluster node where the Analytic Metastore is installed, start the ADS service. Navigate to the folder /opt/ibm/spss/analyticserver/3.2/ads/bin and run the following command to check ADS service status:
./apacheds.sh status
If the ADS service is not running, run the following command:
./apacheds.sh start
Upgrading from Analytic Server 3.2.1 to 3.2.1.1 - Ubuntu
1. In the Ambari console, stop the Analytic Server service.
2. On the Analytic Server node, create a <local_repo> directory that serves as the repository for the Analytic Server DEB files. For example:
mkdir –p /usr/local/mydebs
3. Copy the required Analytic Server DEB files to the <local_repo> directory:
IBM-SPSS-AnalyticServer_1_amd64.deb
4. Create the local repository.
a. Install the tool that creates a local repository:
apt-get install dpkg-dev
b. Generate the source package file:
cd <local_repo>
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz
c. Create the component (main) and architecture (for example, binary-i386, binary-amd64) of your local repository:
mkdir -p <local_repo>/dists/IBM-SPSS-AnalyticServer/main/binary-amd64/
mkdir -p <local_repo>/dists/IBM-SPSS-AnalyticServer/main/binary-i386/
mkdir -p <local_repo>/dists/IBM-SPSS-AnalyticServer/main/binary-i386/
d. Copy the source package:
cp -fr <local_repo>/Packages.gz <local_repo>/dists/IBM-SPSS-AnalyticServer/main/binary-amd64/Packages
cp -fr <local_repo>/Packages.gz <local_repo>/dists/IBM-SPSS-AnalyticServer/main/binary-i386/Packages
cp -fr <local_repo>/Packages.gz <local_repo>/dists/IBM-SPSS-AnalyticServer/main/binary-i386/Packages
5. Create the local repository definition. For example, create a file that is named IBM-SPSSAnalyticServer-
3.2.1.1.list in /etc/apt/sources.list.d with the following content.
3.2.1.1.list in /etc/apt/sources.list.d with the following content.
deb file:<local_repo> ./
6. Run the following command to update the repository list:
apt-get update
7. Run the following command to upgrade IBM SPSS Analytic Server 3.2.1:
dpkg upgrade IBM-SPSS-AnalyticServer_1_amd64.deb
8. Navigate to the folder: /opt/ibm/spss/analyticserver/3.2/ae_wlpserver/usr/servers/aeserver/modules/spark/, and run the following command:
rm -rf com.ibm.spss.sparkmapreduce-3.2.1.1.jar
9. Remove the folder /opt/ibm/spss/analyticserver/3.2/lib/as-spark-lib-backup
10. Repeat the previous steps on all the Analytic Server and Analytic Metastore nodes in your cluster.
11. On the Ambari master node, update your Ambari repository file "repoinfo.xml" (typically located in /var/lib/ambari-server/resources/stacks/HDP/<stackVersion>/repos/) to use the local Yum repository. (<stackVersion> is your HDP version)
11. On the Ambari master node, update your Ambari repository file "repoinfo.xml" (typically located in /var/lib/ambari-server/resources/stacks/HDP/<stackVersion>/repos/) to use the local Yum repository. (<stackVersion> is your HDP version)
a. In the repoinfo.xml file, locate to the section that matches your OS type (for example, <os family="redhat7">).
b. Within this section, change the <baseurl> and <reponame> values.
<os family="{host_os_type}">
......
<repo>
<baseurl>{path to local repository} (e.g file:///root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/)</baseurl>
<repoid>IBM-SPSS-AnalyticServer</repoid>
<reponame>IBM-SPSS-AnalyticServer-3.2.1.1</reponame>
</repo>
......
</os>
......
<repo>
<baseurl>{path to local repository} (e.g file:///root/repos/IBM-SPSS-AnalyticServer/3.2.1.1/)</baseurl>
<repoid>IBM-SPSS-AnalyticServer</repoid>
<reponame>IBM-SPSS-AnalyticServer-3.2.1.1</reponame>
</repo>
......
</os>
12. On the Ambari master node, edit the file "server.env.j2".
For HDP 3.x series:
/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ANALYTICSERVER/package/templates/server.env.j2
/var/lib/ambari-server/resources/stacks/HDP/3.0/services/ANALYTICSERVER/package/templates/server.env.j2
For HDP 2.x series:
/var/lib/ambari-server/resources/stacks/HDP/2.5/services/ANALYTICSERVER/package/templates/server.env.j2
/var/lib/ambari-server/resources/stacks/HDP/2.5/services/ANALYTICSERVER/package/templates/server.env.j2
Change the HDP_VERSION value as follows:
HDP_VERSION={{fully_qualified_stack_version}}
HDP_VERSION={{fully_qualified_stack_version}}
Change the SPARK_HOME value as follows:
{% elif spark_current_ver==2 %}
SPARK_HOME=/usr/hdp/current/spark2-client
{% endif %}
{% elif spark_current_ver==2 %}
SPARK_HOME=/usr/hdp/current/spark2-client
{% endif %}
13. On the Ambari master node, run the "ambari-server restart" command on your cluster.
14. In the Ambari console, run the Refresh action on the SPSS Analytic Server service.
15. In the Ambari console, start Analytic Server service.
16. On the cluster node where Analytic Metastore is installed, start the ADS service. Navigate to folder /opt/ibm/spss/analyticserver/3.2/ads/bin and run the following command to check the ADS service status:
./apacheds.sh status
If the ADS service is not running, run the following command:
./apacheds.sh start
HDP troubleshooting
--------------------------
1. If you want to import user and group information from an XML file to an ADS profile, via the importUser.sh script, you need to perform the following steps:
--------------------------
1. If you want to import user and group information from an XML file to an ADS profile, via the importUser.sh script, you need to perform the following steps:
a. Unzip the file /opt/ibm/spss/analyticserver/3.2/tools/ads.zip to a temp folder
b. Copy the file "com.ibm.spss.embeddedADS-3.2.1.1.jar" from the temp folder "./ads/lib/" to your installed ADS folder "/opt/ibm/spss/analyticserver/3.2/ads/lib/"
c. Run the importUser.sh script with the required parameters.
HDP uninstallation instructions
--------------------------
For uninstall information, please refer to the IBM SPSS Analytic Server 3.2.1 Installation and Configuration Guide.
Off
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWLVY","label":"IBM SPSS Analytic Server"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.1.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
26 June 2019
UID
ibm10888113