Chapter 1 Installation (Server Package) - Fujitsusoftware.fujitsu.com/jp/manual/fm_e/b23j37jh0/b1wn5181/01/b1wn5… · Chapter 1: Installation (Server Package) Note ”n” is as

Chapter 1 Installation (Server Package)

This chapter explains how to install the Server Package.

1-1

Chapter 1: Installation (Server Package)

Installation scenarios This section explains the types of Interstage Application Server Package that can be installed.

The following types of Interstage Application Server Package can be installed.

• Application Server

Select this to install Interstage Application Server server functions.

• Admin Server

Select this to install Interstage Application Server Admin Server functions.

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 that is required for using Interstage is set up automatically. After the installation is complete, the Interstage Management Console can be used for simple operation.

Functions that can be used

Enterprise Edition: Application Server If the Typical installation is selected, the functions shown in “This cannot be changed” and “Selected” in the table below are installed. If the Custom installation is selected, it is possible to select the functions that are installed.

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

1-2

Installation scenarios


EventService Selected Asynchronous communication

MessageQueueDirector Not selected

SOAP Service Selected Web Services

ebXML Message Service Not selected

Optional feature

- 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

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

• Smart Repository

• Enabler Server

1-3


Plus: Application Server If the Typical installation is selected, the functions shown in “This cannot be changed” and “Selected” in the table below are installed. If the Custom installation is selected, it is possible to select the functions that are installed.



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

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

• Smart Repository

• Enabler Server

1-4

System Requirements

System Requirements This section explains the system requirements.

<OS>

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

• Windows® 2000 Server or Advanced Server

*1. This cannot be used in combination with the following function:

− Terminal Services

<Disk space>

Drive/Folder Application Server XML Processor

Installation folder 800 MB (*1)

System drive 200 MB 45 MB

Temporary folder (Environment variable TEMP) 10 MB

*1) To install JDK/JRE on a different drive to the installation folder, the following disk space is required.

− JDK1.3: 100MB

− JRE1.3: 60MB

− JDK1.4: 130MB

− JRE1.4: 80MB

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).

1-5


Pre-Installation Preparations Essential tasks before beginning installation

Before beginning installation of Interstage Application Server Server Package:

• Interstage Application Server Server Package cannot be installed in an environment in which any of the products listed below has already been installed. If any of the following products is already installed, uninstall it before installing Interstage Application Server Server Package.

− Client package of this software

− An earlier version or another edition of this software

− Interstage Business Application Manager

− Interstage Apworks

− Interstage Apworks (Apworks Client Runtime 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)

• When Interstage is installed, it might cause the installation to fail if resources that are used by Interstage such as disk and the registry (for example, event viewer, Explorer, registry editor) are used. Before starting the installation, exit all Windows® applications first.

When Interstage Application Server Server Package is installed onto an NTFS formatted drive

When 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 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)

To prevent access to folders or files installed onto an NTFS formatted drive by an unspecified user, access authority can be changed by executing the issetfoldersecurity command after the installation.

For details of issetfoldersecurity, refer to the “Interstage Application Server Reference Manual (Command Edition)”.

1-6

Pre-Installation Preparations

For a general user (a user that is not an Administrator user and does not belong to the Administrators group) to be able to execute the following Interstage operations, that user must have access authority to all folders or files under the Interstage installation folder. In this case, as above, use the issetfoldersecurity command to specify the user name (or group name).

• Execution of the following CORBA Service Commands:

− odlistns

− IDLc

− odlistir

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

• Execution of the EJB Service Command

• Execution of the WorkUnit Management Command

• Operation of the Interstage API

• Execution of the Event Service Command

• Execution of the JMS Operating Command

• When utilizing a JMS listener that uses Durable Subscription.

• Execution of the Backup Command

• When Interstage certificate authority is used and SSL certificates or encryption is employed.

If the terminal service is installed in Windows 2000 Server, Windows 2000 Advanced Server or Windows Server(TM) 2003

