lix installation 1 - fujitsu...installation scenarios 1-3 functions that can be used enterprise...

1-1

Chapter 1 Installation (Server Package)

This chapter explains how to install the Server Package.

Chapter 1: Installation (Server Package)

1-2

Installation Scenarios This section explains the two types of Interstage Application Server Package that can be installed:

• Application Server

Select this to install Interstage Application Server server functions.

This option can also be selected to install the Managed Server functions.

For details on Managed Server operations, refer to the Interstage Application Server Operator’s Guide.

• Admin Server

Select this to install Interstage Application Server Admin Server functions.

Use it to execute operations when managing more than one server.

For details on Admin Server operations, refer to the Interstage Application Server Operator’s Guide.

Note

To run the Admin Server and Application Server functions on the same server, first install the Application Server functions. Next, use the isaddadminfunc command to add the Admin Server functions. For details of the isaddadminfunc command, refer to the Reference Manual (Command Edition).

The Application Server function types that can be installed are as follows:

• Typical installation

Select this to use the standard functions following a simple installation.

• Custom installation

Select this to install the minimum set of functions, or to use a version of JDK/JRE other than JDK 1.4.

When the installation is executed, the environment required for using Interstage is set up automatically. After the installation is complete, the Interstage Management Console can be used for simple operation.

Installation Scenarios

1-3

Functions that can be used

Enterprise Edition: Application Server If the Typical installation is selected, the functions shown as 'This cannot be changed' and 'Selected' in Table 1-1 are installed. If the Custom installation is selected, it is possible to select the functions that are installed.

Table 1-1 Functions available in a Typical Enterprise Edition installation Function Default status

Interstage Application Server basic functions This cannot be changed

J2EE Common Resource

- Servlet Service (Tomcat 4.1-based servlet)

- Interstage EJB Service

- Interstage JMS

Selected

Web Server (Interstage HTTP Server) Selected

Interstage Management Console Selected

Secure Communication Service Selected

Database Linkage Service Selected

EventService Selected Asynchronous communication

MessageQueueDirector Not selected

SOAP Service Selected Web Services

ebXML Message Service Not selected

Optional features

- Portable-ORB

- CORBA Service Development Tool

- Enabler Server

Selected

Interstage Single Sign-on

- Interstage Single Sign-on Business server

- Interstage Single Sign-on Authentication server

- Interstage Single Sign-on Repository server

Not selected

UDDI Client Not selected

Smart Repository Selected

Load measuring agent Not selected

Application server compatible functions

- Web Server (InfoProvider Pro)

- Tomcat 3.1 servlet service

Not selected


1-4

Function Default status

Sample Application Selected

JDK/JRE 1.3 Not selected JDK/JRE

JDK/JRE 1.4 Selected

Framework Selected

Portal component Selected

Apworks Server Runtime Not selected

Enterprise Edition: Admin Server In Enterprise Edition, the following functions are installed if Admin Server is selected.

• JDK 1.4

• Web Server (Interstage HTTP Server)

• Interstage Management Console

• Secure Communication Service

• Fujitsu XML Processor

• Smart Repository

• Enabler Server

Plus: Application Server If the Typical installation is selected, the functions shown as 'This cannot be changed' and 'Selected' in Table 1-2 are installed. If the Custom installation is selected, it is possible to select the functions that are installed.

Table 1-2 Functions available in a Typical Plus Edition installation Function Default status


Servlet Service (Tomcat 4.1-based servlet) This cannot be changed

Web Server (Interstage HTTP Server) This cannot be changed

Application server compatible functions

- Web Server (InfoProvider Pro)

- Tomcat 3.1 servlet service

Not selected

Interstage Single Sign-on

- Interstage Single Sign-on Business server

- Interstage Single Sign-on Authentication server

- Interstage Single Sign-on Repository server

Not selected

Installation Scenarios

1-5

Function Default status

Sample Application Selected

JDK/JRE 1.3 Not selected JDK/JRE

JDK/JRE 1.4 This cannot be changed

Framework Selected

Portal component Selected

Apworks Server Runtime Not selected

Optional feature

- Enabler Server

This cannot be changed

Smart Repository This cannot be changed

Plus: Admin Server In Plus Edition, the following functions are installed if Admin Server is selected.

• Interstage Application Server basic functions

• Web Server (Interstage HTTP Server)

• JDK 1.4

• Interstage Management Console

• Secure Communication Service


• Smart Repository

• Enabler Server


1-6

System Requirements This section explains the system requirements.

OS • Red Hat Enterprise Linux AS (v.3)

• Red Hat Enterprise Linux ES (v.3)

When using the Interstage Application Server, the following patches must be applied.

• Update 2

Disk Space

Table 1-3 Disk Space Requirements Number File system Mount point Disk space

(Unit: Mbytes) Remarks

1 opt file system /opt 900

2 etc file system /etc/opt 25

3 ver file system /var/opt 5

Note

To run Interstage, the following package groups and optional packages in the OS need to be installed.

Table 1-4 Package Requirements Item Package Group Select / Do not select

X Window System Select(tkinter)

GNOME Desktop Environment Select

Desktops

KDE Desktop Environment

Editors Select

Engineering and Scientific

Graphical Internet Select

Text-based Internet

Office/Productivity

Sound and Video

Applications

Authoring and Publishing

System Requirements

1-7

Item Package Group Select / Do not select

Graphics

Games and Entertainment

Server Configuration Tools Select

Web Server Select

Mail Server Select

Windows File Server Select

DNS Name Server Select

FTP Server Select

SQL Database

MySQL Database

News Server

Network Servers Select (openldap-servers , quagga , radvd)

Servers

Legacy Network Server Select (rusers-server , telnet-server)

Development Tools Select (Ruby)

Kernel Development Select

X Software Development

GNOME Software Development Select

KDE Software Development

Development

Legacy Software Development Select

Administration Tools

System Tools Select (net-snmp-utils , sysstat)

System

Printing Support

Everything Other

Minimum

To run the Interstage Application Server, the following system parameter file needs to be edited.

Edit the '/etc/sysctl.conf' file using the 'vi' command according to the following procedure: # vi /etc/sysctl.conf


1-8

The edit contents are as follows.

Before editing: # Controls IP packet forwarding net.ipv4.ip_forward = 0 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 # Controls the System Request debugging functionality of the kernel kernel.sysrq = 0 # Controls whether core dumps will append the PID to the core filename. # Useful for debugging multi-threaded applications. kernel.core_uses_pid = 1

After editing: # Disables packet forwarding # Controls IP packet forwarding net.ipv4.ip_forward = 0 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 # Controls the System Request debugging functionality of the kernel kernel.sysrq = 1･････････････････････････ Modify # Controls whether core dumps will append the PID to the core filename. # Useful for debugging multi-threaded applications. kernel.core_uses_pid = 1 kernel.shmmax = 4000000000 ････････････ Add kernel.sem = 1100 35406 200 800 ･･････････ Add kernel.msgmax = 32768 ･････････････････ Add kernel.msgmni = 8199 ･･････････････････ Add kernel.threads-max = 8192 ･･････････････ Add kernel.shmmni = 4315 ･･････････････････ Add kernel.msgmnb = 4194304････････････････ Add fs.file-max = 65536 ･･･････････････････ Add net.ipv4.ip_local_port_range = 1024 65000･･ Add

Pre-Installation Preparations

1-9

