Interstage Shunsaku Data Manager Installation Guide

Installation Guide

Trademarks Trademarks of other companies are used in this manual only to identify particular products or systems.

Product Trademark/Registered Trademark

Microsoft, Visual C++, Windows, and Windows Server

Registered trademark or trademarks of Microsoft Corporation in the United States and other countries.

Solaris Solaris and all other trademarks and logos related to Solaris are registered trademarks or trademarks of Sun Microsystems Inc. U.S.A. in the United States and other countries, and are used under license from the said company.

Linux Registered trademark or trademark of Linus Torvalds in the United States and other countries.

Java Java and other trademarks comprising Java are trademarks of Sun Microsystems Inc. U.S.A. in the United States and other countries.

CORBA CORBA is a registered trademark of Object Management Group, Inc. in the United States and other countries.

Red Hat, RPM, and all trademarks and logos based on Red Hat

Trademarks or registered trademarks of Red Hat Inc. in the United States and other countries.

Oracle Oracles a registered trademark of Oracle Corporation.

Interstage Interstage is a registered trademark of Fujitsu Limited.

Fujitsu documentation may contain specific technologies that are subject to the Foreign Exchange and Foreign Trade Control Law. When such specific technology is described in a document, and that document is either exported or provided to a non-resident, permission must be sought under the above law.

Fujitsu Limited

First Edition (December 2005) Second Edition (January 2006)

The contents of this manual may be revised without prior notice. All Rights Reserved, Copyright © FUJITSU Limited 2005-2006

ii

Preface

Purpose of this Manual This manual describes the install and uninstall methods for the Interstage Shunsaku Data Manager (hereafter abbreviated as Shunsaku).

Target Audience This manual is intended for use by persons installing or using Shunsaku.

Required Knowledge This manual assumes that the reader has an understanding of the following topics:

• Internet basics

• Solaris(TM) Operating System

• Windows

• Linux

iii

Preface

Organization of this Manual This manual is organized as follows:

• Chapter 1 - Shunsaku Configurations

This chapter describes the various Shunsaku system configurations.

• Chapter 2 - Preparing for Installation

This chapter describes the preparation required before installing Shunsaku.

• Chapter 3 - Shunsaku System Installation and Setup

This chapter describes the procedures required for Shunsaku system installation and setup.

• Chapter 4 - Installation and Setup of Application Server APIs

This chapter describes installation of the Shunsaku APIs on an application server.

• Chapter 5 - Installing an Upgrade

This chapter describes the procedures for upgrading Shunsaku.

• Chapter 6 - Uninstall

This chapter describes the procedures used to uninstall Shunsaku.

• Appendix A - Migration Operations

This appendix describes the procedures for migration from a 6.0 Shunsaku system to a 7.0 system.

• Appendix B - How to Set Up IPC Resources

This appendix describes how to set up IPC resources.

iv

Table of Contents

Chapter 1 Shunsaku Configurations Basic Configuration.....................................................................................................................1-2 Multi-server Configurations.........................................................................................................1-3

Chapter 2 Preparing for Installation Basic Software ............................................................................................................................2-2 Related Software ........................................................................................................................2-4

Application Development Environment Information ..............................................................2-4 HA Function Information ........................................................................................................2-5 XML Conversion Information .................................................................................................2-5

Databases Suitable for the XML Conversion Function.....................................................2-5 JDBC Drivers Required for the XML Conversion Function ..............................................2-5

Excluded Software ......................................................................................................................2-6 Required Patches .......................................................................................................................2-7 Hardware Requirements.............................................................................................................2-8 Setting Environment Variables..................................................................................................2-11

Chapter 3 Shunsaku System Installation and Setup Installation and Setup for Systems Running Searchers on Separate Servers...........................3-2

Installing Shunsaku on the Director Server ...........................................................................3-2 Installation from the GUI ...................................................................................................3-2 Installation without the GUI...............................................................................................3-9

Setup the Director Server ....................................................................................................3-13 Identifier Setup................................................................................................................3-13 Port Number Definition ...................................................................................................3-13 Environment File Creation ..............................................................................................3-14 IPC Resource Setup.......................................................................................................3-14

Installing Shunsaku on Search Servers...............................................................................3-14 Installation from the GUI .................................................................................................3-15 Installation without the GUI.............................................................................................3-17

Setting Up Search Servers ..................................................................................................3-18 Defining Searcher Port Numbers....................................................................................3-18 Editing the Searcher Environment File ...........................................................................3-19 Registering Host Names.................................................................................................3-19

v

Table of Contents

Setting Up the Operating System .................................................................................. 3-20 Setting Up the Director Server............................................................................................ 3-21

Editing and Distributing the System Environment File .................................................. 3-21 Registering Host Names................................................................................................ 3-22

Installation and Setup with Additional Search Servers ............................................................ 3-23 Installation and Setup with Additional Director Servers ........................................................... 3-24

Shunsaku Installation.......................................................................................................... 3-24 Installation from the GUI ................................................................................................ 3-24 Installation without the GUI............................................................................................ 3-30

Setup for Systems with Additional Director Servers ........................................................... 3-32 Defining Director Port Numbers..................................................................................... 3-32 Editing the Director Environment File ............................................................................ 3-33 Registering Host Names................................................................................................ 3-33 Setting up the Operating System................................................................................... 3-34

Installation and Setup with Additional Sort Servers ................................................................. 3-36 Shunsaku Installation.......................................................................................................... 3-36

Installation from the GUI ................................................................................................ 3-36 Installation without the GUI............................................................................................ 3-36

Setup for Systems with Additional Sort Servers ................................................................. 3-37 Defining Sorter Port Numbers........................................................................................ 3-37 Editing Sorter Environment Files ................................................................................... 3-38 Registering Host Names................................................................................................ 3-38 Setting Up the Operating System .................................................................................. 3-38

Chapter 4 Installation and Setup of Application Server APIs Shunsaku API Installation .......................................................................................................... 4-2

Under Solaris ........................................................................................................................ 4-2 Installation from the GUI .................................................................................................. 4-2 Installation without the GUI.............................................................................................. 4-2

Under Windows..................................................................................................................... 4-3 Under Linux........................................................................................................................... 4-4

Installation from the GUI .................................................................................................. 4-5 Installation without the GUI.............................................................................................. 4-5

Chapter 5 Installing an Upgrade Migrating from Shunsaku 6.x ..................................................................................................... 5-2

Shunsaku Versions that can be Migrated ............................................................................. 5-2 Servers to be Migrated.......................................................................................................... 5-2 Operating Configurations and System Configurations ......................................................... 5-2

Director Server and Search Server Upgrade Installation .......................................................... 5-3 Upgrade Installation on Director Servers.............................................................................. 5-3 Upgrade Installation on Search Servers ............................................................................... 5-4 Migration Operations............................................................................................................. 5-5

vi

Table of Contents

Upgrade Installation on Application Servers...............................................................................5-6 Under Solaris .........................................................................................................................5-6 Under Windows .....................................................................................................................5-6 Under Linux............................................................................................................................5-6

Differences between Shunsaku 6.0 and 7.0...............................................................................5-7 System Start and Stop ...........................................................................................................5-7 Search Expressions...............................................................................................................5-7 Monitoring ..............................................................................................................................5-7

Chapter 6 Uninstall Uninstall on Search Servers .......................................................................................................6-2

Shunsaku Uninstallation ........................................................................................................6-2 Uninstall on Sort Servers ............................................................................................................6-4

Shunsaku Uninstallation ........................................................................................................6-4 Uninstall on Director Servers ......................................................................................................6-6

Shunsaku Uninstallation ........................................................................................................6-6 Uninstall for Application Servers .................................................................................................6-7

Under Solaris .........................................................................................................................6-7 Under Windows .....................................................................................................................6-7 Under Linux............................................................................................................................6-8

Appendix A Migration Operations Migration Procedures................................................................................................................. A-2 Director Server Migration........................................................................................................... A-3

Resources to be Migrated during Director Server Migration ................................................ A-3 Director Server Migration Procedures .................................................................................. A-3 Checking the System Process Configuration ....................................................................... A-4

Checking the System Operating Format ......................................................................... A-4 Checking the Conductor Information............................................................................... A-4 Checking the Sorter Information...................................................................................... A-4 Checking the Director Information................................................................................... A-5 Checking the Searcher Information................................................................................. A-5

Determining the Shunsaku System Name............................................................................ A-5 Creating and Editing Environment Files ............................................................................... A-5

Creating the System Environment File ............................................................................ A-6 Creating and Editing the Conductor Environment File .................................................. A-12 Creating and Editing the Sorter Environment File ......................................................... A-13 Editing the Director Environment Files .......................................................................... A-14

Defining Port Numbers ....................................................................................................... A-15 Setting up the Operating System........................................................................................ A-16

IPC Resource Settings .................................................................................................. A-16

vii

Table of Contents

Distributing the System Environment File................................................................................A-17 Migrating Search Servers ........................................................................................................A-18

Resources to be Migrated during Search Server Migration ...............................................A-18 Search Server Migration Procedures..................................................................................A-18

Checking the Searchers to be Migrated ........................................................................A-18 Editing the Searcher Environment Files ........................................................................A-18

Appendix B How to Set Up IPC Resources Modifying the Kernel Configuration File (/etc/system) ............................................................... B-2 Resource Management.............................................................................................................. B-3

viii

Chapter 1 Shunsaku Configurations

This chapter describes the various Shunsaku system configurations.

• Basic Configuration

• Multi-server Configurations

1-1

Chapter 1: Shunsaku Configurations

Basic Configuration This section describes the basic Shunsaku system configuration:

• Systems Running Searchers on Separate Servers

The conductor, director, and sorter are allocated to the director server, and the searchers are allocated to and operate on the search server.

Figure 1-1 Systems Running Searchers on Separate Servers

1-2

Multi-server Configurations

Multi-server Configurations This section describes extended system configurations for Shunsaku.

These configurations can be customized to suit particular user requirements.

Shunsaku can be installed and set up using combinations of the following system configurations:

• Systems running with additional director servers

Figure 1-2 Systems Running with Additional Director Servers

1-3

Chapter 1: Shunsaku Configurations

• Systems running with additional sort servers

Figure 1-3 Systems running with additional sort servers

The procedure for setting up these configurations is to first set up a system running searchers on separate servers and then add servers.

Refer to Adding Directors and Director Servers and Adding Sorters and Sort Servers in the Operator's Guide (Advanced) for details.

1-4

Chapter 2 Preparing for Installation