If the terminal service is installed in Windows 2000 Server, Windows 2000 Advanced Server, or Windows Server(TM) 2003 in application server mode, execute the following command to switch to installation mode before installing Interstage Application Server. CHANGE USER /INSTALL

After installing this product, execute the following command to switch from installation mode to run mode. CHANGE USER /EXECUTE

Notes about using the multiserver management function

All Managed Servers belonging to the Server Group must be installed in the same installation folder before the multiserver management function can be used. Even if the same folder name is specified for the installation folder, it may be treated as a different folder name by the use of the short path.

The installation folder name is treated as a short path in the following cases:

1. The installation folder name specified in the ”Select installation directory” window at the time of installation contains a space or spaces, and

2. There is a folder name in the same layer as the folder specified in point 1 with the same first “n” (see Note) characters.

1-7


Note

”n” is as follows, depending on the number of folders with the same name.The number of folders is 2 to 9: 6 characters

• The number of folders is 10 to 99: 5 characters

• The number of folders is 100 to 999: 4 characters

Problem

In a multiserver environment, if the folder configuration between servers differs (the same folder name exists/does not exist) in the same layer as the installation folder, the short path will differ between servers even if the same name is specified for the installation folder.

As a result, the environment definition contents will differ between Managed Servers, and an error will occur when Managed Servers are added to the Server Group.

Name of server Server A Server B

Folder configuration of the installation destination

"C:\Interstage A" exists There are no folders starting with "Inte" on the “C” drive

Specified installation folder name

"C:\Interstage B" "C:\Interstage B"

Short path name of the installation folder

"C:\INTERS~2" "C:\INTERS~1"

The short path name can be investigated by executing "dir /X" on the command prompt.

Action

Check the following points for all server installation folders in the multiserver environment.

1. Check whether there are other folder names with the same first 4-6 characters.

2. If a folder with the same name already exists, either change the installation folder name, or specify a folder name that does not contain spaces. Make the same settings for all servers.

In the above example, a folder name containing the "C:\Inters" part in Server A already exists. Either change this part to "C:\IS", or specify "C:\Interstage" or "C:\InterstageB" so that it does not contain spaces. Make the same settings for Server A and Server B.

If a folder with the same name is installed by mistake, uninstall the folder and then reinstall it setting a correct folder name according to the above guidelines.

1-8

Install procedure

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

Use the typical installation option to install the standard components and functionality of the Interstage Application Server Server Package, and use the custom installation option for cases in which you want to specify which components are to be installed.

• “:”, “;”, “/”, “*”, “?”, “\”, “<“, “>“, “(“, “)”, “|”, “#”, “%”, “^”, “!”, and double-byte characters cannot be specified for the installation folder name.

• During the installation, if Cancel is clicked to interrupt the installation, or the folder that has been set as the installation folder is changed to a different folder, it might cause folders that have already been created to remain. If necessary, delete these folders.

• During the installation, if an abnormality occurs during file copying, for example, a window urging restart of the computer is displayed. In this case, after the installation is complete, in the window for selecting system restart that is displayed, select either “Yes, restart computer now.” or “No, restart computer later.” and then click Finish. During the installation, if an abnormality occurs during file copying, for example, the installation processing is completed when the computer is restarted. If “No, restart computer later.” is selected, the computer must be restarted before the environment can be created.

• The user account ID 'oms' is created by installing Enabler.

Installing Application Server functions (Typical install) Insert the CD in the CD drive. The autorun program should launch automatically; if not, double-click the autorun icon in the root directory of the installation CD to launch it. Click Install to launch the installation wizard. The Server Type Selection page is displayed.

1. In the Server Type Selection page, select Install the Application Server, and then click Next.

2. In the Installation Type Selection page, select Typical, and then click Next.

If you specify a Typical installation, and the port number you intend to use in Interstage is already in use, a warning message is output. In the Check Installation Settings page, select the Change check box and then change the port number.

3. In the Check Installation Settings page, to start the installation using the displayed contents, click Next without removing the check mark from [Do not make any changes]. This starts the installation. To change the displayed contents, select the Change check box, and then click Next.

4. In the Select Destination Folder page, click Browse. Set the installation destination for Interstage, and then click Next.

