SPSS Modeler 15.0 Fix Pack 1 - Premium Add-ons

1. Back-up the options.cfg file in your Modeler Client or Modeler Server installation's \config directory.
2. Download the zip file containing the fix pack you require, and extract the contents of the .zip file. Doing so creates a .exe file.
3. Ensure Modeler Client or Batch is shut down before applying the fix pack for Text Analytics, Entity Analytics, or Social network Analysis. If you are updating Modeler Server, Text Analytics Server, or Entity Analytics Server, ensure that the corresponding Server service is stopped.
4. Double-click the .exe file that you have downloaded. The installer automatically finds your Modeler 15.0 installation.
5. When the installation wizard is displayed, choose "Next" and then "Install" to apply the fix pack.

WARNING: If you are downloading the UNIX or Linux Fix Packs using Internet Explorer, using the HTTP download method, do not left-click the package on the Fix Central page that displays the package for download because this will cause your browser to freeze. Instead, right-click on the package and select "save target as" to download it.

1. Back-up the options.cfg file in your Modeler Server installation's \config directory.

2. Download the appropriate .bin file containing the fix pack you require and ensure that it is executable by performing a chmod u+x fixpack.bin operation, where fixpack.bin denotes the fix pack that you downloaded.

3. If you are updating Modeler Server, Text Analytics Server, or Entity Analytics Server, ensure that the corresponding Server service is stopped and back up its installation directories. After you have stopped the Modeler and Text Analytics Servers run the command:

./modelersrv.sh list

This command should return no processes.

4. On AIX ONLY, enter the following command:

/usr/sbin/slibclean

5. Ensure that you are logged in as the user that originally installed the product.

6. If you are installing the Modeler Server, Text Analytics Server, or Entity Analytics Server fix pack, copy the .bin file to the Modeler Server installation directory.

7. Execute the .bin file that you copied into the product's installation directory and follow the installation wizard prompts. An example of executing a .bin file is:

./ea_aix64.bin

8. If you are updating Social Network Analytics Server these fix packs are provided as .zip files. Download the fix pack to a temporary location on your file system and extract the contents of the .zip file to obtain the separate server and worker installers. Execute the relevant .bin file and follow the installation wizard prompts. When prompted for an installation directory, specify the Modeler Server installation directory.


To stop the EA service (and SolidDB if applicable):

Invoke the manage_repository script with the -stop option:

cd <modeler-install-directory>\ext\bin\pasw.entityanalytics
manage_repository.bat|.sh –stop <repository-name> <username> <password>

For example:
pasw.entityanalytics> ./manage_repository.sh -stop AAA myuser mypass
Stopping local EA service
Shutdown command sent to EA service
Stopping local SolidDB server
Shutdown command sent to SolidDB server

To check if EA service and SolidDB are running:

Invoke the manage_repository script with the -check option:

cd <modeler-install-directory>\ext\bin\pasw.entityanalytics
manage_repository.bat|.sh -check<repository-name> <username> <password>

For example:
pasw.entityanalytics > ./manage_repository.sh -check AAA myuser mypass
SolidDB server is running on host localhost, port 1320
EA service is running on host localhost, port 1321

For C&DS 4.2.1: C&DS 4.2.1 FP 3 (4.2.1.3)

For C&DS 4.2: No Fix Pack required

c). 15.0 FP1 must also be applied to any Modeler Premium components you are using (Text Analytics, EA, SNA). If you are using these components within C&DS the 15.0 FP1 Modeler Premium adapter must also be applied to your C&DS installation after applying the 15.0 FP1 Modeler Professional adapter.

Installation Instructions

Windows systems only

1. Download the .zip file containing the correct adapter for your operating system and version of Collaboration and Deployment Services, and extract the contents of the zip file. Doing so creates a .exe file.

The Modeler Premium FP1 adapter packages do not depend on the C&DS version into which you are installing, they depend only on the C&DS operating system. The same Modeler Premium FP1 adapter package applies to C&DS 4.2, 4.2.1 and 5.0.

2. Ensure that the Collaboration and Deployment Services application server is in the following state:

- JBoss: shutdown

- WebLogic: shutdown

- WebSphere: running, but various applications must be shut down. If using a WebSphere application, log into the WebSphere profile and disable the following five applications: scoring, scoring-ejb, admin, security, and security-ws.

Here are the steps to disable the auto start for an application:

a). Go to the Target specific application status page for your application. Click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

b). Select the target server on which the application resides.

c). Click Disable Auto Start.

d). Save changes to the administrative configuration.

e). Restart WebSphere.

3. Double-click the .exe file that you have extracted from the .zip file.

4. Follow the on-screen instructions to complete the installation. When prompted, enter the username and password of the repository administrator. Ensure that the installation folder is set correctly. NOTE that for C&DS 4.2 and 4.2.1 there is an additional "Server" subdirectory within the directory to which the Collaboration and Deployment Services software was installed at the repository host that must be included, for example:

For C&DS 4.2.1:

C:\Program Files\IBM\SPSS\Collaboration and Deployment Services\4.2.1\Server

For C&DS 4.2:

C:\Program Files\IBM\SPSS\Collaboration and Deployment Services\4.2\Server

5. If using a WebSphere application, log into the WebSphere profile and enable each application disabled in step 2.

Here are the steps to enable the auto start for an application:

a). Go to the Target specific application status page for your application. Click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

b). Select the target server on which the application resides.

c). Click Enable Auto Start.

d). Save changes to the administrative configuration

e). Restart WebSphere.

6. Restart the Collaboration and Deployment Services Application server or service.

Unix systems except IBM System i (iSeries)