This chapter describes the preparation required before installing Shunsaku.

• Basic Software

• Related Software

• Excluded Software

• Required Patches

• Hardware Requirements

• Setting Environment Variables

2-1

Chapter 2: Preparing for Installation

Basic Software The basic software below is required on each of the following servers where Shunsaku is to be used:

• Director Server

• Sort Server

• Search Server

• Application Server

Director Server Solaris(TM) 8 Operating System

Solaris(TM) 9 Operating System

Solaris(TM) 10 Operating System (*1)

*1 This product can only be installed in a Solaris global zone, (not in a non-global zone).

Sort Server Solaris(TM) 8 Operating System




Search Server

Red Hat Enterprise Linux AS (v.3 for x86)

Red Hat Enterprise Linux ES (v.3 for x86)

Application Server





2-2

Basic Software

Microsoft(R) Windows(R) 2000 Server operating system

Microsoft(R) Windows(R) 2000 Advanced Server operating system

Microsoft(R) Windows Server(TM) 2003, Standard Edition

Microsoft(R) Windows Server(TM) 2003, Enterprise Edition

Red Hat Enterprise Linux AS (v.3 for x86)

Red Hat Enterprise Linux ES (v.3 for x86)

2-3


Related Software This section describes other software that can be used with the various Shunsaku functions.

Application Development Environment Information This section describes the application development environment required by Shunsaku.

If Java API is used One of the following is required:

• If the basic software is Solaris(TM) 10 Operating System

− Java2 SDK 1.4.2_07 or later

− Java2 Runtime Environment 1.4.2_07 or later

• If the basic software is other than the above product

− Java2 SDK 1.3 or later

− Java2 Runtime Environment 1.3 or later

If C API is used One of the following is required:

• Microsoft(R) Visual C++(R) Version 6.0 or later

• gcc and other related packages (*1)

• Sun WorkShop Compiler C 4.2 or later (*2), or Fujitsu C Compiler 4.0 (*3)

*1 Only compilers provided by the operating system products are supported

*2 Sun WorkShop Compiler C is not a product name. It is the name of a component that is incorporated in the products listed below. Therefore, to get Sun WorkShop Compiler C, you must have one of the following products:

− Sun Visual WorkShop C++ 3.0 or later

− Sun WorkShop Professional C 3.0 or later

− Sun WorkShop Compilers C/C++ 4.2 or later

− Sun Performance WorkShop Fortran 3.0 or later

Note that the following products of Forte Developer, the follow-on product after Sun WorkShop, are also supported:

− Forte C++ Enterprise Edition

− Forte C++ Personal Edition

− Forte C

− Forte for High Performance Computing

− Forte Fortran Desktop Edition

2-4

Related Software

*3 Fujitsu C Compiler is not a product name. It is the name of a component that is incorporated in the products listed below. Therefore, to obtain the Fujitsu C Compiler, you must have one of the following products:

− C Development package 4.0

− C++ Professional package 4.0

If Application Server Plus Developer is used

Interstage Application Server Plus Developer V7.0

If Apworks is used

Interstage Apworks Modelers-J Edition V7.0

HA Function Information The following cluster system software is required for the director server failover function:

• PRIMECLUSTER V4.1A30 or later

XML Conversion Information This section provides information related to the XML conversion function provided by Shunsaku.

Databases Suitable for the XML Conversion Function The following databases are suitable for the XML conversion function:

• PostgreSQL 7.4.x

• Oracle 8i

• Oracle 9i

• Oracle 10g

• Microsoft(R) SQL Server 2000

2-5


JDBC Drivers Required for the XML Conversion Function If the XML conversion function is to be used, use a driver that suits JDBC2.0 or later.

The following JDBC drivers are recommended for the XML conversion function:

Database JDBC driver

PostgreSQL pg74.215.jdbc2.jar or pg74.215.jdbc3.jar

Oracle classes12.zip or ojdbc14.jar

SQL Server The following three files are required:

- msbase.jar

- mssqlserver.jar

- msutil.jar

2-6

Excluded Software

Excluded Software None.

2-7


Required Patches The patches listed in the following table are required to use Shunsaku:

Table 2-1 Required Patches

No. Product name Patch ID/PTF

1 Solaris(TM) 10 Operating System 119689-06 2 Red Hat Enterprise Linux AS (v.3 for x86) Update4 3 Red Hat Enterprise Linux ES (v.3 for x86) Update4

2-8

Hardware Requirements

Hardware Requirements The hardware described below is required when Shunsaku is used.

Verify that sufficient free disk space is available for installation.

If there is insufficient disk space, increase the size of the relevant file system.

Shunsaku System Servers CPU : 550MHZ or more

Memory : 64 MB or more

CD-ROM drive

Network card

Hard disk:

• Standard installation

− Director server : 17.2 MB or more

Directory Disk space (Unit: MB)

/ 0.1

/usr 0.1

/var 8.8

/home 0.0

/$DIR(*1) 8.8

*1 "$DIR" is the directory name specified during installation of this software.

− Search server : 2.2 MB or more


/ 0.1

/usr 0.1

/var 0.1

/home 0.0

/opt 2.0

2-9


• Custom installation

− Director server : 8.8 MB or more


/ 0.1

/usr 0.1

/var 4.7

/home 0.0

/$DIR(*1) 4.7


− Sort server : 5.6 MB or more


/ 0.1

/usr 0.1

/var 2.7

/home 0.0

/$DIR(*1) 2.7


Note

• The above amounts indicate the space required during Shunsaku installation.

• Calculate the space required based on the combination of functions installed on each server.

For details of the resources required to run Shunsaku, refer to Estimating Resources in the Operator’s Guide, Operator's Guide (Advanced) and the Application Development Guide.

Application Servers CPU : 550MHZ or more

Memory : 64 MB or more 256 MB or more

CD-ROM drive

Network card

Hard disk:

2-10

Hardware Requirements

• : 7.2 MB or more


/ 0.1

/usr 0.1

/var 3.5

/home 0.0

/$DIR(*1) 3.5





/ 0.1

/usr 0.1

/var 0.1

/home 0.0

/opt 3.1

Note

• The above amounts indicate the space required during Shunsaku installation.

For details of the resources required for Shunsaku to run applications, refer to Estimating Resources in the Application Development Guide.

2-11


Setting Environment Variables This section explains how to set the environment variables that are required to use Shunsaku commands and the man command.

Refer to the Application Development Guide for more information on the environment variables that are required to use the Shunsaku APIs.

Setting Environment Variables for the Director Server • Set "ja" in the LANG environment variable if the character encoding is EUC; "ja_JP.PCK" if the

character encoding is Shift-JIS; and "C" if the character encoding is English.

• Add "/opt/FJSVshnsk/bin" to the PATH environment variable.

• Add "/opt/FJSVshnsk/man" to the MANPATH environment variable.

Examples of how to set the environment variables are provided below.

Example 1 For Bourne and Korn shells LANG= C ; export LANG PATH=/opt/FJSVshnsk/bin:$PATH ; export PATH MANPATH=/opt/FJSVshnsk/man:$MANPATH ; export MANPATH

Example 2 For C shell setenv LANG C setenv PATH /opt/FJSVshnsk/bin:$PATH setenv MANPATH /opt/FJSVshnsk/man:$MANPATH

2-12

Setting Environment Variables

Setting Environment Variables for Search Servers • Set "C" or "ja_JP.eucJP" for the LANG environment variable.

• Add "/opt/FJSVshnsk/bin" to the PATH environment variable.

• Add "/opt/FJSVshnsk/man" to the MANPATH environment variable.

Examples of how to set the environment variables are provided below.

Example 1 For bash, Bourne and Korn shells LANG= C ; export LANG PATH=/opt/FJSVshnsk/bin:$PATH ; export PATH MANPATH=/opt/FJSVshnsk/man:$MANPATH ; export MANPATH

Example 2 For C shell setenv LANG C setenv PATH /opt/FJSVshnsk/bin:$PATH setenv MANPATH /opt/FJSVshnsk/man:$MANPATH

2-13


2-14

Chapter 3 Shunsaku System Installation and Setup

This chapter describes the procedures required for Shunsaku system installation and setup.

• Installation and Setup for Systems Running Searchers on Separate Servers

• Installation and Setup with Additional Search Servers

• Installation and Setup with Additional Director Servers

• Installation and Setup with Additional Sort Servers.

3-1

Chapter 3: Shunsaku System Installation and Setup

Installation and Setup for Systems Running Searchers on Separate Servers

This section explains the procedures for installing and setting up a system that uses a Solaris director with Linux search servers.

First set up the Solaris director server, then set up the Linux search servers where the searchers are located.

Installing Shunsaku on the Director Server The installation procedure is explained below.

The following two installation methods are available:

• Installation from the GUI

• Installation without the GUI

Note

• A superuser must perform the installation.

Installation from the GUI The procedure for installing Shunsaku APIs from the GUI is explained below.

Note

• In an X Window system environment, the graphic mode must be set to true color (depth 24bit), and the screen size must be set to XGA (1024x768) or higher using the following three steps. Refer to the Solaris manual for further details.

1. Log in.

2. Enter the text below: fbconfig -res horizontal-width x vertical-heightxfrequency nocheck

- depth 24

3. Log in again.

• The font size must be set to Medium in the font style manager. Characters may not display correctly on the GUI if other font sizes are set.

• Specify "C" for the LANG environment variable.

3-2


To install Shunsaku APIs from the GUI:

1. Start the Shunsaku installation script (install.sh). The "/dev/dsk/c0t4d0s2" device name will differ depending on the environment used. # mount -F hsfs –o ro /dev/dsk/c0t4d0s2 /cdrom/cdrom0 # cd /cdrom/cdrom0/solaris # ./install.sh

In the dialog displayed, click the Install button.

2. In the Select Setup Type dialog, select TYPICAL, then click the Next button.

3-3


3. In the Confirm Setup Information dialog, verify the settings:

− To proceed with the installation process using the displayed settings, select Do not modify, then click the Next button. The installation process will start. Proceed to step 7.

− If the host name or IP address could not be acquired automatically, select Modify, to specify these settings manually, then click the Next button. Proceed to step 4.

3-4


4. In the Modify Settings dialog, select Interstage Shunsaku Data Manager, and specify the Installation Directory.

The following table explains the item to be specified.

Item name Explanation

Installation directory Specify the absolute path of the directory where the package will be stored.

Hash characters "#", blanks and multi-byte characters cannot be specified for the directory name.

The directory specified here must already exist.