5. In the Select Installation Folder for JDK 1.4 page, click Browse. Set the installation destination for JDK1.4, and then click Next.

Note

It is recommended that a new Interstage Application Server is installed in the standard folders.

1-9


6. In the Interstage Management Console Settings page, select the security operating mode for the Interstage Management Console. Select whether or not to use SSL encryption communication in the Interstage Management Console, and then click Next.

7. In the Port Number Setup page, specify a port number and then click Next. If there is no change to the port number, click Next again.

The default port numbers are shown in the table.

Function Default port number

Interstage Management Console 12000

Web Server (Interstage HTTP Server) 80

CORBA Service 8002

8. In the Installation selection of a message manual page, select whether or not to refer to the Messages Manual from the Interstage Management Console directly. If this is selected, you can refer to the manual of error messages that are output in the Interstage Management Console directly. Select [Message manual is installed], and then click Next.

9. In the Selection of install location page, set the creation destination for the J2EE common folder, and then click Next.

10. In the Check Installation Settings page, check the contents that have been entered. If the contents are correct, click Install. This starts the installation.

11. After the installation is complete, click Finish.

Installing the Application Server functions (Custom install) Insert the CD in the CD drive. The autorun program should launch automatically; if not, double-click the autorun icon in the root directory of the installation CD to launch it. Click Install to launch the installation wizard. The Server Installation Type Selection page is displayed.

1. In the Server Type Selection page, select Install the Application Server, and then click Next.

2. In the Installation Type Selection page, select Custom, and then click Next.


4. In the Select Components to Install page, select the function to be installed, and then click Next.

5. In the Selection of JDK or JRE page, select either JDK or JRE.

6. In the Select Installation Folder for JDK 1.x (or JRE 1.x) page, click Browse. Set the installation destination for the selected JDK or JRE, and then click Next. If multiple versions of JDK or JRE are selected, settings must be made for each version.

Note

It is recommended that a new Interstage Application Server is installed in the default folders.

7. If multiple versions of JDK or JRE have been selected, the Select JDK (JRE) version page is displayed, select the JDK or JRE version that is normally used, and then click Next.

1-10

Install procedure


9. In the Port Number Setup page, specify a port number and then click Next. If there is no change to the port number, click Next again.





CORBA Service 8002

Web Server (InfoProvider Pro) 81

10. In the Installation selection of a message manual page, select whether or not to refer to the Messages Manual from the Interstage Management Console directly. If this is selected, you can refer to the manual of error messages that are output in the Interstage Management Console directly. Select [Message manual is installed], and then click Next.

11. (Enterprise Edition only) If MessageQueueDirector or ebXML Message Service is selected, it must be installed on NTFS. If the Interstage installation folder is not NTFS, the window in step 14.below is displayed. Set the folder for installing MessageQueueDirector or ebXML Message Service on NTFS, and then click Next. If MessageQueueDirector or ebXML Message Service is not selected, or the Interstage installation folder is NTFS, the window in step 14.below is not displayed.

12. In the Selection of install location page, set the creation destination for the J2EE common folder, and then click Next.



Installing the Admin Server functions Insert the CD in the CD drive. The autorun program should launch automatically; if not, double-click the autorun icon in the root directory of the installation CD to launch it. Click Install to launch the installation wizard. The Server Type Selection page is displayed.

1. In the Server Type Selection page, select [Install Admin Server], and then click Next.

2. In the Check Installation Settings page, to start the installation using the displayed contents, click Next without removing the check mark from [Do not make any changes]. This starts the installation.

To change the displayed contents, select the Change check box, and then click Next.


Note

If the folder that has been set as the installation folder is changed to a different folder, it might cause folders that have already been created to remain. If necessary, delete these folders.

1-11


4. In the Select Installation Folder for JDK 1.4 page, click Browse. Set the installation destination for JDK1.4, and then click Next.

It is recommended that a new Interstage Application Server is installed in the standard folders.


6. In the Port Number Setup page, specify the port number to be used by the Interstage Management Console and Web server (Interstage HTTP Server) and then click Next. If there is no change to the port number, click Next again.