Pre-Installation Preparations Essential tasks before beginning installation Before beginning installation of the Interstage Application Server Server Package:

• Ensure that all of the relevant items described in the System Requirements table 1-3 are satisfied in the target environment.

• Close any applications that are running.

• Check the system environment.

Check whether an earlier version or level of this software is installed. If any packages are output, this software is already installed and the existing software package must be deleted.

• If the hostname has not been configured correctly for your operating system, the Fujitsu Enabler (FJSVena) installation will fail. Avoid the installation failure by ensuring that the hostname is configured correctly for your system before the installation.

Perform the following procedures to confirm and set the hostname.

1) Confirm the hostname by executing hostname. # hostname <RETURN> localhost.localdomain

2) If 'localhost.localdomain' is output, it means the hostname has not been configured correctly. Execute 'hostname FQDN'.

ex) # hostname host01.fujitsu.com <RETURN>


1-10

Install Procedure The following methods are available for installing the Interstage Application Server Server Package. Select the appropriate installation method for your system.

• Installation using GUI-installer

This is an easy method of installing Interstage Application Server using a GUI-installer.

To use the GUI-installer, the following system environment is required:

− X terminal (*1)

− Disk space of /tmp : 150 MB

(*1) If the message text overflows on the GUI screen, set up a suitable font size or screen resolution.

It is also possible to use the GUI-installer on a Windows system to output the installation shell scripts. This is useful for installing and setting up this product with the GUI-installer even if there is no X terminal. Refer to Generating Installation Scripts

• Installation using Installation Shell Script

This method is for installation on a system where there is no X terminal or for installation on multiple machines.

Installation using GUI-installer Installation of the Interstage Application Server Server Package must be performed by a superuser.

To install the Interstage Application Server Server Package using the GUI-installer, execute isinstaller.

Note

• The isinstaller can be performed only if this product is not installed.

• When executing the GUI-installer, the LANG environment variable needs to be set as 'LANG=C'.

• Additionally, characters may not display on the GUI depending on the font size and screen resolution. In this case, adjust the font size and screen resolution.

1) Execute isinstaller To execute the GUI-installer, insert the first Server Package CD in the CD drive, mount the CD and execute the isinstaller on an X terminal. # mount /dev/<device-name> /mnt/cdrom <RETURN> # /mnt/cdrom/isinstaller <RETURN>

Click Install to launch the installation wizard. The 'Select Server Type' screen is displayed.

Install Procedure

1-11

Selecting the Server Type

First, select the server type.

If Application Server is selected, select typical or custom.

Performing a Typical install

Select Typical as the type of installation to be performed and click Next. The 'Confirm Setup Information' screen is displayed.

On this screen, check the displayed settings. Select Modify or Do not modify depending on whether or not the settings require modification and click Next.

If Modify was selected, the 'Modify Settings' screen is displayed. Check or correct the settings and click Next.

On the Confirm Setup Information page, check the settings and click Next. A message to insert the next CD is displayed. Insert the appropriate CD and click Yes. The installation starts.

When the installation process is complete, the Result of Package installation page is displayed.

Performing a Custom install

Select 'Custom' as the type of installation to be performed and click Next. The Choose components to install page is displayed.

Specify the facilities you want to install and the settings for each of the facilities and click Next.

On the Confirm Setup Information page, check the settings and click Next. A message to insert the next CD is displayed. Insert the appropriate CD and click Yes. Installation starts.

When the installation process is complete, the 'Result of Package installation' screen is displayed.

2) Output Log or Scripts To output the installation log or shell scripts, click Next. On the 'Output Install Log and Shell Scripts' screen, select the required options and the destination directory and click Finish.

3) System Reboot To exit the GUI-installer, click Exit on the initial installation wizard.

When the GUI-installer ends, reboot the system. # cd / <RETURN> # shutdown -r now <RETURN>


1-12

Generating Installation Scripts The GUI-installer can be run on a Windows system and make the shell scripts install or uninstall the Interstage Application Server Server Package for Linux.

To execute the GUI-installer on a Windows system, insert the first CD in the CD drive and execute isinstaller.exe.

Click Create Install Shell Script to launch the installation wizard.

The procedure for interactive installation is similar to Installation using the GUI-installer. The default hostnames of FJSVihs and FJSVisgui are for a Windows system; change them for a Linux system. The 'Confirm Setup Information' screen is displayed.

On this screen, check the settings and click Next. The 'Result of create installation shell script' screen is displayed. To generate the shell scripts, click Next. The 'Output Install Log and Shell Scripts' screen is displayed. Select the required options and the destination directory and click Finish.

To exit the GUI-installer, click Exit on the initial installation wizard.

Note

• When executing the GUI-installer on a Windows system, the following systems are required.

− Windows 2000, Windows XP or Windows 2003 Server

• The shell scripts listed below need to be transferred to the Linux system on which installation of the Interstage Application Server Server Package is performed:

− <output-destination-directory>\isinstaller\setupinstall.sh

− <output-destination-directory>\isinstaller\setupuninstall.sh

For details on how to execute setupuninstall.sh, refer to Generating Installation Scripts.

When executing setupinstall.sh or setupuninstall.sh to install or uninstall the Server Package on a Linux system, these shell script files must be set to allow execution. If the CD mount directory of the Linux system is different to '/mnt/cdrom', correct PKGDIRECTORY in setupinstall.sh. ex) Assume the mount directory is "/mnt/ABC": PKGDIRECTORY="/mnt/ABC/RPMS"

To perform installation with setupinstall.sh, login to the system as a superuser and execute the following commands. # cd directory-of-shellscripts <RETURN> # chmod +x setupinstall.sh <RETURN> # ./setupinstall.sh <RETURN>

When the GUI-installer ends, reboot the system. # cd / <RETURN> # shutdown -r now <RETURN>

Install Procedure

1-13

Installation using Installation Shell Script To Install Interstage Application Server Server Package using the installation shell script, execute install.sh.

Install the Server Package using the following procedures.

1) Execute install.sh Insert the second CD of the Server Package and specify install.sh. Change the installation shell script to the directory on the CD-ROM, and then execute. # mount /dev/<device-name> /mnt/cdrom <RETURN> # cd /mnt/cdrom # ./install.sh <RETURN>

Note

After install.sh is executed, there may be short delay until the installation window is displayed.

If any packages to be installed are already installed, the install.sh outputs the following messages. <package-name> is already installed.

To continue the install after uninstalling this product or the packages, re-execute install.sh.

Selecting the Server Type

First, select the server type.

If Application Server is selected, select typical or custom. Please choose the server type to install. (1: Application Server, 2: Admin Server) [1,2,q]:

Performing a Typical install

To perform a typical installation, select 'typical' as the type of installation to be performed by entering '1' and press <RETURN>. Please select the installation type. (1: typical, 2: custom) [1,2,q]:

Enter the port number of the CORBA Service. Please specify port number of CORBA Service. (default: 8002) [?,q]:


1-14

Enter the port number of the Web Server (Interstage HTTP Server) and Interstage Service. Please specify port number of Web server(Interstage HTTP Server). (default: 80) [?,q]:

Enter the port number of the Interstage Management Console. Please specify port number of Interstage Management Console. (default: 12000) [?,q]:

If using SSL communication on the Interstage Management Console, enter 'y'. Please select whether to use SSL encryption communication for Interstage Management Console. (default: n) [y,n,q]

If using the Message Manual for Interstage Management Console, enter 'y'. Please select whether to use Message Manual for Interstage Management Console. (default: y) [y,n,q]:

Check the displayed installation settings. To start installation, enter 'y' and <RETURN> is response to the following prompt. Do you want to proceed with the installation ? [y,q]:

Performing a Custom install

To install using the install.sh shell, you may choose either Select Function or Select Package.

Choose Select Function to install the functions you want to use. The package required for the corresponding function is installed automatically.

Choose Select Package to install the packages you want to use. More packages are available for this option than for the Select Function option. By selecting Select Package, you can choose which packages you want to install.

To perform a 'custom' installation, select 'custom' as the type of installation to be performed by entering '2' and press <RETURN>. Please select the installation type. (1: typical, 2: custom) [1,2,q]:

Install Procedure

1-15

1. Select the function installation.

Select 'the function installation' by entering '1' and press <RETURN>. Please select whether to choose functions or packages to install. (1: function, 2: package) [1,2,q]:

The function list is displayed. Select 'all' or the number of the function(s) to be installed. functions: 1 Web Server(Interstage HTTP Server) 2 JDK/JRE : Please select functions. When you choose more than one, please separate with ",".[?,??,all,q]:

2. Select the package installation.

Select 'the package installation' by entering '2' and press <RETURN>. Please select whether to choose functions or packages to install. (1: function, 2: package) [1,2,q]:

The package list is displayed. Select 'all' or the number of the package(s) to be installed. Packages: 1 FJSVawjdk Interstage Apworks Java Development Kit 2 FJSVidsdk InfoDirectory Software Development Kit : Please select packages. When you choose more than one, please separate with ",". [?,??,all,q]: all

If using SSL communication on the CORBA Service samples, enter 'y'. Do you want to install the CORBA Service samples? (default: y) [y,n,q]:

Enter the port number of CORBA Service. Please specify port number of CORBA Service. (default: 8002) [?,q]:

Select whether 'JDK' or 'JRE' is to be used. Please select JDK or JRE. (1: JDK, 2: JRE) (default: 1) [1,2,q]


1-16

Select whether or not JDK/JRE 1.3 is to be installed. If not installing it, enter 'n'. Please select whether to install JDK/JRE 1.3 (default: y) [y,n,q]:

Select whether or not JDK/JRE 1.4 is to be installed. If installing it, enter 'y'. Please select whether to install JDK/JRE 1.4 (default: n) [y,n,q]:

Enter the port number and the hostname of the Web Server (Interstage HTTP Server). Please specify host name of Web server(Interstage HTTP Server). (default: host01) [?,q]: Please specify port number of Web server(Interstage HTTP Server). (default: 80) [?,q]:

Enter the port number and the hostname of the Interstage Management Console. Please specify host name of Interstage Management Console. (default: host01) [?,q]: Please specify port number of Interstage Management Console. (default: 12000) [?,q]:

If using SSL communication on the Interstage Management Console, enter 'y'. Please select whether to use SSL encryption communication for Interstage Management Console. (default: n) [y,n,q]

If using the Message Manual for Interstage Management Console, enter 'y'. Please select whether to use Message Manual for Interstage Management Console. (default: y) [y,n,q]:

Check the displayed installation settings. To start installation, enter 'y' and <RETURN> in response to the following prompt. Do you want to proceed with the installation ? [y,q]:

Install Procedure

1-17

2) System Reboot When the installation process has been completed, the following message is displayed. Installation of "Interstage Application Server" has ended.

Reboot the system. # cd / <RETURN> # shutdown -r now <RETURN>

3) Start Interstage When the machine starts, Interstage is started when an automatic setup is executed. To run the sample application, refer to Sample Applications for Application Server.

Note

To switch a version of JDK or JRE that is already installed, the Interstage Management Console settings must be modified. For details of how to modify the settings, refer to 'Customizing the Interstage Management Console environment' in Appendix A of the Interstage Application Server Operator’s Guide.


1-18

Post-Installation This section explains the following aspects of Post-installation:

• Environment Variable Settings

• Setting up the Port Number of the Web server

• Starting the Web Server (Interstage HTTP Server) Automatically Using the Admin Server Functions

• Setting up the Portal Component

Environment Variable Settings Set the environment variables required for operating Interstage.

In Interstage, the following shell scripts are offered as support tools for setting the environment variables.

• /opt/FJSVisas/bin/setISASEnv.sh

• /opt/FJSVisas/bin/setISASEnv.csh

The methods for setting environment variables using the support tool are shown below.

Bourne shell or bash method

This method uses the 'dot' command to execute setISASEnv.sh in each machine used for operating. . /opt/FJSVisas/bin/setISASEnv.sh

C shell method

This method uses the 'source' command to execute setISASEnv.csh in each machine used for operating. source /opt/FJSVisas/bin/setISASEnv.csh

Setting up the Port Number of the Web server The default port numbers of the Apache HTTP Server (bundled with the operating system) and of the Interstage HTTP Server are both '80'. To set up and operate both Web servers, it is therefore necessary to change the port numbers defined in the following configuration files of each so that they are different.

• Interstage HTTP Server: /etc/opt/FJSVihs/conf/httpd.conf

• Apache HTTP Server: /etc/httpd/conf/httpd.conf

Post-Installation

1-19

Starting the Web Server (Interstage HTTP Server) Automatically Using the Admin Server Functions

In the Admin Server function, the Web server (Interstage HTTP Server) start shell is not registered in the RC procedure. For this reason, the Web server does not start automatically even if the Linux system is rebooted. To start the Web server (Interstage HTTP Server) in the Admin Server function automatically, execute the following shell and register the start shell in the RC procedure. /opt/FJSVihs/bin/install/ihsautosetup.sh

In the application server function, the Web server (Interstage HTTP Server) start shell is registered in the RC procedure, and the Web server starts automatically.

Setting up the Portal Component In order to use the Portal component, settings must be specified in addition to those existing as a result of installing the Interstage Application Server Server Package.

Execute the following shell script. /opt/FJSVispw/WEB-INF/setup/pwsetup.sh

Note

A sample application for a Framework must be run before the Portal component can be set up to display the Framework sample in the Portal component sample role window.

Execute the following interactive processing:

1. The portal component provides integration of Web screens and the personalized environment for each user. Therefore, users of the portal component require authentication. In this example, select the user authentication system to be used. (*1) Portalworks sign mode 1: Portalworks 2: LDAP 3: Interstage Single Sign On Please specify portalworks sign mode. [1-3,q] (1) :


1-20

2. The portal component uses FJSVena for storing information. Specify the password to access the Datastore of FJSVena. The user cannot omit the password. The password can be from 6 bytes up to 25 bytes. Only alphanumeric characters can be used for the password. Please specify the password which accesses Datastore used by Portalworks.[?]: Please specify the password which accesses Datastore used by Portalworks, again.[?]: Information for portal component setup. Sign mode: Portalworks Do you want to proceed with the installation ? [y,q]:y

*1) There are two authentication methods

• Authentication by the portal component

The portal component manages and authenticates the user.

• Authentication by an external authentication server

An external authentication system (LDAP (such as InfoDirectory) or Interstage Single Sign On, which is not the portal component) authenticates the user. Specify this if the user selects operation using an external authentication system.

− Portalworks

Select this when the user uses authentication provided by the portal component. Select 'Portalworks' when the user does not use any external authentication system.

− LDAP

Select this when the user uses the LDAP server for authentication. Use identity (user information) stored in the LDAP server. The user must construct the LDAP server environment.