If Java environments such as Java APIs or XML conversion functions are to be used, do not include “;”, “%”, “^”, or “!” in the pathname of the installation directory. Depending on the Java environment used, use of these characters may lead to abnormal Shunsaku operation.

3-5


5. In the Modify Settings dialog, select the FJSVshncd package. Specify the Shunsaku system name, the Host name or IP address, the Director data file directory, the Port number for receiving requests, and the Character encoding identifier. If necessary, check the option Automatically set up IPC resources. Then click the Next button.

The following table explains the items to be specified.


Shunsaku system name Specify the name assigned to the Shunsaku system. Specify up to 8 bytes of alphanumeric characters.

Host name or IP address Specify the host name or IP address of the server where the Shunsaku system will run. Loopback address “127.0.0.1” or the host name that represents “127.0.0.1” (usually "localhost") cannot be specified.

Director data file directory Specify the name of the folder (absolute path) where the director data file is stored. Hash characters "#", blanks and multi-byte characters cannot be specified for the directory name. Shunsaku uses this directory, so do not place anything else in this location.

Port number for receiving requests

Specify the port number used to receive requests from the Shunsaku API.

3-6



Character encoding identifier

Specify the character encoding used in the character strings that are search targets. Select one of the following specifications: UTF-8: UTF-8 SHIFT-JIS: Shift-JIS (Japanese) EUC: EUC-JP (Japanese) GB2312: GB2312 (Chinese) big5: Big5 (Chinese) KSC5601: KSC5601 (Korean)

Automatically set up IPC resources

If the server where Shunsaku is installed is used only for Shunsaku, check this option to automatically set up IPC resources The parameters in the /etc/system file will be changed automatically. Clear this option if other products are to be installed on the same server as Shunsaku, or if IPC resources are set up using Solaris 10 resource management. For details on setting up IPC resources, refer to IPC Resource Settings under Setting up the Operating System.

6. If the information displayed in the Confirm Setup Information dialog is correct, click the Next button. The installation process will start.

3-7


7. After the installation process completes, in the Result of Package installation dialog, click the Next button to save the installation log.

3-8


8. In the Output Install Log dialog, ensure the Save installation log checkbox is checked, specify the Output destination directory, and then click the Finish button.

9. Restart the system if Automatically set up IPC resources has been checked in step 5.

Installation without the GUI The installation procedure when the GUI is not used is explained below.

1. Start the Shunsaku installation script (cmdinstall.sh). (The "/dev/dsk/c0t4d0s2" device name will differ depending on the environment used.) # mount –F hsfs –o ro /dev/dsk/c0t4d0s2 /cdrom/cdrom0 # cd /cdrom/cdrom0/solaris # ./cmdinstall.sh

2. Select the installation method by entering 1 and pressing ENTER. ---------------------------------------------------------- Interstage Shunsaku Data Manager Enterprise Edition 7.0.1 All Rights Reserved, Copyright(c) FUJITSU LIMITED 2003-2006 ---------------------------------------------------------- Please select the installation type. (1: typical, 2: custom) [1,2,q]:

3-9


3. Specify the directory where the package will be stored. To install Shunsaku using the default value ("/opt"), press ENTER. To change the storage directory, specify the absolute path of the storage directory, then press ENTER. Please specify installation directory. (default: /opt) [?,q]:

Note

− The directory name must not include hash characters ‘#’, double-byte characters, or space characters.

− The specified directory must already exist.

− If Java environments such as Java APIs or XML conversion functions are to be used, do not include “;”, “%”, “^”, or “!” in the pathname of the installation directory. Depending on the Java environment used, use of these characters may lead to abnormal Shunsaku operation.

4. Specify the name to be assigned to the Shunsaku system. To perform installation using the default value (“shunsaku”), press ENTER. To change the name assigned to the Shunsaku system, specify a new name using up to eight alphanumeric characters, then press ENTER. Please specify the Shunsaku system name. (default: shunsaku) [?,q]:

5. Specify the host name or IP address of the server where the Shunsaku system will run. To perform installation using the default value (the host name or IP address that is acquired automatically), press ENTER. To change the host name or IP address of the server where the Shunsaku system will run, specify the new host name or IP address, then press ENTER. In the following example, “DirSvr1” is a host name that is acquired automatically. Please specify the host name or the IP address. (default: DirSvr1) [?,q]:

Note

− Loopback address “127.0.0.1” or the host name that represents “127.0.0.1” (usually "localhost") cannot be specified.

6. Specify the name of the directory where the director data file is stored. To perform installation using the default value (/Shunsaku), press ENTER. To change the name of the directory where the director data file is stored, specify the absolute path of the new directory, then press ENTER. Please specify the Director data file directory. (default: /Shunsaku) [?,q]:

Note


− Do not place any files in the specified directory as this directory is used by Shunsaku.

3-10


7. Specify the port number for receiving requests from the Shunsaku APIs.

To perform installation using the default value (the port number that is acquired automatically), press ENTER. To change the port number for receiving requests from the Shunsaku APIs, specify the new port number, then press ENTER. In the following example, “33101” is a port number that is acquired automatically. Please specify port number for receiving request. (default: 33101) [?,q]:

Note

− Do not specify a port number that is already in use.

8. Specify the character encoding used in the character strings to be searched.

To perform installation using the default value (1. UTF-8), press ENTER.

To change the character encoding used in the character strings to be searched, specify the number corresponding to the new character encoding, then press ENTER. Character encoding identifier: 1. UTF-8 2. SHIFT-JIS 3. EUC 4. GB2312 5. big5 6. KSC5601 Please select character encoding identifier. (default: 1) [?,q]:

The following table explains the items to be entered:


UTF-8 UTF-8

SHIFT-JIS Shift-JIS (Japanese)

EUC EUC-JP (Japanese)

GB2312 GB2312 (Chinese)

big5 Big5 (Chinese)

KSC5601 KSC5601 (Korean)

9. Specify if IPC resources should be set up automatically.

− Enter “y” and press ENTER if the server where Shunsaku is installed is used only for Shunsaku. In this case, the parameters in the /etc/system file will be changed automatically.

− Enter “n” and press ENTER if other products are to be installed on the same server as Shunsaku, or if IPC resources are set up using Solaris 10 resource management. For details on setting up IPC resources, refer to IPC Resource Settings under Setting up the Operating System.

Specify if IPC resources will be set up automatically. (default: n) [y,n,q]

3-11


10. Enter “y” and press ENTER to start the installation process using the displayed information. Install information: Installation functions: director conductor sorter API Installation packages: FJSVshnsk FJSVshnsy FJSVshndr FJSVshncd FJSVshnso FJSVshnap FJSVshndb Installation directory: /opt Shunsaku system name: shunsaku Host name or IP address: DirSvr1 Director data file directory: /Shunsaku Port number for receiving requests: 33101 Character encoding identifier: UTF-8 Automatically set up IPC resources: No. Do you want to proceed with the installation ? [y,q]:

The installation process will start. Installation of packages has started. Installation of <FJSVshnsk> was successful. : Installation of packages has ended.

If there is a processing error, the following message will be displayed and the installation process will be terminated. Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

If the installation is successful, a message will be displayed indicating that the installation process has completed. An installation log will be created in “/opt/FJSVshnsk/setup.log". Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was successful.

11. If Automatically set up IPC resources was specified in step 9, restart the system.

3-12


Setup the Director Server When installation is complete, the following setup tasks are performed automatically:

• Identifier Setup

• Port Number Definition

• Environment File Creation

• IPC Resource Setup (if Automatically set up IPC resources was specified)

Note

− By default IPC resources are not set up automatically. If Automatically set up IPC resources was not specified, refer to IPC Resource Settings under Setting up the Operating System for details on setting up IPC resources.

Identifier Setup The following identifiers are set:

Type Identifier name Shunsaku system name The value specified at installation conductor identifier shunc director identifier shund1 sorter identifier shuno1

Port Number Definition The port numbers used by Shunsaku are defined in the following services file:

/etc/services

If a "typical" installation has been performed, the services file will be defined using the following format: # Inserted by the Interstage Shunsaku (begin) shunc 33101/tcp # conductor (1) shund1_1 33301/tcp # director 1_1 (2) shund1_2 33302/tcp # director 1_2 (3) shund1_3 33303/tcp # director 1_3 (4) shuno1 33201/tcp # sorter (5) # Inserted by the Interstage Shunsaku (end)

(1) The port number for receiving requests from APIs specified at installation time

(2) The port number for issuing search requests to searchers that have the port number for the director (acquired automatically)

(3) The port number for issuing update requests to searchers that have the port number for the director (acquired automatically)

(4) The port number for receiving requests from the director.

(5) The port number for receiving requests from the conductor that has the port number for the sorter (acquired automatically)

3-13


Environment File Creation The following environment files are created:

Type Environment file name

System environment file /etc/opt/FJSVshnsk/etc/system/Shunsaku system name.cfg

conductor environment file

/etc/opt/FJSVshnsk/etc/conductor/shunc.cfg

director environment file /etc/opt/FJSVshnsk/etc/director/shund1.cfg sorter environment file /etc/opt/FJSVshnsk/etc/sorter/shuno1.cfg

Refer to Execution Parameters in Environment Files in the Operator's Guide (Advanced) for details of the execution parameters of the various environment files.

IPC Resource Setup The IPC resources will be changed as follows:

Type Number of instances started at simultaneously

Conductor 1 Director 1 Sorter 1

Refer to IPC Resource Settings in Setting up the Operating System for more information on setting up IPC resources.

Installing Shunsaku on Search Servers This section explains the procedure for installing Shunsaku on servers where searchers are located.

Repeat this installation procedure for each server where searchers are located.




Note


3-14



Note

• For X Window system environments, the screen size must be at least XGA (1024x768).


• The openmotif environment (openmotif21 package) must already be installed.

1. Start the Shunsaku installation script (install.sh). # mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/redhat # ./install.sh

Execute Install in the dialog that is displayed after the installation script is executed.

2. In the Select Setup Type dialog, select Typical, then click the Next button.

3-15


3. If the settings in the Confirm Setup Information dialog are correct, check the Do not modify checkbox, then click the Next button. The installation process will then start.

4. After the installation process completes, in the Result of Package installation dialog, click the Next button to save the installation log.

3-16


5. In the Output Install Log dialog, ensure the Save installation log checkbox has been selected, specify the Output destination directory, and then click the Finish button.


1. Start the Shunsaku installation script (cmdinstall.sh). # mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/redhat # ./cmdinstall.sh