7. In the Installation selection of a message manual page, select whether or not to refer to the Messages Manual from the Interstage Management Console directly. If this is selected, you can refer to the manual of error messages that are output in the Interstage Management Console directly. Select [Install Messages Manual], and then click Next.



XML Processor To use the Fujitsu XML processor, a separate installation operation is required. Insert the product CD which includes the server function into the CD drive, double-click \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.2.

On completion of installation of Interstage Application Server Enterprise Edition and Fujitsu XML Processor, the following program groups are registered on the Start > Programs menu:

• Interstage

• Fujitsu XML Processor

1-12

Post-installation

Post-installation

Environment Variable Settings In order to install Interstage Application Server Server Package, it is necessary that the path of the folder of each specific component of the Java integrated development environment and operation test environment be set in the PATH environment variable, and that the paths of the respective Java class library and Jar file 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 Server. See files below to set PATH variable for system environment variable.

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

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

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 by accessing the Control Panel, and selecting System > Detailed Settings.

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.

Note

If the environment variables have not been successfully set, neither Interstage nor any of the services will be operational. After completing the manual settings according to the procedure described above and restarting the system, Interstage and each of the services will automatically start.

1-13


Starting the Web server (Interstage HTTP Server) automatically using the Admin Server functions

In the Admin Server functions, the ”FJapache” service of the Web server (Interstage HTTP Server) is installed manually using [Manual] as the ”Startup Type”. To start the ”FJapache” service automatically, first click (Control Panel > Management Tool > Services) in the service window. Next, set the ”Startup Type” of the ”FJapache” service of the Web server (Interstage HTTP Server) to [Automatic]. In the Application Server functions, the ”FJapache” service of the Web server (Interstage HTTP Server) is installed automatically using [Automatic] as the ”Startup Type”.

Action to take if automatic setup fails If the automatic setup fails during the installation, a dialog showing the abnormality is output. In this case, take the following action.

If the installation install is completed, take action according to the message showing the abnormality in the automatic setup that is output in the dialog and event viewer, and complete the setup using the isinitservice command. For details of the isinitservice command, refer to the “Reference Manual (Command Edition)”.

If the installation fails, take action according to the message showing the abnormality in the automatic setup that is output in the dialog and event viewer, and re-install “FJapache”.

Commands and storage directories for DLL files used until Interstage Application Server V6.0L10

The commands offered in each service and the storage directories for DLL files have changed from Interstage Application Server V7.0 For processing to recognize storage directories configured before Interstage Application Server V6.0, the old storage directory must be changed to match the configuration of the new storage directory.

If the configuration of the old storage directory is not changed, the issetcompatiblepath command can be used to copy commands and DLL files to the old storage directory. For details of the issetcompatiblepath command, refer to the “Reference Manual (Command Edition)”.

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

Open the Start menu and select Programs > Interstage > Application Server > Portal component setup to display the Setup screen. For details regarding setup of the Portal component, click Help on the Setup screen. For details regarding setting up the environment of the Portal component, refer to the Interstage Portalworks Administration Guide.

Note

• Before the Portal component can be operated in a standalone environment, the following procedures must be performed:

1) Add network adapter: Microsoft Loopback Adapter

2) Set up the added adapter, and specify under the TCP/IP settings that the IP address be obtained automatically for the DHCP server.

1-14

Post-installation

• 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. To start the Framework sample application, click the Start menu and select Programs > Interstage > Application Server > Run Sample Integrated Environment.

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

1-15


Adding/Deleting components for an existing installation

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

1-16

Chapter 2 Installation (Client Package)

This chapter explains how to install the Client Package.

2-1

Chapter 2: Installation (Client Package)

Installation scenarios The Interstage Application Server Client Package 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 choose the functions you want to install.

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

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

2-2

System Requirements

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 following function:

− Terminal Services

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

<Disk space> Drive/Folder Application Server

Installation folder 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-3


Pre-Installation Preparations Essential tasks before beginning installation

Before beginning installation of Interstage Application Server Client Package:

• If the Server package is installed, uninstall it.

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


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

• When Interstage is installed, it might cause the installation to fail if resources that are used by Interstage such as disk and the registry (for example, event viewer, Explorer, registry editor) are used. Before starting the installation, exit all Windows® applications first.

When Interstage Application Server Server Package is installed onto an NTFS formatted drive

When 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 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)

If the terminal service is installed in Windows 2000 Server, Windows 2000 Advanced Server, or Windows Server(TM) 2003

If the terminal service is installed in Windows 2000 Server, Windows 2000 Advanced Server or Windows Server(TM) 2003 in application server mode, execute the following command to switch to installation mode before installing Interstage Application Server. CHANGE USER /INSTALL

After installing this product, execute the following command to switch from installation mode to run mode. CHANGE USER /EXECUTE

2-4

Install procedure

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

Use the typical installation option to install the standard components and functionality of the Interstage Application Server Client Package, and use the custom installation option for cases in which you want to specify which components are to be installed.

Note

• “:”, “;”, “/”, “*”, “?”, “\”, “<“, “>“, “(“, “)”, “|”, “#”, “%”, “^”, “!”, and double-byte characters cannot be specified for the installation folder name.

• During the installation, if ”Cancel” is clicked to interrupt the installation, or the folder that has been set as the installation folder is changed to a different folder, it might cause folders that have already been created to remain. If necessary, delete these folders.

• During the installation, if an abnormality occurs during file copying, for example, a window urging restart of the computer is displayed. In this case, after the installation is complete, in the window for selecting system restart that is displayed, select either “Yes, restart computer now.” or “No, restart computer later.” and then click Finish. During the installation, if an abnormality occurs during file copying, for example, the installation processing is completed when the computer is restarted. If “No, restart computer later.” is selected, the computer must be restarted before the environment can be created.

• For details of installing the XML processor, refer to XML Processor.

Performing a Typical install 1. Insert the CD of the Client Package in the CD drive. The autorun program should launch

automatically; if not, double-click 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 page is displayed.

2. In the Installation Type Selection page, select Typical, and then click Next.

3. In the Check Installation Settings page, to start the installation using the displayed contents, click Next without removing the check mark from [Do not make any changes]. This starts the installation.

To change the displayed contents, select the Change check box, and then click Next.


5. In the Check Installation Settings page, check the contents that have been entered, If the contents are correct, click Install. This starts the installation.


2-5


Performing a Custom install 1. Insert the CD of the Client Package in the CD drive. The autorun program should launch

automatically; if not, double-click 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 page is displayed.

2. In the Installation Type Selection page, select Custom, and then click Next.

3. In the Choose Destination Location page, click Browse. Set the installation destination for Interstage, and then click Next.

4. In the Select Components to Install page, select the function to be installed, and then click Next.

5. In the Check Installation Settings page, check the contents that have been entered, If the contents are correct, click Install. This starts the installation.


2-6

Post-installation

Post-installation

Environment Variable Settings In order to install Interstage Application Server Client Package, it is necessary that the path of the folder of each specific component of the Java integrated development environment and operation test environment be set in the PATH environment variable, and that the paths of the respective Java class library and Jar file 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.

Setting PATH and CLASSPATH

If the automatic modification of the PATH and CLASSPATH variables fails 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 by accessing the Control Panel, and 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.

2-7


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

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

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

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 the chapter “Java Programming Guide” in Distributed Application Development Guide (CORBA Service Edition).

2-8

Post-installation

To use Portable-ORB, make 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, and 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 by (installed by) the Portable-ORB must be set.

An example of the settings procedure 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 Distributed Application Development Guide (CORBA Service Edition).

2-9


Adding/Deleting components for an existing installation

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.

2-10

Chapter 3 Uninstallation (Server Package)

3-1

Chapter 3: Uninstallation (Server Package)

Pre-uninstallation Essential tasks before beginning installation


• To register ServerMachineMonitor and ServerMachineMonitorAgent in a service, execute the isunsetsmm command and isunsetsmma command.