− Interstage Single Sign On

Select this when the user uses the Interstage Single Sign On functions. The user must construct the Interstage Single Sign On environment.

Setting Interstage Application Server Perform the following steps to use the portal component:

• Set the Interstage HTTP Server environment definition file (httpd.conf) (when the user uses Interstage HTTP Server as a Web server).

State the contents of the httpd.conf file located in /etc/opt/FJSVispw/conf additionally at the end of the httpd.conf file located under /opt/FJSVihs/conf.

• Restart Interstage HTTP Server.

For starting or stopping Interstage HTTP Server, refer to Interstage HTTP Server Operation Commands in the Reference Manual (Command edition)

• Start WorkUnit (PortalServer).

For starting or stopping the WorkUnit (PortalServer), refer to an Interstage manual.

Post-Installation

1-21

Environment Setup For environment setup after Interstage Application Server setup, refer to 'Initial Settings' in the Interstage Portalworks Administration Guide.

If the user installs Interstage HTTP Server after installing the Portal component, or installs from the GUI installer, refer to 'Changing the Host Name and Port Number of the Web Server' in the Interstage Portalworks Administration Guide, and change the host name and port number.

Note

Interstage Contentbiz/Contentbiz Repository cannot be operated on a machine on which the Portal component is being operated.


1-22

Notes This section contains notes about the following topics:

• Notes about using JDK/JRE1.4

• Notes about installing Systemwalker Centric Manager (*)

• Notes about using Fujitsu Enabler

• Notes about installing CORBA Service from another product

Notes about using JDK/JRE1.4 Characters recommended for the host name

Use the following characters for the host name:

• Upper-case letters ('A'-'Z') or lower-case letters ('a'-'z')

• Numbers ('0'-'9')

• Hyphens ('-')

• Periods ('.')

If JDK/JRE1.4 is used, underscores ('_') cannot be used in the host name.

If non-recommended characters such as underscores are used in the host name, the installation processing period is extended and an error dialog informing you that the Interstage Operation Tool service failed to start is displayed at the time of installation.

Although installation processing continues after the error dialog is displayed, an error dialog informing you that the creation of the IJServer failed.

After the installation is complete, and you log in to the Interstage Management Console, the 'IS: error: is40001: Could not collect system information' message is output, and Interstage operations cannot be executed.

If an error is displayed because non-recommended characters were used in the host name, refer to 'Characters recommended for the host name', above, and modify the host name.

Notes about installing Systemwalker Centric Manager (*) This section includes notes about installing the server used for managing Systemwalker Centric Manager and the Interstage application server function on the same machine.

For details about operating Systemwalker Centric Manager, refer to the Systemwalker Centric Manager manual.

If the Systemwalker Centric Manager management client and the Interstage client are installed on the same machine, the Systemwalker management client cannot be used.

(*) Red Hat Enterprise Linux v.3 or later

Notes

1-23

To use the multiserver management function, only the following server types can be used for the installation.

− Admin Server

− Combined Server

− Standalone Server

Notes about using Fujitsu Enabler Registering an oms account

If an oms account has not been registered in the system, register it when installing Fujitsu Enabler.

Port number

The default port number used by the Fujitsu Enabler service is 9700. Before modifying the port number, make sure that it is not being used by other applications or the Fujitsu Enabler datastore. Modify the port number according to the following method.

Modify the port number in the following parts of the '/etc/services' file:

• omsservd new port number/tcp

• omsservd new port number/udp

The default port number used by the repository ranges from 2000 to 9999, and is not used when the repository is created. Before modifying the port number, make sure that it is not being used by other applications or the Fujitsu Enabler datastore. Modify the port number according to the following method.

/opt/FJSVena/Enabler/server/bin/omschangeport 'repository name' –pn 'new port number'

Notes about installing CORBA Service from another product The Interstage Application Server CORBA Service is also used in other products.

If you try to install Interstage, and a product containing a built-in CORBA Service has already been installed, the following message is output: Since FJSVod is installed from other Fujitsu's middleware products, installation is stopped.

If the following products are installed in the same system, refer to Notes about installing Systemwalker Centric Manager (*)

• Systemwalker Centric Manager operation Admin Server


1-24

2-1

Chapter 2 Installation (Client Package)

This chapter explains how to install the Client Package.

Chapter 2: Installation (Client Package)

2-2

Installation Scenarios There are two Interstage Application Server Client Package types that can be installed:

• Typical installation

Select this to use the standard functions following a simple installation.

• Custom installation

Select this to choose the functions you want to install.

Functions that can be used If the Typical installation is selected, the functions shown as “This cannot be changed” and “Selected” in Table 2-1 are installed. If the Custom installation is selected, it is possible to select the functions that are installed.

Table 2-1 Functions available in a Typical Enterprise Edition installation Default status Function

Enterprise Edition Plus


J2EE Common Resource

CORBA Service Client

CORBA Service Development Tool

Interstage EJB Service Client

Interstage JMS

SOAP Service Client

Portable-ORB

UDDI Client

Secure Communication Service

Smart Repository

Selected

This cannot be changed

1.3.1 Not selected Not selected JBK Plugin

1.4.1 Selected Selected

System Requirements

2-3

System Requirements This section explains the system requirements.

OS • Windows Server(TM) 2003 Standard Edition or Enterprise Edition (*1)

• Windows® XP Professional, or Home Edition (*2)

• Windows® 2000 Professional, Server or Advanced Server

*1. This cannot be used in combination with the Terminal Services function

*2. If IPv6 is used, apply Service Pack 1 or later.

Disk Space

Table 2-2 Disk Space Requirements Drive/Folder Application Server

Installation drive 350MB

System drive 150MB

Temporary folder (Environment variable TEMP) 10MB

Note

The disk space requirements shown above have been calculated assuming a target drive using 32 KB per cluster. Approximately 1.5 times the stated disk space is required for a target drive using 64 KB per cluster.

Execution Environment • Microsoft® Internet Explorer 4.01 (**SP1 or later).


2-4

Pre-Installation Preparations Essential Tasks before beginning Installation Before beginning installation of the Interstage Application Server Client Package:

• Ensure that all of the relevant items described in the System Requirements table are satisfied in the target environment.

• Close any applications that are running.

• Delete any unnecessary paths from the environment variables (PATH, CLASSPATH)

• Interstage Application Server Client Package cannot be installed in an environment in which Interstage Application Server Package for Windows has already been installed. If it is already installed, uninstall it before installing Interstage Application Server Client Package.

When Interstage Application Server Server Package is installed onto an NTFS formatted drive When the Interstage Application Server Server Package is installed onto an NTFS formatted drive, the files and folders located in the installation folder will inherit the permissions settings of the folder into which the Interstage Application Server Server Package is installed.

Assign either of the following permissions to the installation folder:

• Administrator user (full control) and SYSTEM group (full control)

• Administrators group (full control)

For details regarding the setting of user permissions for each file and folder located in the installation drive, refer to the respective section in the Reference Manual (Command Edition).

• Execution of the following CORBA Service Commands:

− odlistns

− IDLc

− odlistir

• Operation of a CORBA program that uses the odwin.dll command

• When utilizing a JMS listener that uses Durable Subscription.

Install Procedure

2-5

Install Procedure Installation of the Interstage Application Server Client Package must be performed by a user who belongs to the Administrators group.

Note