2. Select the installation method by entering 1 and pressing ENTER. ---------------------------------------------------------- Interstage Shunsaku Data Manager Enterprise Edition V7.0L11 All Rights Reserved, Copyright(c) FUJITSU LIMITED 2003-2006 ---------------------------------------------------------- Please select the installation type. (1: typical, 2: custom) [1,2,q]:

3-17


3. Enter “y” and press ENTER to start the installation process using the displayed information. Install information: Installation functions: searcher Installation packages: FJSVshnsk FJSVshnsy FJSVshnsh Do you want to proceed with the installation ? [y,q]:


If there is a processing error, the following message will be displayed and the installation process will be terminated. Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

If the installation was successful, a message will be displayed indicating that the installation process has completed. An installation log will be created in “/opt/FJSVshnsk/setup.log". Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was successful.

Setting Up Search Servers This section explains the procedure for setting up servers where searchers are located.

Defining Searcher Port Numbers Specify the port number that is to receive requests from the director.

The port number used by a searcher is specified in the following search server file:

/etc/services

The specification format is shown below.

Format service-name port-number/protocol

Service name

Specify a character string that is easily associated with the searcher.

3-18


Port number

Specify a port number that is not in use at the search server.

Protocol

Specify tcp.

Example

A definition example is shown below.

If "shuns01" is specified as the service name of the searcher: shuns01 33501/tcp (1)

(1) Port number for receiving requests from the director

Note

• The Port number for receiving requests from the director must be specified in the Searcher parameter of the system environment file.

Refer to Appendix A, Execution Parameters in Environment Files in the Operator’s Guide (Advanced) for details of the system environment file execution parameters.

Editing the Searcher Environment File Copy and edit the following searcher environment file sample:

/etc/opt/FJSVshnsk/etc/searcher/searcher.cfg-sample

Set searcher-identifier.cfg as the filename of the edited searcher environment file and store it in the same folder as the sample file.

For the searcher identifier, use a character string comprising up to 8 bytes of alphanumeric characters.

Refer to Searcher Environment Files in Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details of the searcher environment file execution parameters.

Registering Host Names If host names have been specified in the system environment file without using IP addresses, specify the host name and IP address of the director server in the following file on the search server:

/etc/hosts


Format IP-address host-name

IP address

Specify the IP address of the director server.

3-19


Host name

Specify the host name of the director server.

Example

A definition example is shown below. 192.168.0.10 DirSvr1

Setting Up the Operating System This section describes how to setup the Operating System.

IPC Resource Settings Shunsaku uses the System V IPC resources provided by the operating system for communications between the different processes that make up Shunsaku. IPC resources must be set up according to the definitions for the Shunsaku operating environment to successfully run Shunsaku.

The following IPC resource settings are required to run Shunsaku:

• Shared memory resources

• Semaphore resources

These settings are made using the kernel configuration file (/etc/sysctl.conf).

The parameter values in the tables below are required to run Shunsaku.

If values have already been set in the kernel configuration file, check these values and add or change them as required.

If no values are set in the kernel configuration file, the operating system’s default values will be used, so add or change these default values as required.

For the parameters indicated as ‘max’ in the following explanation, set a larger value than the existing value (the default value or the value that has already been set). For parameters indicated as ‘add’, add the value given in the ‘Value’ column to the existing value.

After editing the kernel configuration file, either restart the system or execute "sysctl -p /etc/sysctl.conf".

Shared Memory Resources Set the following values for shared memory resources.

Kernel parameter name Value Remarks

kernel.shmmax 1048576 or more max kernel.shmmni The number of searchers that will run

simultaneously add

Semaphore Resources Set the following values for semaphore resources.

Entry Format kernel.sem = para1 para2 para3 para4

3-20


Set the following values for para1, para2, para3, and para4.

Kernel parameter name Value Remarks

para1 (*1) 1 or more max para2 The number of searchers that will run

simultaneously × 10 add

para3 (*1) 1 or more max para4 The number of searchers that will run

simultaneously × 10 add

*1 When setting para1 and para3, set a value that is equal to or greater than the default value for the operating system.

Setting Up the Director Server This section explains the procedure for setting up the director server.

Editing and Distributing the System Environment File Edit and distribute the system environment file as follows.

1. Add the following parameter to the system environment file.

Execution parameter name Meaning

Searcher Server information for the searcher

2. Distribute the system environment file to the following directory on the server where the searcher is located.

/etc/opt/FJSVshnsk/etc/system/

3-21


Registering Host Names If host names have been specified in the server information for the searcher without using IP addresses, specify in the following file the host name and IP address of the server where the searcher is located.

/etc/hosts



IP address

Specify the search server IP address.

Host name

Specify the search server host name.

Example

A definition example is shown below. 192.168.0.20 SchSvr01

3-22

Installation and Setup with Additional Search Servers

Installation and Setup with Additional Search Servers

This section explains how to install and set up Shunsaku when creating a multi-server configuration system where search servers will be added.

Refer to Installing Shunsaku on Search Servers and Setting Up Search Servers for information on installing and setting up Shunsaku when adding search servers.

3-23


Installation and Setup with Additional Director Servers

This section describes installation and setup for a multi-server system that has additional director servers.

Shunsaku Installation This section explains how to install Shunsaku when director servers are added.




Note



Note

• In an X Window system environment, the graphic mode must be set to true color (depth 24bit), and the screen size must be set to XGA (1024x768) or higher using the following three steps. Refer to the Solaris manual for further details.

1. Log in

2. Enter the following: fbconfig -res horizontal-widthxvertical-heightxfrequency nocheck -depth 24

3. Log in again.

• The font size must be set to Medium in the font style manager. Characters may not display correctly on the GUI if other font sizes are set.


3-24


To install Shunsaku when directors servers are added:

1. Start the Shunsaku installation script (install.sh). (The "/dev/dsk/c0t4d0s2" device name will differ depending on the environment used.) # mount -F hsfs –o ro /dev/dsk/c0t4d0s2 /cdrom/cdrom0 # cd /cdrom/cdrom0/solaris # ./install.sh

In the dialog displayed after the installation script is executed, click the Install button.

2. In the Select Setup Type dialog, select CUSTOM, then click the Next button.

3-25


3. In the Choose components to install dialog,select Interstage Shunsaku Data Manager, then specify the Installation Directory

The following table explains the items to be specified:


Installation directory Specify the absolute path of the directory where the package will be stored. Hash characters "#", blanks and multi-byte characters cannot be specified for the directory name. The directory specified here must be created in advance. If Java environments such as Java APIs or XML conversion functions are to be used, do not include “;”, “%”, “^”, or “!” in the pathname of the installation directory. Depending on the Java environment used, use of these characters may lead to abnormal Shunsaku operation.

3-26


4 In the Choose components to install dialog, select the FJSVshndr package, and click the Next button.

3-27


5. If the settings in the Confirm Setup Information dialog are correct, click the Next button. The installation process will begin.

3-28


6 After the installation process completes, in the Result of Package installation dialog, click the Next button to save the installation log.

3-29


7. In the Output Install Log dialog, ensure the Save installation log checkbox has been selected, specify the Output destination directory, and then click the Finish button.


1. Start the Shunsaku installation script (cmdinstall.sh). (The "/dev/dsk/c0t4d0s2" device name will differ depending on the environment used.) # mount –F hsfs –o ro /dev/dsk/c0t4d0s2 /cdrom/cdrom0 # cd /cdrom/cdrom0/solaris # ./cmdinstall.sh

2. Select the installation method by entering 2 and pressing ENTER. ---------------------------------------------------------- Interstage Shunsaku Data Manager Enterprise Edition 7.0.1 All Rights Reserved, Copyright(c) FUJITSU LIMITED 2003-2006 ---------------------------------------------------------- Please select the installation type. (1: typical, 2: custom) [1,2,q]:

3-30


3. Specify the directory where the package will be stored. To install Shunsaku using the default value ("/opt"), press ENTER. To change the storage directory, specify the new directory name using its absolute path, then press ENTER. Please specify installation directory. (default: /opt) [?,q]:

Note


− The specified directory must already exist.

− If Java environments such as Java APIs or XML conversion functions are to be used, do not include “;”, “%”, “^”, or “!” in the pathname of the installation directory. Depending on the Java environment used, use of these characters may lead to abnormal Shunsaku operation.

4. Select the function to be installed by entering 1 and pressing ENTER. Functions: 1. director 2. sorter 3. API Please select functions. [?,all,q]:

5. Enter “y” and press ENTER to start the installation process using the displayed information. Install information: Installation functions: director Installation packages: FJSVshnsk FJSVshnsy FJSVshndr Installation directory: /opt Do you want to proceed with the installation ? [y,q]:


If there is a processing error, the following message will be displayed, and the installation process will be terminated. Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

3-31


If the installation is successful, a message will be displayed indicating that the installation process has completed. An installation log will be created in “/opt/FJSVshnsk/setup.log". Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was successful.

Setup for Systems with Additional Director Servers This section describes setup for systems with additional director servers.

Defining Director Port Numbers The port numbers used by the director are specified in the following director server file:

/etc/services

The following definitions are required for the port numbers used by the director:

• Port number for issue of search requests to the searcher

• Port number for issue of update requests to the searcher

• Port number for receiving requests



Service name

Specify a character string that is easily associated with the director.

Port number

Specify a port number that is not in use at the director server.

Protocol

Specify tcp.

Example


If "shund1_1", "shund1_2", and "shund1_3" are specified as the director service names: shund1_1 33301/tcp (1) shund1_2 33302/tcp (2) shund1_3 33303/tcp (3)

(1) Port number for issue of search requests to the searcher

(2) Port number for issue of update requests to the searcher

(3) Port number for receiving requests

3-32


Note

• The port numbers used by the director must be specified in the Director parameters in the system environment file.

Refer to Execution Parameters in Environment Files in Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details of the system environment file execution parameters.

Editing the Director Environment File Copy and edit the following director environment file sample:

/etc/opt/FJSVshnsk/etc/director/director.cfg-sample

Set director-identifier.cfg as the filename of the edited director environment file and store it in the same folder as the sample file.

For the director identifier, use a character string comprising up to 8 bytes of alphanumeric characters.

Refer to Director Environment Files in Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details of director environment file execution parameters.

Registering Host Names If host names, rather than IP addresses, are specified in the system environment file, specify the search server IP address and host name in the following file at the added director servers:

Repeat this task if there are multiple search servers.

/etc/hosts



IP address

Specify the search server IP address.

Host name

Specify the search server host name.

Example

A definition example is shown below. 192.168.0.30 SchSvr01