• 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 "Backing up and Restoring Smart Repository" in the Smart Repository Operator's Guide. Also, save any files that are considered to be necessary in the following folder.

− C:\Interstage\IREP

Tasks before uninstalling JTS

Execute the following tasks before stopping the services of the database linkage service.

1. Check whether the OTS system and resource management program are running using the otsalive command.

(Example: They are running) > otsalive <RETURN> ------------------------------------------------------------------------ OTS system START-TIME 1999/06/27 10:17:26 OTS Resource resourcedef1 START-TIME 1999/06/27 11:50:12 OTS Resource resourcedef2 START-TIME 1999/06/27 12:50:12 ------------------------------------------------------------------------

(Example: They have not been started) > otsalive <RETURN> ------------------------------------------------------------------------ Nothing ------------------------------------------------------------------------

2. If they are running, stop the OTS system using the otsstop command.

Also, stop the resource management program using the otsstoprsc command. If it was operated using the isstart command, stop it using the isstop command. > otsstop <RETURN> > otsstoprsc -n resourcedef1 <RETURN> > otsstoprsc -n recourcedef2 <RETURN>

3. Evacuate or delete user resources in the folder in which the database linkage service was installed. If a dump file is output, delete it.

The dump file is stored under Interstage installation folder\ots\var.

3-2

Pre-uninstallation

4. Delete any unnecessary information that is registered in CORBA Service. If this is not deleted, there is no need to register the settings for the OTS system operating environment (otssetup command), the resource management program (otssetrsc command), and the server application (CORBA application) after reinstalling database linkage service.

− Delete the registered server application information using the OD_impl_inst command and the OD_or_adm command.

− Delete the registered resource management program information using the otssetrsc command. > otssetrsc -d -n resourcedef1 <RETURN> > otssetrsc -d -n resourcedef2 <RETURN>

− Delete the OTS system operating environment using the otssetup command. >otssetup -d <RETURN>

Pre-uninstallation for Portal component

Portal component is uninstalled at the same time as Interstage. Before uninstalling Interstage, note the following points:

• When the uninstallation is executed, all the server resources are deleted. For this reason, the resources must be backed up before the 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 the uninstallation.

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

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

3-3


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

1. In the Start menu, execute Programs > Interstage > Application Server > Uninstallation > Uninstall to launch the uninstallation of Interstage Application Server Server Package.

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

3. After the uninstallation is completed, select “Yes, I want to restart my computer now”. This restarts the machine.

Note

• The uninstallation might fail while the service startup is being processed immediately after the machine is started. If this happens, wait for a while and then re-execute the uninstallation.

• The Cancel button is inactive during the uninstallation.

XML Processor uninstallation Refer to Uninstalling XML Processor.

3-4

Post-uninstallation

Post-uninstallation • To reinstall Interstage after the uninstallation, the system must be restarted before Interstage is

reinstalled.

Before reinstalling Interstage, first delete the previously installed resources.

• If the path in the PATH and CLASSPATH environment variables has been set manually, it might remain even after the uninstallation processing. Delete any unnecessary paths from the environment variables.

• Delete the following folders if they are still remaining. In the following example, the folders were installed in C:\Interstage.

− C:\Interstage\etc

− C:\Interstage\var

− C:\Interstage\GUI\trcfolder

− C:\Interstage\F3FMwww\Oplogfolder

− C:\Interstage\ODWIN\etc

− C:\Interstage\ODWIN\var

− C:\Interstage\eswin\etc

− C:\Interstage\eswin\var

− C:\Interstage\EJB\var

− C:\Interstage\EJB\etc

− C:\Interstage\jdk13 (*1)

− C:\Interstage\jre13 (*1)

− C:\Interstage\jdk14 (*1)

− C:\Interstage\jre14 (*1)

− C:\Interstage\ots\etc (*2)

− C:\Interstage\ots\var (*2)

− C:\Interstage\ID

− C:\Interstage\F3FMsoap\log

− C:\Interstage\F3FMsoap\etc (*3)

− C:\Interstage\F3FMsoap\classes (*4)

− C:\Interstage\jms\etc