• If the terminal service is installed in Windows 2000 Server or Windows 2000 Advanced Server in application server mode, execute the following command to switch to installation mode before installing the Interstage Application Server Enterprise Edition Client Package. CHANGE USER /INSTALL

• After installing the Interstage Application Server Enterprise Edition Client Package, execute the following command to switch from installation mode to operation mode. CHANGE USER /EXECUTE

Insert the Client Package CD in the CD drive. The autorun program should launch automatically; however if it does not, double click on the autorun icon in the root directory of the installation CD to launch it. Click Install to launch the installation wizard. The Installation Type Selection screen is displayed.

Performing a Typical Install Select the type of installation to be performed (“Typical”), and click Next. The Check Installation Settings screen is displayed. Check the displayed settings and select whether or not to modify them. If they are not to be modified, select Do not make any change and click Change to begin the install.

After selecting Change, the Select Destination Folder screen is displayed. Ensuring that adequate disk space is available on the target drive, specify the installation folder and click Next. The Check Installation Settings screen is displayed. Confirm the displayed settings, and then click Install to begin the installation. The Setup Status screen is displayed.

Once the installation process has been completed, the Installation Completed screen is displayed. Click Finish.


2-6

Performing a Custom Install Select the type of installation to be performed (“Custom”), and click Next. The Select Destination Folder screen is displayed.

Specify the installation folder, and then click Next. The Select Components to Install screen is displayed. Select the components and functionality to be installed, ensuring that adequate disk space is available on the target drive, and click Next. The Check Installation Settings screen is displayed. Check the displayed settings.

Click Back to return to a previous screen to modify settings, or click Install to begin the installation. The Setup Status screen is displayed.

When the installation process has been completed, the Installation Completed screen is displayed. Click Finish.

Post-installation

2-7

Post-installation This section explains the following aspects of Post-installation:


• Environment Variable Settings

• CORBA Service

• Portable-ORB

Fujitsu XML Processor To use the Fujitsu XML processor a separate installation operation is required. Insert the product CD (which includes the client function) into the CD drive, double-click on \XML\setup.exe and follow the instructions of the installer screens.

If the confirmation dialog box for system restart opens when Fujitsu XML processor installation is competed, be sure to restart the system. The user documentation for the Fujitsu XML Processor can be found in the program directory, accessed by selecting Start > Programs > Fujitsu XML Processor 5.1.

Environment Variable Settings In order to install the Interstage Application Server Client Package, the path of the folder of each specific component of the Java integrated development environment and operation test environment must be set in the PATH environment variable. Additionally, the paths of the respective Java class library and Jar file must be set in the CLASSPATH environment variable. The Interstage Application Server installation program will automatically modify the Windows environment variables PATH and CLASSPATH. However, if the length limit of the PATH and/or CLASSPATH variables is exceeded at this time, the modification will fail and one of the following error messages will be displayed:

• Unable to set environment variable required for Interstage Application Server for Client. See files below to set PATH variable for system environment variable.

• Unable to set environment variable required for Interstage Application Server for Client. See files below to set CLASSPATH for user environment variable.

• Unable to set environment variable required for Interstage Application Server for Client. See files below to set PATH variable for system environment variable and CLASSPATH variable for user environment variable.


2-8

Setting PATH and CLASSPATH If the automatic modification of the PATH and CLASSPATH variables should fail during the installation process manually set the environment variable PATH according to the following procedure:

1. Display the contents (variable values) of the PATH and CLASSPATH environment variables from Control Panel, by selecting System > Detailed Settings.

− Windows® 2000

Access the Control Panel, and select System > Environment > Environment Variables.

− Windows® Server 2003:

Access the Control Panel, and select System > Detailed Settings > Environment Variables.

2. Delete any unnecessary paths.

3. Add the values found in the following files to the respective environment variable:

− C:\Interstage\path.txt

Add the value found in this file to the system environment variable, PATH.

− C:\Interstage\classpath.txt

Add the value found in this file to the system environment variable, CLASSPATH.

4. Save the variable settings, and then restart the system.

CORBA Service When the CORBA Service is used for application linkage, it is necessary to refer to a Naming Service or an Interface Repository to acquire information about the respective applications. For this reason, the Naming Service or Interface Repository host information must be defined in the inithost file of the CORBA Service Client.

The host information can be set to the inithost using the odsethost command (C:\Interstage\ODWIN\bin\odsethost).

Example

Adding CORBA server information to the inithost file (host name: server1, port number: 8002) odsethost -a -h server1 -p 8002

Restart the system after setting the CORBA Service information to the inithost file.

For details of the odsethost command, refer to the Reference Manual (Command Edition). For details of the inithost file, refer to the Tuning Guide.

Post-installation

2-9

Portable-ORB When the Portable-ORB is used, the following settings must be performed according to the operation mode.

Table 2-3 Portable-ORB Settings Operation Mode Required Settings Comments

Portable-ORB and Java applets are downloaded from a Web server

initial_hosts Setting performed for the Web server *

initial_hosts Setting performed for the Web server * Only Java applets are downloaded from a Web server. CLASSPATH Setting performed for the Client

initial_hosts Setting performed for the Client Java application

CLASSPATH Setting performed for the Client

* When the Portable-ORB or a Java applet is to be downloaded from a Web server, the Portable-ORB module and operating environment files must be located under the documents root directory of the Web server. The exact storage location differs according to the operation type.

For more detailed information, refer to the section on 'Portable-ORB Operation Environment File Settings' in Chapter 6, Java Programming Guide of the Distributed Application Development Guide (CORBA Service Edition).

To use Portable-ORB, configure the following environment settings according to the operating mode.

1) initial_hosts settings

The host name and port number of the Naming Service and Interface Repository to be referred to must be added to the Portable-ORB operating environment file (C:\Interstage\PORB\etc\initial_hosts).

In the operation mode in which Java applets are to be downloaded, use the initial_hosts file residing on the Web server. In the operation mode using Java applications, edit the initial_hosts file.

2) CLASSPATH settings

In the operation mode in which the Portable-ORB is not downloaded from a Web server, the CLASSPATH variable of the Client operated and installed by the Portable-ORB must be set.

An example of how to set the variable is shown below. set CLASSPATH=.;%PORB_HOME%\lib\ODporb.jar;%PORB_HOME%\lib\CosNaming.jar; %PORB_HOME%\lib\InterfaceRep.jar;%CLASSPATH% PORB_HOME："C:\Interstage\PORB"

The Java library set to the CLASSPATH variable depends on the JDK/JRE that is used.

For more detailed information, refer to the section on 'Execution of CORBA Applications; in Chapter 6, Java Programming Guide of the Distributed Application Development Guide (CORBA Service Edition).


2-10

Adding/Deleting Components for an Existing Installation

The Interstage Application Server Client Package supports addition/deletion of components for an existing installation. When adding components it is necessary to configure each respective component.

3-1

Chapter 3 Uninstallation (Server Package)

Chapter 3: Uninstallation (Server Package)

3-2

Pre-Uninstallation Essential tasks before beginning installation • Close any applications that are running.

• Check whether any repositories of Smart Repository are running using the [System] > [Services] > [Repository], [Repository: View Status] window in the Interstage Management Console. If any repositories are found to be running, stop them.

After checking that all repositories have stopped, back up the repositories if necessary and then delete all repositories. For details about backing up repositories, refer to 'Back up and Restore' in Chapter 1 of the Smart Repository Operator's Guide.

Additionally, save any required files in the following directories