3-33


Setting up the Operating System This section describes how to set up the operating system.

IPC Resource Settings Shunsaku uses the System V IPC resources provided by the operating system for communications between the different processes that make up Shunsaku. IPC resources must be set up according to the definitions for the Shunsaku operating environment to successfully run Shunsaku.

The following IPC resource settings are required to run Shunsaku:

• Shared memory resources

• Semaphore resources

The parameter values in the tables below are required to run Shunsaku.

If values have already been set in the kernel configuration file or by resource management, check these values and add or change them as required. If no values are set, the operating system’s default values will be used, so add or change these default values as required. Refer to Appendix B, How to Set Up IPC Resources for information on how to make these changes.

For the parameters indicated as ‘max’ in the following explanation, set a larger value than the existing value (the default value or the value that has already been set). For parameters indicated as ‘add’, add the value given by the formula to the existing value.

Shared Memory Resources

Kernel parameter name Resource management name

Value Remarks

shminfo_shmmax project.max-shm-memory 1MB or more max shminfo_shmmni project.max-shm-ids The number of Shunsaku

processes that start simultaneously (*1)

add

shminfo_shmseg - The number of Shunsaku processes that start simultaneously (*1)

add

*1 This is the number of directors, conductors and sorters.

Note

• For the Solaris 9 and later, the "shminfo_shmseg" parameter has been discontinued and is not valid, so there is no need to set this parameter.

3-34


Semaphore Resources Set the following values for semaphore resources.

Kernel parameter name

Resource management name

Value Remarks

seminfo_semmni project.max-sem-ids The number of Shunsaku processes that start simultaneously (*1) × 10

add

seminfo_semmns - The number of Shunsaku processes that start simultaneously (*1) × 10

add

seminfo_semmnu -

The number of Shunsaku processes that start simultaneously (*1) × 10

add

*1 This is the number of directors, conductors, and sorters.

Note For Solaris 10 and later, the ‘seminfo_semmns’ and ‘seminfo_semmnu’ parameters have been discontinued and are not valid, so there is no need to set these parameters.

3-35


Installation and Setup with Additional Sort Servers This section describes installation and setup for a multi-server system that has additional sort servers.

Shunsaku Installation This section describes installation for systems that have additional sort servers.



Note



Installation from the GUI for additional sort servers is the same as that described under Installation and Setup with Additional Director Servers except for step 4.

Replace step 4 with the following: In the Choose components to install dialog, select the FJSVshnso package and click the Next button.


Installation without the GUI for additional sort servers is the same as that described under Installation and Setup with Additional Director Servers except for step 4.

Replace step 4 with the following: Enter the number corresponding to the sorter function at the ‘Please select functions’ prompt, then press ENTER.

3-36

Installation and Setup with Additional Sort Servers

Setup for Systems with Additional Sort Servers This section describes setup for a system with additional sort servers.

Defining Sorter Port Numbers Specify the definition for the port number used to receive requests from the conductor.

In the following sort server file, specify the port number used to receive sort and aggregate requests:

/etc/services



Service name

Specify a character string that is easily associated with the sorter.

Port number

Specify a port number that is not in use at the sort server.

Protocol

Specify tcp.

Example


If "shuno1" is specified as the sorter service name: shuno1 33201/tcp (1)

(1) Port number for receiving requests from the conductor

Note

• The port number for receiving requests from the conductor must be specified in the Sorter parameter of the system environment file.

Refer to System Environment Files in the Operator's Guide (Advanced) for details of the system environment file execution parameters.

3-37


Editing Sorter Environment Files Copy and edit the following sorter environment file sample:

/etc/opt/FJSVshnsk/etc/sorter/sorter.cfg-sample

Set sorter-identifier.cfg as the filename of the edited sorter environment file and store it in the same folder as the sample file.

For the sorter identifier, use a character string comprising up to 8 bytes of alphanumeric characters.

Refer to Sorter Environment Files in the Operator's Guide (Advanced) for details of the sorter environment file execution parameters.

Registering Host Names If host names, rather than IP addresses, are specified in the system environment file, specify the director server IP address and host name in the following file at the added sort servers:

/etc/hosts



IP address

Specify the director server IP address.

Host name

Specify the director server host name.

Example

A definition example is shown below. 192.168.0.10 DirSvr1

Setting Up the Operating System This section describes how to set up the operating system.

IPC Resource Settings Shunsaku uses the System V IPC resources provided by the operating system for communications between the different processes that make up Shunsaku. IPC resources must be set up according to the definitions for the Shunsaku operating environment to successfully run Shunsaku. Refer to IPC Resource Settings under Setup for Systems with Additional Director Servers for more information on setting up IPC resources.

3-38

Chapter 4 Installation and Setup of Application Server APIs

This chapter describes installation of the Shunsaku APIs on an application server.

• Shunsaku API Installation

4-1

Chapter 4: Installation and Setup of Application Server APIs

Shunsaku API Installation This section describes the Shunsaku API installation procedure.

The Shunsaku API installation procedure is different for different application server operating systems.

Under Solaris

This section describes the installation procedure for a Solaris application server.




Note



The procedure for installing the Shunsaku APIs is the same as that described in ‘Installation from the GUI’ under ‘Installation and Setup with Additional Director Servers’ in chapter 3, except for step 4.

Replace step 4 with the following:

In the Choose components to install dialog, select the FJSVshnap package, and click the Next button.

Note

• An error will occur if the FJSVshnsy package is selected.


The procedure for installing the Shunsaku APIs is the same as that described in ‘Installation without the GUI’ under ‘Installation and Setup with Additional Director Servers’ in chapter 3, except for Step 4.

Replace step 4 with the following:

Enter the number corresponding to the API function at the ‘Please select functions’ prompt, then press ENTER.

4-2

Shunsaku API Installation

Under Windows

This section describes the installation procedure for a Windows application server.

Note

• The installation must be performed by a user who belongs to the Administrators group.

• Ensure that all applications are stopped before starting installation.

1. Start the Shunsaku install program.

− Insert the CD-ROM. Insert the Shunsaku CD-ROM in the disk drive.

− Execute the install program. When the CD-ROM is inserted, the install menu is displayed. Click the Install button. If the install menu is not displayed, start the CD-ROM "MENU" (or MENU.EXE).

2. In the Welcome dialog, click the Next button.

3. In the Installation type selection dialog, select Typical, then click the Next button.

4. In the Confirm Setup Information dialog, check the settings displayed

− To proceed with the installation using the displayed settings, check the Do not modify checkbox, then click the Next button. The installation process will start. Go to Step 7. Note If the Cancel button is clicked during installation to stop the install process, the installation destination folder may remain. Delete this folder if it is no longer required.

− To change the displayed settings, check the Modify checkbox, click the Next button and go to Step 5.

5. In the Choose Destination Location dialog, specify the Destination Folder, then click the Next button.

Note

− Specify an NTFS format local disk as the drive for the installation destination folder.

− Multi-byte characters cannot be included in the folder name specified as the installation destination folder.

− If a folder that does not exist is specified, then a different folder is specified, the folder specified first may remain. Delete this folder if it is no longer required.

− If Java environments such as Java APIs or XML conversion functions are to be used, do not include “;”, “# “, “%”, “^”, or “!” in the pathname of the installation directory. Depending on the Java environment used, use of these characters may lead to abnormal Shunsaku operation.

6. If the settings shown in the Installation confirmation dialog are correct, click the Install button. The installation process will start. Note

− If the Cancel button is clicked during installation to stop the install process, the installation destination folder may remain. Delete this folder if it is no longer required.

7. After the installation and setup completes, the Complete dialog will be displayed. Check the Save installation log checkbox to save the installation settings, then click the Finish button. The settings will be saved in a file called ’setup.log’ under the installation directory.

4-3


8. In the Restarting Windows dialog, select Yes, I want to restart my computer now, then click the OK button.

Note

• If system environment variable setup fails during installation, the following message is displayed: The following path has not been set in System variables PATH. Set this path manually when the installation is complete. C:\Program Files\Interstage Shunsaku\Shunsaku\bin

Before using the system, set the system environment variable PATH using the following procedure.

For Windows 2000:

1. Click Control Panel, System, then the Details tab, and click the Environment variables button.

2. Delete unnecessary paths, then add the following path to the system environment variable PATH:

Shunsaku installation destination folder\Shunsaku\bin; 3. Restart the system.

For Windows Server 2003:

1. Click Control Panel, System, then ‘Detailed setup’, and click the Environment variables button.

2. Delete unnecessary paths, then add the following path to the system environment variable PATH:

Shunsaku installation destination folder\Shunsaku\bin; 3. Restart the system.

Under Linux

This section describes the installation procedure for a Linux application server.




Note

A superuser must perform the installation.

4-4

Shunsaku API Installation


Note

• In an X Window system environment, the screen size must be set to XGA (1024x768) or higher.

• Specify "C" as the environment variable LANG.

• The openmotif environment (openmotif21 package) must already be installed.

1. Start the Shunsaku install script (install.sh). # mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/redhat # ./install.sh

In the dialog displayed after executing this script, click the Install button. 2. In the Select Setup type dialog, select Custom, then click the Next button.

3. In the Choose components to install dialog, select the FJSVshnap package, and click the Next button.

Note

− An error will occur if the FJSVshnsy package is selected.

4. In the Confirm Setup Information dialog, if the settings are correct, click the Next button. The installation process will then begin.

5. After the installation completes, in the Result of Package installation dialog, click the Next button to save the installation log.

6. Ensure that the Save installation log checkbox has been selected in the Output Install Log dialog, then specify the Output destination directory and click Finish.


1. Start the Shunsaku install script (cmdinstall.sh). # mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/redhat # ./cmdinstall.sh

2. Select the installation method by entering 2 and pressing ENTER. ---------------------------------------------------------- Interstage Shunsaku Data Manager Enterprise Edition V7.0L11 All Rights Reserved, Copyright(c) FUJITSU LIMITED 2003-2006 ---------------------------------------------------------- Please select the installation type. (1: typical, 2: custom) [1,2,q]:

4-5


3. Select the function to be installed by entering 2 and pressing ENTER. Functions: 1. searcher 2. API Please select functions. [?,all,q]:

4. Enter “y” and press ENTER to start the installation process using the displayed information. Install information: Installation functions: API Installation packages: FJSVshnsk FJSVshnap Do you want to proceed with the installation ? [y,q]:


If there is a processing error, the following message will be displayed, and the installation process will be terminated. Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