− C:\Interstage\jms\var

− C:\Interstage\F3FMihs (*5)

− C:\Interstage\F3FMsso\ssoatcsv (*6)

3-5


− C:\Interstage\F3FMsso\ssoatcag (*6)

− C:\Interstage\F3FMsso\ssoatzag (*6)

− C:\Interstage\F3FMsso\ssocm (*6)

− C:\Interstage\F3FMsso\ssoatzag\lib

− C:\Interstage\Extp\etc

− C:\Interstage\td\etc

− C:\Interstage\td\trc

− C:\Interstage\td\isp

− C:\Interstage\td\var (*7)

− C:\Interstage\jms

− C:\Interstage\J2EE

− C:\Interstage\IREP

− C:\Interstage\Portalworks

− C:\Interstage\Enabler

− C:\Interstage\APW

− C:\Interstage\var\repository (*8)

(*1) If JDK/JRE is installed in a different, delete that folder.

(*2) If there are files or folders under the folder, delete everything including those files or folders.

(*3) A site certificate, CA certificate, or private key is saved here. If necessary, evacuate it to a file under the path before the deletion.

(*4) If CORBA/SOAP client gateway class/jar files have been allocated, if necessary evacuate them to a file under the path before the deletion.

(*5) The Web server (Interstage HTTP Server) environment definition file and log file are saved here. If necessary, evacuate them to a file under the path before the deletion.

(*6) The Interstage Single Sign-on environment definition file is saved here. If necessary, evacuate it to a file under the path before the deletion.

(*7) If the Systemwalker CentricMGR Operation Management Server or the Systemwalker Centric Manager Operation Management Server has been installed, do not delete C:\Interstage\td\var\IRDB.

(*8) If “Repository Storage Destination” of the business configuration management function has been changed, delete it. Do not delete this folder if you intend to reuse previous information in the next installation. Information can be inherited by specifying the same folder in the next installation.

3-6

Uninstalling XML Processor

Uninstalling XML Processor If the Fujitsu XML Processor has been installed, a separate uninstall operation is required to uninstall it. The operation is the same as that used to uninstall Interstage Application Server Server Package. After the uninstallation is complete, delete the Fujitsu XML Processor Jar files that have been set to the CLASSPATH.

3-7


3-8

Chapter 4 Uninstallation (Client Package)

4-1

Uninstallation

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

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

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

3. After the uninstallation is completed, select “Yes, I want to restart my computer now”. This restarts the machine.

XML Processor uninstallation Refer to Uninstalling XML Processor in Chapter 3 – Uninstallation (Server Package).

Post-uninstallation • If the path in the PATH and CLASSPATH environment variables has been set manually, it might

remain even after the uninstallation processing. Delete any unnecessary paths from the environment variables.

• Delete the following folders if they are still remaining. In the following example, the folders were installed in C:\Interstage. − C:\Interstage\J2EE − C:\Interstage\F3Fmsoap − C:\Interstage\ID − C:\Interstage\JBKDI − C:\Interstage\IREP

4-2

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] page, 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] page, 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] page, 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.



A-4

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

Detailed Settings


Classpath Class path of the JDBC driver that is used

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 using the 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]


A-5

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.

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.


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


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 . . .


A-6

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]

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)


Web application name:SampleGuideServer

Sample Application is being deployed. Deployed：/opt/FJSVisspl/integrate/SampleGuideServer.war


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.


A-7

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.


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/

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.


A-8

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.


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] page, click [Stop Interstage]. In the window for selecting the stop method, select [Forced System Stop], and then click [stop]. After a while, Interstage stops.


A-9

• 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.

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] page, 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


A-10


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.

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.


A-11

• 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

− 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


A-12

• 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.

Portal Component Sample Applications

A-13

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. Refer to the notes in Operating the portal component to set up the portal component.

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.

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

Documents

Chapter 1 Installation (Server Package) - Fujitsusoftware.fujitsu.com/jp/manual/fm_e/b23j37jh0/b1wn5181/01/b1wn5… · Chapter 1: Installation (Server Package) Note ”n” is as