− /opt/FJSVirep

− /etc/opt/FJSVirep

− /var/opt/FJSVirep

• Before installing Interstage and the server used for managing Systemwalker Centric Manager on the same server, stop all Systemwalker Centric Manager functions. For details of the stop method, refer to the Systemwalker Centric Manager manual.

Pre-uninstallation Preparations Before beginning uninstallation of the Interstage Application Server Server Package, stop all services and applications of Interstage Application Server by executing the following commands: # isstop –f # tdunsetup # /opt/FJSVisgui/bin/S99isstartoptool stop # /opt/FJSVisjmx/bin/isjmxstop # /opt/FJSVjs2su/bin/jssvstop

Pre-uninstallation for Portal component The Portal component is uninstalled at the same time as Interstage. Before uninstalling Interstage, note the following points:

• When uninstallation is executed, all the server resources are deleted. For this reason, the resources must be backed up before uninstallation for them to be saved. For details, refer to 'Backing-up System Resources' in the Interstage Portalworks Administration Guide.

To delete all the server resources completely, delete the Portalworks installation folder after uninstallation.

• The database created in the RDB is not deleted. Delete this database.

− Oracle: Delete using a tool such as Database Configuration Assistant.

Uninstallation

3-3

Uninstallation The following methods are available for uninstalling the Interstage Application Server Server Package. Select the appropriate uninstallation method for your system. In normal cases, it is recommended that the uninstallation is executed using the uninstall.sh shell.

1. Uninstallation with uninstall.sh

This is the uninstall method using uninstall.sh.

2. Uninstallation with setupuninstall.sh

setupuninstall.sh is generated by the GUI-Installer. This method is only available if the installation was performed using the GUI-installer.

Note

CORBA Service can also be used in the following products. If the following products are installed, do not uninstall CORBA Service.

• Systemwalker Centric Manager operation Admin Server

Uninstallation using uninstall.sh Uninstallation of the Interstage Application Server Server Package must be performed by a superuser.

Uninstallation of the Server Package is performed using the following procedures.

1) Execute uninstall.sh Insert the second CD of the Server Package, change the current directory to the CD root directory and execute uninstall.sh. # mount /dev/<device-name> /mnt/cdrom <RETURN> # cd /mnt/cdrom <RETURN> # ./uninstall.sh <RETURN>

Perform the uninstallation answering the uninstall.sh prompts.

2) System Reboot When the uninstallation process has been completed, the following message is displayed. Uninstallation of "Interstage Application Server" has ended.


3-4

Reboot the system. #cd / <RETURN> #shutdown -r now <RETURN>

Uninstallation using setupuninstall.sh For details on creating a setupuninstall.sh, refer to Uninstallation using uninstall.sh.

Uninstallation using setupuninstall.sh must be performed by a superuser and the setupuninstall.sh mode must be set to allow execution.

Execute the following commands: # chmod +x setupuninstall.sh <RETURN> # setupuninstall.sh <RETURN>

Note

If FJSVjs2su is uninstalled, the following Warning messages are output. These messages can be ignored.

Warning: /etc/opt/FJSVjs2su/jswatch.conf saved as /etc/opt/FJSVjs2su/jswatch.conf.rpmsave

Warning: /etc/opt/FJSVjs2su/jsgw_apapi.conf saved as /etc/opt/FJSVjs2su/jsgw_apapi.conf.rpmsave

Warning: /etc/opt/FJSVjs2su/jscontainer.xml saved as /etc/opt/FJSVjs2su/jscontainer.xml.rpmsave

After uninstallation is completed, reboot the system. # cd / <RETURN> # shutdown -r now <RETURN>

Notes

3-5

Notes This section contains notes on the following topics:

• Notes about uninstalling CORBA Service

Notes about uninstalling CORBA Service The CORBA Service included in Interstage is also used by the following products. If CORBA Service is used by another product, do not uninstall it. (*)

Systemwalker Centric Manager operation Admin Server

(*) Red Hat Enterprise Linux v.3 or later


3-6

4-1

Chapter 4 Uninstallation (Client Package)

Uninstallation

4-2

Uninstallation Before uninstalling the Interstage Application Server Client Package, close any applications that are running. Installation of the Interstage Application Server Client Package must be performed by a user who belongs to the Administrators group.

1. From the Start menu, select Programs > Interstage > Application Server > Uninstallation > Uninstall to launch the uninstallation of the Interstage Application Server Client Package.

2. In the Confirm Uninstall page, click OK to uninstall the Interstage Application Server Server Package. Click Cancel to cancel the uninstallation.

3. The completion message is displayed after the uninstallation processing finishes. Specify whether or not to restart the system, and then click Finish.

XML Processor Uninstallation If the Fujitsu XML Processor has been installed, a separate uninstall operation is required to uninstall it. To uninstall Fujitsu XML Processor open the Start menu, select Control Panel > Add/Remove Programs, and click Delete to launch the uninstaller. After the uninstallation is complete, delete the Fujitsu XML Processor Jar files that have been set to the CLASSPATH.

A-1

Appendix A Executing Sample Applications

This chapter explains the sample applications that can be executed in Interstage Application Server.

Appendix A: Executing Sample Applications

A-2

The Sample Environment This section explains the following topics:

• Overview of the Sample Environment and Explanation of Functions

• Advance Preparation

• Starting the Sample Environment

• Sample Applications that are Offered

Overview of the Sample Environment and Explanation of Functions

The sample environment is a GUI tool for running sample applications that use J2EE functions and Framework sample applications. Use the sample environment in a standalone environment.

This tool can also be used to display a guide containing an overview of each sample application, the environment setup method, and the execution method.

Advance Preparation Before starting the sample environment, it is recommended that the following preparation tasks are executed.

EE • Running the Web server so that it is linked with Interstage

After Interstage is installed, the settings are such that the Web server does not start up and link with Interstage. If the machine is restarted immediately after the installation, the Web server is not started automatically. For this reason, if the sample environment explained below is started immediately after the restart, the sample environment window is not displayed in the browser.

To run the Web server so that it is linked with Interstage, configure the settings according to the following procedure.

1. Select [System] from the Interstage Management Console.

2. Enter the following information in the [Update System Settings] screen, and then click [Update].

Detailed Settings

Item name Input value

Web server Select [Synchronized].

The Sample Environment

A-3

• Setting up Event Service

Before JMS can be used, 'Event Service' must be registered as the Interstage configuration service.

Using the Interstage Management Console, select [System]. In the [View System Status] window, click details [Show]. If 'Event Service' has not been registered in [Interstage Component Services], register it according to the following procedure:

1. Using the Interstage Management Console, select [System].

2. Enter the following information in Detailed Settings of the [Update System Settings] screen, and then click [Update].

Detailed Settings


Event Service Settings Select [Yes]

Plus • Setting up Event Service

Before JMS can be used, 'Event Service' must be registered as the Interstage configuration service.

Using the Interstage Management Console, select [System]. In the [View System Status] window, click details [Show]. If 'Event Service' has not been registered in [Interstage Component Services], register it according to the following procedure:


2. Enter the following information in Detailed Settings of the [Update System Settings] screen, and then click [Update].

Detailed Settings


JMS Settings Select [Yes]

• Setting the class path for the JDBC driver in J2EE properties

To use a sample application that uses an Oracle, SQL Server, or PostgreSQL database, the class path for the JDBC driver must be set in the J2EE properties.