If installation was successful, a message will be displayed indicating that the installation process has completed. An installation log will be created in “/opt/FJSVshnsk/setup.log". Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was successful.

4-6

Chapter 5 Installing an Upgrade

This chapter describes the procedures for upgrading Shunsaku.

• Migrating from Shunsaku 6.x

• Director Server and Search Server Upgrade Installation

• Upgrade Installation on Application Servers

• Differences between Shunsaku 6.0 and 7.0

This chapter uses the following version notations.

Version notation Product/version

7.x Shunsaku 7.0 Solaris Interstage Shunsaku Data Manager Enterprise Edition 7.0.1

Shunsaku 6.2 Solaris Interstage Shunsaku Data Manager Enterprise Edition 6.2 6.x

Shunsaku 6.0 Solaris Interstage Shunsaku Data Manager Enterprise Edition 6.0

5-1

Chapter 5: Installing an Upgrade

Migrating from Shunsaku 6.x This section describes the tasks involved in migrating Shunsaku from 6.0. It describes the following:

• Shunsaku Versions that can be Migrated

• Servers to be Migrated

• Operating Configurations and System Configurations

Shunsaku Versions that can be Migrated The following older Shunsaku versions can be migrated to Shunsaku 7.0:

• Interstage Shunsaku Data Manager Enterprise Edition 6.0

• Interstage Shunsaku Data Manager Enterprise Edition 6.2. (*1)

*1 This product is unavailable outside Japan. As this chapter presents examples of migration from 6.2 to 7.0, please skip over any information relating to 6.2.

Servers to be Migrated Of the servers comprising the Shunsaku system, the following are migration targets:

• Director servers

• Search servers

Operating Configurations and System Configurations Director servers targeted for migration have the following operating configurations:

• Both conductor and sorter used

• Conductor used, but sorter not used

• Conductor not used

In the system configuration of all director servers above, searchers run on separate servers.

5-2

Director Server and Search Server Upgrade Installation


This section describes the procedures used to upgrade director servers and search servers.

Upgrade Installation on Director Servers Installing the upgrade causes the environment resources to be inherited.

Note

• Upgrade installations must be performed by a superuser.

• The installation destination cannot be changed when the upgrade is installed.

• Stop Shunsaku before installing the upgrade.

1. Start the upgrade installation script (update.sh).

# mount -F hsfs -o ro /dev/dsk/c0t4d0s2 /cdrom/cdrom0 # cd /cdrom/cdrom0/solaris # ./update.sh

2. Enter “y” and press ENTER to perform the upgrade installation.

---------------------------------------------------------- Interstage Shunsaku Data Manager Enterprise Edition 7.0.1 All Rights Reserved, Copyright(c) FUJITSU LIMITED 2003-2006 ---------------------------------------------------------- This program will install "Interstage Shunsaku Data Manager Enterprise Edition" on your system. The following products are installed. Product : Interstage Shunsaku Data Manager Enterprise Edition Version : 6.0 Function : director conductor API Do you want to proceed with the installation? (default:n) [y,n]

5-3


The installation process will start.

Deletion of packages has started. Removal of <FJSVshndr> was successful. : Deletion of packages has ended. Installation of packages has started. Installation of <FJSVshnsk> was successful. : Installation of packages has ended.

If there is a processing error, the following message will be displayed, and the installation process will be terminated.

Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

If installation was successful, a message will be displayed indicating that the installation process has completed.

Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was successful.

Upgrade Installation on Search Servers Environment resources are inherited when the upgrade is installed.

Note

• Upgrade installations must be performed by a superuser.

• Stop Shunsaku before installing the upgrade.

1. Start the upgrade installation script (update.sh).

# mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/redhat # ./update.sh

2. Enter “y” and press ENTER to perform the upgrade installation.

---------------------------------------------------------- Interstage Shunsaku Data Manager Enterprise Edition V7.0L11 All Rights Reserved, Copyright(c) FUJITSU LIMITED 2003-2006 ----------------------------------------------------------

5-4


This program will install "Interstage Shunsaku Data Manager Enterprise Edition" on your system. The following products are installed. Product : Interstage Shunsaku Data Manager Enterprise Edition Version : V7.0L10 Function : searcher Do you want to proceed with the installation? (default:n) [y,n]

The installation process will start.

Deletion of packages has started. Removal of <FJSVshnap> was successful. : Deletion of packages has ended. Installation of packages has started. Installation of <FJSVshnsk> was successful. : Installation of packages has ended.

If there is a processing error, the following message will be displayed, and the installation process terminates.

Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated. If installation was successful, a message displays indicating that the installation process has completed.

Installation of "Interstage Shunsaku Data Manager Enterprise Edition" was successful.

Migration Operations Refer to Appendix A, Migration Operations for details of the tasks required to migrate from 6.0.

5-5


Upgrade Installation on Application Servers This section describes installation of Shunsaku API upgrades on Application Servers.

Under Solaris

The upgrade installation procedure for Shunsaku APIs on Solaris application servers is the same as the procedure described in Upgrade Installation on Director Servers.

Under Windows

This section describes the procedure for upgrading Shunsaku APIs on Windows Application Servers.

Note

• Upgrade installations must be performed by users that belong to the Administrators group.

• Stop all applications before installing the upgrade.


− Insert the CD-ROM. Insert the Shunsaku CD-ROM in the disk drive.

− Execute the install program. When the CD-ROM is inserted, the install menu is displayed. Click the Install button. If the install menu does not display, run MENU.EXE from the CD-ROM.

2. In the Welcome dialog, click the Next button.

3. In the Installation Confirmation dialog, click the Install button.

Note

− Do not click the Cancel button. If the Cancel button is clicked after the installation has started, the upgrade will need to be uninstalled and then installed again.

4. Click the Finish button.

5. When the Restarting Windows dialog is displayed, select Yes, I want to restart my computer now, and click the OK button.

Under Linux

The upgrade installation procedure for Shunsaku APIs on Linux Application Servers is the same as the procedure described in Upgrade Installation on Search Servers

5-6

Differences between Shunsaku 6.0 and 7.0

Differences between Shunsaku 6.0 and 7.0 As the result of functional enhancements under 7.0, the following functions differ from 6.0:

• System Start and Stop

• Search Expressions

• Monitoring

The following sections describe how to make these functions operate as in 6.0.

System Start and Stop The shunsysstart command and the shunsysstop command perform batched start and stop of all processes on the servers required for Shunsaku operation. Therefore, start and stop commands need not be executed separately for each of the processes. Refer to the Command Reference for details.

To start or stop an individual process as done under 6.0, set the SystemName parameter in the environment file of the targeted process to match the 'Shunsaku system name' that was determined when performing the migration tasks. Refer to Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details.

Search Expressions Enhancements to search expression formats that can be specified in applications enable greater freedom in searches. This has resulted in differences in the method of specifying escape characters in search expressions and in the operation of ellipse searches. Refer to Appendix B, Formats of Search Expressions, Return Expressions and Sort Expressions of the Application Development Guide.

To specify escape characters and use ellipse searches in the same way as under 6.0, specify "1: Compatible format queries used" as the ExtendedQuery parameter in the system environment file or the director environment file. Refer to Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details.

Monitoring Enhancements to the monitoring command functions mean that more information can be monitored. As a result, the display format when command options are omitted has changed. Refer to the Command Reference for details.

To display information in the same format as in 6.0, specify "1: 6.0 output format" for the MonitoringStyle parameter in the system environment file. Refer to Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details.

5-7


5-8

Chapter 6 Uninstall

This chapter describes the procedures used to uninstall Shunsaku.

• Uninstall on Search Servers

• Uninstall on Sort Servers

• Uninstall on Director Servers

• Uninstall for Application Servers

6-1

Chapter 6: Uninstall

Uninstall on Search Servers This section describes the procedure used to uninstall Shunsaku from search servers.

Shunsaku Uninstallation The procedure used to uninstall Shunsaku is described below.

Note

• Uninstallation must be performed by a superuser.

• Stop Shunsaku before uninstalling. Refer to Stopping Shunsaku in the Operator's Guide (Advanced) for more information on how to stop Shunsaku.

• Stop Shunsaku applications before uninstalling.

• When Shunsaku is uninstalled, everything in the Shunsaku installation directory will be deleted. Back up any required files using the cp command or some other method.

1. Start the uninstallation script (uninstall.sh).

# mount -t iso9660 -o ro /dev/cdrom /mnt/cdrom # cd /mnt/cdrom/redhat # ./uninstall.sh

2. A message will be displayed indicating which packages are currently installed, as shown below.

Enter “y” and press ENTER to remove these packages.

This program will remove "Interstage Shunsaku Data Manager Enterprise Edition" on your system. The following packages are installed. FJSVshnsy : Is removal started?(default y) [y,n]

If there is a processing error, the following message will be displayed, and the removal process will be terminated.

Removal of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

6-2

Uninstall on Search Servers

If the uninstallation was successful, a message will be displayed indicating that the removal process has completed.

Removal of "Interstage Shunsaku Data Manager Enterprise Edition" is ended.

3. Delete the port numbers that have been defined in the following "services" file on the server:

/etc/services

4. The uninstallation script does not change IPC resource settings. Review the IPC resource

settings and change them if necessary.

Refer to IPC Resource Settings under Setting up Search Servers in Chapter 3, Shunsaku System Installation and Setup for information on IPC resource settings.

6-3


Uninstall on Sort Servers This section describes the procedure used to uninstall Shunsaku from sort servers.

Shunsaku Uninstallation The procedure used to uninstall Shunsaku is described below.

Note

• Uninstallation must be performed by superusers.

• Stop Shunsaku before uninstalling. Refer to Stopping Shunsaku in the Operator's Guide (Advanced) for more information on how to stop Shunsaku.

• Stop Shunsaku applications before uninstalling.

• When Shunsaku is uninstalled, everything in the Shunsaku installation directory will be deleted. Back up any required files using the cp command or some other method.

1. Start the uninstallation script (uninstall.sh).

(The "/dev/dsk/c0t4d0s2" device name will differ depending on the environment used.)

# mount -F hsfs -o ro /dev/dsk/c0t4d0s2 /cdrom/cdrom0 # cd /cdrom/cdrom0/solaris # ./uninstall.sh

2. A message will be displayed indicating which packages are currently installed, as shown below.

Enter “y” and press ENTER to remove these packages.

This program will remove "Interstage Shunsaku Data Manager Enterprise Edition" on your system. The following packages are installed. FJSVshnsy : Is removal started?(default y) [y,n]

If there is a processing error, the following message will be displayed, and the removal process will be terminated.