WARNING: If you are downloading the UNIX or Linux Fix Packs using Internet Explorer, using the HTTP download method, do not left-click the package on the Fix Central page that displays the package for download because this will cause your browser to freeze. Instead, right-click on the package and select "save target as" to download it.

1. Download the binary (.bin) file containing the correct adapter for your operating system and version of Collaboration and Deployment Services.

The Modeler Premium FP1 adapter packages do not depend on the C&DS version into which you are installing, they depend only on the C&DS operating system. The same Modeler Premium FP1 adapter package applies to C&DS 4.2, 4.2.1 and 5.0.

2. Ensure that the .bin file is executable by performing a chmod u+x fixpack.bin operation, where fixpack.bin denotes the fix pack that you downloaded.

3. Ensure that the Collaboration and Deployment Services application server is in the following state:

- JBoss: shutdown

- WebLogic: shutdown

- WebSphere: running, but various applications must be shut down. If using a WebSphere application, log into the WebSphere profile and disable the following five applications: scoring, scoring-ejb, admin, security, and security-ws.

Here are the steps to disable the auto start for an application:

a). Go to the Target specific application status page for your application. Click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

b). Select the target server on which the application resides.

c). Click Disable Auto Start.

d). Save changes to the administrative configuration.

e). Restart WebSphere.

4. Execute the .bin file from step 2. For example:

./15.0-IM-S15MPCDS5-Solaris-FP001.bin

5. Follow the on-screen instructions to complete the installation. When prompted, enter the username and password of the repository administrator. NOTE that for C&DS 4.2 and 4.2.1 there is an additional "Server" subdirectory within the directory to which the Collaboration and Deployment Services software was installed at the repository host that must be included, for example:

For C&DS 4.2.1:

/opt/IBM/SPSS/Collaboration_and_Deployment_Services/4.2.1/Server

For C&DS 4.2:

/opt/IBM/SPSS/Collaboration_and_Deployment_Services/4.2/Server

6. If using a WebSphere application, log into the WebSphere profile and enable each application disabled in step 3.

Here are the steps to enable the auto start for an application:

a). Go to the Target specific application status page for your application. Click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

b). Select the target server on which the application resides.

c). Click Enable Auto Start.

d). Save changes to the administrative configuration.

e). Restart WebSphere.

7. Restart the Collaboration and Deployment Services Application server or service.

IBM System i (iSeries)

1. Download the .zip file containing the correct adapter for your operating system and version of Collaboration and Deployment Services.

The Modeler Premium FP1 adapter packages do not depend on the C&DS version into which you are installing, they depend only on the C&DS operating system. The same Modeler Premium FP1 adapter package applies to C&DS 4.2, 4.2.1 and 5.0.

2. Extract the contents of the .zip file using the jar utility. This will create an install.jar file. For example:

jar -xvf 15.0-IM-S15MPCDS5-iSeries-FP001.zip

3. If using a WebSphere application server, ensure it is in the following state:

Running, but various applications must be shut down. If using a WebSphere application, log into the WebSphere profile and disable the following three applications: admin, security, and security-ws.

Here are the steps to disable the auto start for an application:

a). Go to the Target specific application status page for your application. Click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

b). Select the target server on which the application resides.

c). Click Disable Auto Start.

d). Save changes to the administrative configuration.

e). Restart WebSphere.

4. Execute the install.jar file that was extracted from the .zip file:

java –jar install.jar

5. Follow the on-screen instructions to complete the installation. When prompted, enter the username and password of the repository administrator. NOTE that for C&DS 4.2 and 4.2.1 there is an additional "Server" subdirectory within the directory to which the Collaboration and Deployment Services software was installed at the repository host that must be included, for example:
For C&DS 4.2.1:

/opt/IBM/SPSS/Collaboration_and_Deployment_Services/4.2.1/Server

For C&DS 4.2:

/opt/IBM/SPSS/Collaboration_and_Deployment_Services/4.2/Server

6. If using a WebSphere application, log into the WebSphere profile and enable each application disabled in step 3.

Here are the steps to enable the auto start for an application:

a). Go to the Target specific application status page for your application. Click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

b). Select the target server on which the application resides.

c). Click Enable Auto Start.

d). Save changes to the administrative configuration.

e). Restart WebSphere.

Note: Under some circumstances, the installer for iSeries will be unable to determine the available disk space on the disk partition where Collaboration and Deployment Services has been installed, and will report a number of errors instead. These errors can safely be ignored as they do not affect installation of the adapter.

An example of the errors reported is shown below, where <install-dir> is the directory where you installed Collaboration and Deployment Services:

#### Cannot match UNIX flavor to a filesystem table: attempting '/etc/fstab'

fstab: /etc/fstab (A file or directory in the path name does not exist.)

** FileSystem (FSTab): could not generate static fs table

#### Cannot match UNIX flavor to a filesystem table: attempting 'df -k'

CheckDiskSpace: Error determining free disk space for:

<install-dir>

java.lang.NoClassDefFoundError: com/ibm/as400/access/IFSFile

…

at com.zerog.ia.installer.AAMgrBase.m(DashoA10*..)

at com.zerog.ia.installer.LifeCycleManager.a(DashoA10*..)

at com.zerog.ia.installer.LifeCycleManager.a(DashoA10*..)

at com.zerog.ia.installer.Main.main(DashoA10*..)

at install.main(DashoA10*..)

CDS: Assuming sufficient disk space. (-1)

These errors may occur if you use the command "java -jar install.jar" to install the adapter. As an alternative, you can execute the adapter_os400_install.qsh file (extracted from the .zip file) and complete the installation. The qsh content is available here:
#!/QOpenSys/usr/bin/sh
java -cp ./jt400Native.jar:./install.jar install

Should you experience further issues with this installation, contact Technical Support.