Set the J2EE properties according to the following procedure.


2. Enter the following information in the [Update System Settings] screen, and then click [Update]

Detailed Settings


Classpath Class path of the JDBC driver that is used


A-4

Note

Set the class path for the JDBC driver as the class path. For detailed information about the environment settings, refer to the appropriate JDBC driver manual.

Starting the Sample Environment Start the sample environment according to the following operation. If it has already been set up, the Web browser starts up, and the sample environment initial window is displayed.

• Interstage Application Server/Interstage Application Server Plus

Click the [Start] menu, and then click [Programs]>[Interstage]>[Application Server]>[Deploy and run Sample Applications] to start the sample environment.

• Interstage Application Server Plus Developer

Click the [Start] menu, and then click [Programs]>[Interstage]>[ Application Server Plus Developer]>[Deploy and run Sample Applications] to start the sample environment.

(*) In Interstage Application Server Plus Developer, Interstage is not started automatically immediately after the installation or after restart. For this reason, Interstage must be started before the sample environment is started. Please check that Interstage has started by Interstage Management Console.

After Interstage is started according to the above procedure, the following query is output. Respond to the query to launch the setup of the sample environment.

The following query is output immediately after the installation. Any time after that, the query contents are different to those shown below, depending on the environment status.

Set up Sample Integrated Environment Guide and sample applications. 1. Sample Integrated Environment Guide preparation Do you want to deploy the Sample Integrated Environment Guide to the SampleGuideServer? (default:y) [y,n]

If 'y' is entered for the above query, an IJServer WorkUnit with the name 'SampleGuideServer' is created, the application of the Sample Integrated Environment Guide is deployed and started, and the following query is displayed:

Create the IJServer WorkUnit. (IJServer WorkUnit name: SampleGuideServer) Deployment information Web application name:SampleGuideServer Sample Integrated Environment Guide is being deployed. Deployed C:\Interstage\sample\integrate\SampleGuideServer.war Starting the IJServer WorkUnit because the Sample Integrated Environment Guide was deployed for a stopped IJServer WorkUnit.


A-5

2.Sample application preparation Specify the name of the IJServer WorkUnit used for sample application deployment. (default:SampleServer)[?,q]

If nothing is entered for the above query (the 'default' value is selected) and the Enter key is pressed, an IJServer WorkUnit with the name 'SampleGuideServer' is created, the sample application is deployed and started, and the sample environment initial window is displayed in the Web browser. The message that is output is shown below.

To change the IJServer WorkUnit name, specify any IJServer WorkUnit name when the above query is made.

Refer to the Sample Integrated Environment Guide for details of sample applications. Deployment information IJServer WorkUnit name: SampleServer Web application name: HelloServlet Web application name: meetingroom Sample Application is being deployed. Deployed: C:\Interstage\sample\integrate\ja\j2ee\servlet\helloservlet\HelloServlet.war Sample Application is being deployed. Deployed: C:\Interstage\sample\integrate\ja\framework\meetingroom\meetingroom.war Starting the IJServer WorkUnit because the Sample Integrated Environment Guide was deployed for a stopped IJServer WorkUnit.

If 'n' is entered for the first query, setup processing is interrupted. The Sample Integrated Environment Guide and application deployment are not executed. The message that is output is shown below:

Processing was terminated because the Sample Integrated Environment Guide was not deployed. Execute again, and deploy the Sample Integrated Environment Guide. Press any key to continue . . .

Execute the following. /opt/FJSVisspl/integrate/sampleexec.sh

If the above is executed, the following query is output. Respond to the query to launch the setup of the sample environment. Only the superuser can execute the sampleexec.sh.

Set up Sample Integrated Environment Guide and sample applications. Enter the user name that starts the Sample Integrated Environment Guide and sample applications.(default:root)[?,q]


A-6

Sample Integrated Environment Guide preparation Do you want to deploy the Sample Integrated Environment Guide to the SampleGuideServer? (default:y) [y,n]

After entering the user name that starts the Sample Integrated Environment Guide and sample applications, If 'y' is entered for the above query, an IJServer WorkUnit with the name 'SampleGuideServer' is created, the application of the Sample Integrated Environment Guide is deployed and started, and the following query is displayed. The message that is output is shown below:

Create the IJServer WorkUnit. (IJServer WorkUnit name: SampleGuideServer) Deployment information Web application name:SampleGuideServer Sample Application is being deployed. Deployed： /opt/FJSVisspl/integrate/SampleGuideServer.war Starting the IJServer WorkUnit because the Sample Integrated Environment Guide was deployed for a stopped IJServer WorkUnit. 2.Sample application preparation Specify the name of the IJServer WorkUnit used for sample application deployment. (default:SampleServer)[?,q]

If nothing is entered for the above query (the 'default' value is selected) and the Enter key is pressed, an IJServer WorkUnit with the name 'SampleGuideServer' is created, the sample application is deployed and started, and the sample environment initial window is displayed in the Web browser. The message that is output is shown below.

To change the IJServer WorkUnit name, specify any IJServer WorkUnit name when the above query is made.

Refer to the Sample Integrated Environment Guide for details of sample applications. Deployment information IJServer WorkUnit name:SampleServer Web application name:HelloServlet Web application name:meetingroom Sample Application is being deployed. Deployed /opt/FJSVisspl/integrate/ja/j2ee/servlet/helloservlet/HelloServlet.war Sample Application is being deployed. Deployed：/opt/FJSVisspl/integrate/ja/framework/meetingroom/meetingroom.war Starting the IJServer WorkUnit because the Sample Application was deployed for a stopped IJServer WorkUnit. To access the deployed Sample Integrated Environment Guide, specify the following URL on a Web browser. (hostname : Host Name、port : Port No) http://hostname:port/SampleGuideServer/


A-7

If 'n' is entered for the first query, setup processing is interrupted. The Sample Integrated Environment Guide and application deployment are not executed. The message that is output is shown below:

Processing was terminated because the Sample Integrated Environment Guide was not deployed. Execute again, and deploy the Sample Integrated Environment Guide.

Note

• By executing the above, 'IJServer name: SampleGuideServer' (the default for deployment of the sample environment) and 'IJServer name: SampleServer' (the first time default for deployment of the sample application) are created, the following applications are deployed automatically, and IJServer and the Web browser are started.

Deployed in 'IJServer name: SampleGuideServer'

− Sample environment applications

Deployed in 'IJServer name: SampleServer'

− HelloServlet sample application

− Meeting Room Reservation System (Framework sample application)

However, the Meeting Room Reservation System is not deployed automatically if Framework is not installed.

The IJServer types that are created are as follows:

− When EJB is installed

Web and EJB applications are operated in the same JavaVM

− When EJB is not installed

Only the Web application is operated

Additionally, the IJServer name for the sample application can be changed when the sample environment is executed (initialized). If the name for the sample application is changed, it becomes the default value for the IJServer name next time. If an IJServer name that has already been created is specified, it may cause the execution (initialization) of the sample environment to fail because of differences in the IJServer name, IJServer type, and applications that have already been deployed.

• When the sample environment is executed (initialized), if an IJServer name is specified for an IJServer that has already been created using the Interstage Management Console, it may cause the following message to be output in the sample environment window:

− Could not display the window because of defects in the environment.

If this message is output, check that the following items have been set in [Environment Settings] of the IJServer to which the sample environment has been deployed. If these items have not been set, set them using the Interstage Management Console.


A-8