Removal of "Interstage Shunsaku Data Manager Enterprise Edition" was terminated.

6-4

Uninstall on Sort Servers

If the uninstallation was successful, a message will be displayed indicating that the removal process has completed.

Removal of "Interstage Shunsaku Data Manager Enterprise Edition" is ended.

3. Delete the port numbers that have been defined in the following "services" file on the server:

/etc/services

4. The uninstallation script does not change IPC resource settings. Review the IPC resource

settings and change them if necessary.

Refer to IPC Resource Settings under Setup for Systems with Additional Director Servers in Chapter 3, Shunsaku System Installation and Setup for information on IPC resource settings.

6-5


Uninstall on Director Servers This section describes the procedures used to uninstall Shunsaku on director servers.

Shunsaku Uninstallation The procedure used to uninstall Shunsaku on director servers is the same as the procedure described in Uninstall on Sort Servers.

6-6

Uninstall for Application Servers

Uninstall for Application Servers This section describes the procedure to uninstall Shunsaku APIs from Application Servers. The procedure differs depending on the Application Server operating system:

• Under Solaris

• Under Windows

• Under Linux

Under Solaris

The Shunsaku API uninstall procedure for a Solaris Application Server is the same as the procedure described in Uninstall on Sort Servers.

Under Windows

This section describes the Shunsaku API uninstall procedure for a Windows Application Server.

Note

• Only users belonging to the Administrators group can perform the uninstall procedure.

• Stop all applications before uninstalling Shunsaku.

• When uninstall is executed, all files under the Shunsaku installation destination folder are deleted. If any of these files need to be saved, use a copy command to save them before performing the uninstall procedure.

• Do not click the Cancel button during uninstallation.


− Display the control panel. From the Start menu, select Settings, then click Control Panel.

− Execute deletion. Under Windows 2000: In the Control panel, double-click the Add/Remove Applications icon. Select Interstage Shunsaku Data Manager from the list box, then click the Add/Remove button.

Under Windows Server 2003 In the Control panel, double-click the Add/Remove Programs icon. Select Interstage Shunsaku Data Manager from the list box, then click the Add/Remove button.

2. In the ‘Welcome’ dialog, click the Next button.

3. A confirmation message is displayed. Click the OK button to start the uninstall process.

6-7


4. When the uninstall process has completed, click the Finish button.

5. In the Restarting Windows dialog, select Yes, I want to restart my computer now, then click the OK button.

Under Linux

The Shunsaku API uninstall procedure for a Linux Application Server is the same as the procedure described in Uninstall on Sort Servers.

6-8

Appendix A Migration Operations

This appendix describes the procedures for migrating a 6.0 system to a 7.0 system.

• Migration Procedures

• Director Server Migration

• Distributing the System Environment File

• Migrating Search Servers

This chapter uses the following version notations.

Version notation Product/version

7.x Shunsaku 7.0 Solaris Interstage Shunsaku Data Manager Enterprise Edition 7.0.1

Shunsaku 6.2 Solaris Interstage Shunsaku Data Manager Enterprise Edition 6.2 6.x

Shunsaku 6.0 Solaris Interstage Shunsaku Data Manager Enterprise Edition 6.0

A-1

Appendix A: Migration Operations

Migration Procedures Figure A-1 shows the migration procedure.

Figure A-1 Migration Procedures

Repeat the tasks shown above if there are multiple systems on the same director server.

A-2

Director Server Migration

Director Server Migration This section describes the migration procedures for a director server.

Resources to be Migrated during Director Server Migration The director server resources and operating system resources requiring migration are shown below. The director data file can continue to be used as is.

• Environment files

• Services files

• Kernel configuration file

Director Server Migration Procedures Figure A-2 shows the task flow for director server migration.

Figure A-2 Task Flow for Director Server Migration

The following sections provide details of the migration procedures.

A-3


Checking the System Process Configuration Check the process structure and information for the conductor, director, searcher and sorter (if migrating from Shunsaku 6.2) processes used in the current system.

Figure A-3 shows the procedure used to check the process structure of the system.

Figure A-3 Procedure for Checking System Process Structure

The following sections describe the procedures used to check the system operating format and system information.

Checking the System Operating Format Check that the operating format of the current system is one of the following:

• Conductor and sorter used

• Conductor used, but sorter not used

• Conductor not used

Checking the Conductor Information If a conductor is used in the current system, determine which conductor is used and check the conductor identifier.

If the current system does not use a conductor, set a conductor identifier to create a new conductor. Set an alphanumeric character string of up to 8 bytes as the conductor identifier.

Checking the Sorter Information If a sorter is used in the current system, determine which sorter is used and check the sorter identifier.

If the current system does not use a sorter, set a sorter identifier to create a new sorter. Set a single-byte space alphanumeric character string of up to 8 bytes as the sorter identifier.

A-4


Checking the Director Information Determine which director is used in the current system and check the director identifier.

Checking the Searcher Information Determine which searcher is used in the current system and check the searcher identifier, the host name or IP address of the server allocated to the searcher, and the director identifier of the director that connects to the searcher.

Determining the Shunsaku System Name Under Shunsaku, the system operates with an assigned system name. This name is called the Shunsaku system name. Specify a single-byte space alphanumeric character string of up to 8 bytes as the Shunsaku system name.

Creating and Editing Environment Files Table A-1 lists the storage locations of the environment files created or edited when the director server is migrated.

Table A-1 Environment File Storage Locations

Type Storage location

System environment file /etc/opt/FJSVshnsk/etc/system/Shunsaku-system-name.cfg

Conductor environment file /etc/opt/FJSVshnsk/etc/conductor/conductor-identifier.cfg

Sorter environment file /etc/opt/FJSVshnsk/etc/sorter/sorter-identifier.cfg

Director environment file /etc/opt/FJSVshnsk/etc/director/director-identifier.cfg

A-5


Figure A-4 shows the task flow for creating and editing environment files.

Figure A-4 Task flow for Creating and Editing Environment Files

The following sections describe the procedure for migrating the various environment files.

Creating the System Environment File Create a new system environment file. Table A-2 shows the execution parameters of the system environment file.

Refer to Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details of the system environment file.

A-6


Table A-2 System Environment File List

Execution parameter

Explanation Mandatory? Items to be entered Notes

Conductor conductor server information

Mandatory - Conductor identifier

- Host name or IP address allocated for the conductor

- Port number for receiving requests

-

Sorter sorter server information

Mandatory - Sorter identifier

- Host name or IP address allocated for the sorter

- Port number for receiving sort requests from the conductor

-

Director director server information

Mandatory - Director identifier

- Host name or IP address allocated for the director

- Port number for issuing search requests to searchers

- Port number for issuing update requests to searchers

- Port number for receiving requests

- Director number

-

Searcher searcher server information

Mandatory - Searcher identifier

- Host name or IP address allocated for the searcher

- Port number for receiving requests from the director

- Director identifier of the director to be connected to

-

A-7


Execution parameter

Explanation Mandatory? Items to be entered Notes

CharacterCode Character encoding for lookup data

Optional - UTF-8

- SHIFT-JIS

- EUC

- GB2312

- big5

- KSC5601 Select one of the above.

Default: UTF-8

ANKmix Distinguishes between upper and lower-case alphanumeric characters.

Optional Select either: 0: Distinguish 1: Do not distinguish

Default: 0

KNJmix Distinguishes between upper and lower-case multi-byte alphabetic characters.

Optional Select either: 0: Distinguish 1: Do not distinguish

Default: 0

SkipChar Skip character (characters that will not be searched)

Optional Enclose characters that are to be excluded from searches in double quotation marks.

If omitted, all character strings are subject to searches.

ExtendedQuery Query format Optional Select either: 0: Compatible format queries not used 1: Compatible format queries used

Default: 0

SeparateChar Delimiter character

Optional Enclose the characters to be used as the delimiter in double quotation marks.

If omitted, the characters in Default Delimiters are used as the delimiter.

MonitoringStyle Output format for monitoring.

Optional Select either 0: New output format 1: 6.0 output format

Default: 0

The procedures for setting the various execution parameters are described below.

A-8


Conductor • Conductor identifier

Set the conductor identifier that was checked or determined as described in Checking the Conductor Information.

• Host name or IP address

Set the host name or IP address of the director server.


Determine the port number used to receive requests from applications, as shown in the following table:

Operating format of current system Method for determining the port number

Conductor used Set the port number that is set as the MySearchPort parameter of the conductor environment file.

Conductor not used Set a port number that is not being used by the director server.

Sorter • Sorter identifier

Set the sorter identifier that was checked or determined as described in Checking the Sorter Information.



• Port number for receiving requests from the conductor

Determine the port number used to receive requests from the conductor, as shown in the following table:

Operating format of current system Method for determining the port number

Sorter used Set the port number that is set as the SorterInfo parameter in the conductor environment file.

Sorter not used Set a port number that is not being used by the director server.

Director Set the number of directors and the director parameters used in the current system, determined as described in Checking the Director Information, as follows:

• Director identifier

Set the director identifier confirmed as described in Checking the Director Information.



• Port number for issuing search requests to searchersSearch port number for the searcher

Set the SearcherSearchPort value from the director environment file.

A-9


• Port number for issuing update requests to searchersUpdate port number for the searcher

Set the SearcherEntryPort value from the director environment file.


Set the MySearchPort value from the director environment file.

• Director number

Determine the director number as shown in the following table:

Operating format of current system Method for determining the director number

Conductor used The director number entered for Directorinfo in the conductor environment file

Conductor not used Since there is one director used for operations in the current system, set 10.

Searcher Set the number of searchers and the searcher parameters used in the current system, determined as described in Checking the Searcher Information, as follows:

• Searcher identifier


Set the host name or IP address of the server where the searcher is installed.

• Port number for receiving requests from the director

Set the MyPort value in the searcher environment file.

• Director identifier of the director to be connected to

CharacterCode Determine the CharacterCode value as shown in the following table:

Operating format of current system Method for determining the CharacterCode

Conductor used Set the same value as the value specified in the CharacterCode parameter of the conductor environment file. If the CharacterCode parameter was omitted, set the value that was specified in the CharacterCode parameter of the director environment file. If both were omitted, also omit it here.

Conductor not used Set the same value as the value specified in the CharacterCode parameter of the conductor environment file. If the CharacterCode parameter was omitted, also omit it here.

ANKmix Omit this specification because the ANKmix parameter in the director environment file is set separately for each director.

A-10


KNJmix Omit this specification because the KNJmix parameter in the director environment file is set separately for each director.