Path Interstage installation folder\sample\integrate\bin


Library path /opt/FJSVisspl/integrate/lib

• An application that has been deployed automatically cannot be undeployed automatically. Use the Interstage Management Console to undeploy the application.

Additionally, an IJServer that has been created cannot be deleted automatically. Use the Interstage Management Console to delete the IJServer.

• In Interstage Application Server Plus Developer, the performance of the computer and efficiency of development work both improve if Interstage is stopped during development work. For this reason, it is recommended that Interstage is stopped after the sample application is checked.

To stop Interstage, using the Interstage Management Console, select [System]. In the [View System Status] screen, click [Stop Interstage]. In the window for selecting the stop method, select [Forced System Stop], and then click [stop]. After a while, Interstage stops.

• The sample environments mentioned in the above procedure cannot be executed in the following environments.

− A multiserver environment (Admin Server, Managed Server, reserve server)

− A system (Interstage) or Web server (Interstage HTTP Server) that has stopped

− JRE is selected for a custom install

− A WorkUnit with the default value WorkUnit name ('SampleGuideServer' or 'SampleServer'), or a WorkUnit for which the name has been changed exists as mentioned in the above procedure, and only the EJB application is operated for this WorkUnit

− A WorkUnit called 'SampleGuideServer' exists, and the sample environment.

If the following message is output, the sample environment can be set up according to the procedure shown below:

Although the IJServer WorkUnit called “SampleGuideServer” exists, the Sample Integrated Environment Guide is not deployed. For this reason, “SampleGuideServer” is treated as a user resource and processing stops. Check the list of IJServer WorkUnit with Interstage Management Console. When IJServer WorkUnit SampleGuideServer is not a user resource, retry after deleting SampleGuideServer.


A-9

When IJServer WorkUnit SampleGuideServer is a user resource and unable to deploy Sample Integrated Environment Guide, refer to "Appendix A of Installation Guide", create appropriate IJServer WorkUnit from Interstage Management Console and deploy SampleGuideServer.war.

Set up the sample environment according to the procedure shown below.

1) Using the Interstage Management Console, select [System]>[WorkUnit].

2) In the [Create New] screen, click details [Show].

3) Click WorkUnit settings [Show], enter the following information and then click [Create].

Simple settings Item name Input value

WorkUnit name This can be any name

WorkUnit settings


Path Interstage installation folder\sample\integrate\bin


Library path /opt/FJSVisspl/integrate/lib

4) Using the Interstage Management Console, select [System]>[WorkUnit]>[WorkUnit name entered above].

5) In the [Deploy] window, enter the following information and then click [Deploy].

Deployment settings Item name Input value

Deployment file Interstage installation folder\sample\integrate\SampleGuideServer.war

/opt/FJSVisspl/integrate/SampleGuideServer.war

6) After the deployment is complete, click [Start] In the [Operate] window.


A-10

7) Specify the following URL in the Web browser:

http://localhost:port number/SampleGuideServer/

'port number': the port number for the Web server

Create the IJServer WorkUnit for deployment of the sample application according to the Sample Integrated Environment Guide.

• If the Interstage Application Server configuration settings are as shown below, the sample environment start window cannot be displayed.

Using the Interstage Management Console, click [System]. In the [Update System Settings] window, click [Detailed Settings] > [Servlet Service Settings]. [Run Web server and WorkUnit on the same machine?] is not selected.

If [Run Web server and WorkUnit on the same machine?] is not selected, select it.

The settings sometimes revert to those shown above when a multiserver environment is changed to a standalone environment. If [Run Web server and WorkUnit on the same machine?] is not selected, select it.

• If the Web server port number is changed after the installation, the sample environment initial window cannot be displayed. In this case, specify the following in the Web browser: http://localhost:port number/SampleGuideServer/


If the installation is executed by overwriting the previous version, and the Web server port number is a number other than '80', the procedure shown above is the same.

• If the Web server settings are changed to use SSL after the installation, the sample environment initial window cannot be displayed. In this case, specify the following in the Web browser: https://localhost:port number/SampleGuideServer/


Sample Applications that are Offered The following sample applications are offered in the sample environment.

• Servlet/JSP

− HelloServlet application

− Applications that use Session management

− Applications that use Listener

− Applications that use Filter


A-11

− Applications that use the Tag library

− Applications that use JDBC

• EJB

− Application that uses the Session Bean

− Applications that use the BMP that conforms to EJB 2.0 specifications

− Applications that use the CMP (CMP 1.1) that conforms to EJB 2.0 specifications

− Application that uses the Message-driven Bean that conforms to EJB 2.0 specifications

− Applications that use the CMP (CMP 2.0) that conforms to EJB 2.0 specifications

• JMS

− Application that uses the JMS Publish/Subscribe model

− Application that uses the JMS Point-To-Point model

− Application that uses the JMS message selector function

− Application that uses the JMS queue browse function

• JavaMail

− Application that does sends and receives that uses JavaMail

• Business model

− Expense management system

• Framework

− Meetingroom booking system

− Office management system

For details about the method to import the above sample applications to the sample environment, refer to the appropriate application guide for the sample environment.

Depending on the installation status of Interstage Application Server (the components selected for custom install), it might not be possible to use an application.

Additionally, for JMS to be used in the following applications an environment in which JMS can be used, is required. For details about the environment setup method, refer to Advance Preparation.

• Application that uses the Message-driven Bean that conforms to EJB 2.0 specifications

• Application that uses the JMS Publish/Subscribe model

• Application that uses the JMS Point-To-Point model

• Application that uses the JMS message selector function

• Application that uses the JMS queue browse function

• Expense management system

Note

For details about trouble that might occur in the sample environment, refer to the sample environment Help.


A-12

Portal Component Sample Applications The following are offered as portal component sample applications. They can be displayed using the portal component user window.

Personalized view explanation

This is a Web page on which the concept of the portal component personalized view (window customization) is described.

Meeting Room Reservation (Framework sample application)

This is a Web application for reserving meeting rooms. It is the Framework sample application.

(*) To display this from the portal component user window, the Framework sample application must be executed before the portal component is set up.

This section explains the method to display the sample application.

Display method

1. The portal component must be set up before it can be used. To set up the Portal Component, refer to 'Setting up the Portal Component' in Chapter 1 – Installation (Server Package).

2. After setup, exit the machine restart, and then start the portal component according to the following procedure.

Specify the following URL in the Web browser. This starts the Operating Management Console for the portal component. http://host name:port number/portalworks/PWAdminSystem

'host name': the host name for the Web server

'port number': Specify a port number for the Web server. This is '80' by default.

(*) Before the Operating Management Console can be started, Interstage must be started. Refer to Checking that Interstage has started to start Interstage.

In the Operating Management Console, select [Status Monitor] from the [General] menu. In the [General - Status Monitor] window, click the [Start] button.

Portal Component Sample Applications

A-13

3. Log on from the user window. This displays the sample application.

Specify the following URL in the Web browser. This starts the portal component user window. http://host name:port number/portalworks/director

'host name': the host name for the Web server 'port number': Specify a port number for the Web server. This is '80' by default.

If independent authentication is used, the following logon ID is already registered. Log on using this ID.

Logon ID: user001, password: user001

(*) If LDAP authentication or Interstage Single Sign-on authentication is used, log on as a user that has been registered in the authentication server.


A-14

lix installation 1 - fujitsu...installation scenarios 1-3 functions that can be used enterprise...

Documents