Note

• This parameter is valid with Japanese character encodings.

To use Japanese character encoding, specify "UTF-8", "SHIFT-JIS" or "EUC" for the CharacterCode parameter.

SkipChar Omit this specification because the SkipChar parameter in the director environment file is set separately for each director.

ExtendedQuery Specify the value indicating whether or not compatible format queries are used, as shown in the table below. If this parameter is omitted, 0 is assumed.

Specification Method for determining ExtendedQuery

0 Compatible format queries not used

1 Compatible format queries used

Refer to Appendix B, Formats of Search Expressions, Return Expressions and Sort Expressions of the Application Development Guide for details of compatible formats.

SeparateChar This parameter is valid when "Compatible format queries not used" is specified for the ExtendedQuery specification.

Multiple characters can be specified in the SeparateChar parameter. If so, separate each character string with a comma (,).

For the SeparateChar parameter, specify new line, horizontal tab, and ASCII characters other than control characters.

When a character shown below is specified for the SeparateChar parameter, add an escape character to indicate that it is a SeparateChar parameter. The escape character is "\".

Delimiter character Specification method

Space \s

Linefeed \n

Horizontal tab \t

Comma \,

Double quote \"

Backslash \\

If this parameter is omitted, the following 'Delimiters' are assumed:

A-11


Default Delimiters

\t \n \s ! \" #

$ % & ' ( )

* + \, - . /

: ; < = > ?

@ [ \\ ] ^ _

` { | } ~

MonitoringStyle From the table below, determine the output format used for monitoring. If this parameter is omitted, 0 is assumed.

Specification Output format

0 If none of the options w, p, i or c is specified in the shuncstate, shunostate, shundstate, or shunsstate commands, the w option is assumed and information is displayed in the new output format.

1 If none of the options w, p, i or c is specified in the shuncstate, shunostate, shundstate, or shunsstate commands, information is displayed in the 6.0 output format.

Creating and Editing the Conductor Environment File If the conductor is not used in the current system, create a new conductor environment file. If the conductor is used, edit the existing conductor environment file.

Refer to Conductor Environment Files in Appendix A, Execution Parameters in the Environment Files of the Operator's Guide (Advanced) for details of the conductor environment file.

Creating a Conductor Environment File Copy from the conductor environment file sample shown below to create a new conductor environment file.

/etc/opt/FJSVshnsk/etc/conductor/conductor.cfg-sample

Set the name of the edited conductor environment file to "conductor identifier.cfg" and store it in the same directory as the sample file.

Editing the Conductor Environment File Edit the existing conductor environment file as shown in the following table:

Execution parameters in the 6.0 system

Omission in the 6.0 system Editing tasks at time of migration

DirectorInfo Mandatory Delete

LogFileFolder Optional None

LogFileSize Optional None

CoreFileFolder Mandatory None

A-12




AnsMax (*1) Optional None when migrating from Shunsaku 6.2. Edit as required when migrating from Shunsaku 6.0.

MySearchPort Mandatory Delete

CharacterCode (*1) Optional If specified, delete

StartPoint Optional None

WaitTimer Optional If set, set that value in the WaitTimer parameter of the API environment file(*2). If not set, set 3600 in the WaitTimer parameter of the API environment file. Do not change the conductor environment file.

MaxConnection Optional None

MemKey Mandatory Delete

SorterInfo (*1) Optional If specified, delete

*1 These parameters are present only under Shunsaku 6.2.

*2 Refer to the following sections for more information on the API environment file:

− Execution Parameters in Environment Files in the Operator’s Guide (Advanced)

− Setting Up Environment Files in the Application Development Guide

If the V6.0 Start and Stop commands are to be used, set the Shunsaku system name determined by the SystemName parameter.

Set "_LAST_" as the InsertPoint parameter.

Edit the other parameters if required.

Creating and Editing the Sorter Environment File If the sorter is not used in the current system, create a new sorter environment file. If the sorter is used, edit the existing sorter environment file.

Refer to Sorter Environment Files in Appendix A, Execution Parameters in Environment Files of the Operator's Guide (Advanced) for details of the sorter environment file.

Creating a Sorter Environment File Copy from the environment file sample shown below to create a new sorter environment file.

/etc/opt/FJSVshnsk/etc/sorter/sorter.cfg-sample

Set the name of the edited sorter environment file to "sorter identifier.cfg" and store it in the same directory as the sample file.

A-13


Editing the Sorter Environment File Edit the existing sorter environment file as shown in the following table:



MySortPort Mandatory Delete

MultiMax Optional None





If the 6.0 Start and Stop commands are to be used, set the Shunsaku system name determined by the SystemName parameter.


Editing the Director Environment Files Edit the director environment files of all of the directors used in the system, (determined as described in Checking the Director Information), as shown in the table below.

Refer to Director Environment Files in Appendix A, Execution Parameters in Files of the Operator's Guide (Advanced) for details of the director environment file.



DataFileFolder Mandatory None

WorkFolder (*1) Optional If specified, delete




AnsMax Optional None

MultiMax Optional None

SearcherCnt Mandatory Delete

DataRevSize Optional None

MySearchPort Mandatory Delete

MyUpdatePort (*1) Optional If specified, delete

SearcherSearchPort Mandatory Delete

SearcherEntryPort Mandatory Delete

CharacterCode Optional If specified, delete

SearcherWTimer Optional None


A-14




ANKmix Optional None

KNJmix Optional None

SkipChar Optional None

SearcherDataEquality (*1)

Optional None

*1 These parameters are present only under Shunsaku 6.2.

If the 6.0 start and stop commands are to be used, set the Shunsaku system name determined by the SystemName parameter.


Defining Port Numbers When a new conductor is being created, specify the port numbers in the director server file shown below.

When a new sorter is being created, specify the port numbers in the sort server file shown below. /etc/services



Service Name Specify a character string that can be easily associated with the conductor or the sorter.

Port Number When creating a new conductor, define the port number specified in the Conductor parameter of the system environment file.

When creating a new sorter, define the port number specified in the Sorter parameter of the system environment file.

Protocol Specify tcp.

If the MyUpdatePort parameter was deleted as described in Editing the Director Environment Files, delete the specified port number from the above file.

A-15


Setting up the Operating System This section explains the operating system settings.

IPC Resource Settings If new conductors or sorters are created, the kernel configuration file (the "/etc/system" file) must be edited.

Resource Kernel parameter name

Newly created process Change during migration

conductor and sorter Add 2 shminfo_shmmni

sorter Add 1

conductor and sorter Add 2

Shared memory

shminfo_shmseg

sorter Add 1

conductorand sorter Add 20 seminfo_semmni

sorter Add 10

conductor and sorter Add 20 seminfo_semmns

sorter Add 10

conductor and sorter Add 20

Semaphore

seminfo_semmnu

sorter Add 10

Note

• For Solaris 9 and later, the 'shminfo_shmseg' parameter has been discontinued and is not valid, so there is no need to set this parameter.

• Restart the system after editing the kernel.

A-16

Distributing the System Environment File

Distributing the System Environment File Distribute the system environment file that was created when the director server was migrated to the search server that is to be migrated.

Create the following directory on the search server and store the distributed system environment file in this directory:

/etc/opt/FJSVshnsk/etc/system/

A-17


Migrating Search Servers This section describes the migration procedures for search servers.

Resources to be Migrated during Search Server Migration The search server resources and operating system resources requiring migration are shown below.

• Searcher environment files

Search Server Migration Procedures Figure A-5 shows the procedures used to migrate a search server.

Figure A-5 Search Server Migration Procedures

The following sections describe details of the migration procedures.

Checking the Searchers to be Migrated Check the searcher identifiers of the searchers used by the system. Determine the searchers that have the same search server host name as the host names specified in the Searcher parameter of the system environment file distributed to the search servers, and check the searcher identifiers.

Editing the Searcher Environment Files Edit the searcher environment files of all of the searchers used by the system, determined as described in Checking the Searchers to be Migrated.

Type Storage location

Searcher environment file /etc/opt/FJSVshnsk/etc/searcher/searcher identifier.cfg

Edit the searcher environment file for all of the searchers used by the system that were determined in Checking the Searcher Information, as follows.

Refer to Searcher Environment Files in the Operator's Guide (Advanced) for more information on the searcher environment file.

A-18

Migrating Search Servers

Execution parameter for 6.x Can parameter be omitted in 6.x? Change during migration

MyPort No Delete

DirSvrName No Delete

DirectorSearchPort No Delete

DirectorEntryPort No Delete

MemKey No Delete

LogFileFolder Yes None

LogFileSize Yes None

CoreFileFolder No None

To use the start and stop commands from 6.x, set the Shunsaku system name in the SystemName parameter.

Edit the other parameters if necessary.

A-19


A-20

Appendix B How to Set Up IPC Resources

This appendix describes how to set up IPC resources.

Select either of the following methods for setting up IPC resources:

• Modifying the Kernel Configuration File (/etc/system)

• Resource Management

IPC resource setup via resource management is supported in Solaris 10 and later.

B-1

Appendix B: How to Set Up IPC Resources

Modifying the Kernel Configuration File (/etc/system)

Edit the kernel configuration file (/etc/system), and change the project parameters applied to the Shunsaku project at startup. Restart the system after editing the file.

Refer to the Solaris manuals for more information on how to change the parameter values.

Entry Format set shmsys:shminfo_shmmax = 8388608 set shmsys:shminfo_shmmni = 103 set shmsys:shminfo_shmseg = 10 set semsys:seminfo_semmni = 40 set semsys:seminfo_semmns = 90 set semsys:seminfo_semmnu = 60

B-2

Resource Management

Resource Management Use the following procedure to change parameter values:

1. Stop Shunsaku.

2. Change the required project parameters:

− Change the resource management project parameters for starting Shunsaku.

− Change other parameters as required.

Example

Setting the "project.max-sem-ids" parameter for the "user.root" project # projmod -s -K 'project.max-sem-ids=(privileged,158,deny)' user.root

3. Update the changed parameter values to the system.

Example

For the "user.root" project # newtask -p user.root -c $$

4. Start Shunsaku.

Note

• Refer to Chapter 3, Operation, in the Operator's Guide (Advanced) for information on starting and stopping Shunsaku.

• Refer to the Solaris manuals for more information on resource management.

B-3

Appendix B: How to Set Up IPC Resources

B-4

Interstage Shunsaku Data Manager Installation Guide

Documents

Transcript of Interstage Shunsaku Data Manager Installation Guide