Interstage Portalworks General Description

i

Preface

Portal component (hereafter referred to as Portalworks) serves to integrate information stored in a corporation's network.

Portalworks is a Web application that enables the construction of a corporate portal tailored to individual users and GUIs.

November 2003

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation in the United States and/or other countries.

Sun, Sun Microsystems, the Sun logo, Solaris and all Solaris-based marks and logos are trademarks and/or registered trademarks of Sun Microsystems, Inc. Linux is the trademark and registered trademark of Linus Torvalds in the U.S. and other countries. Netscape, Netscape Navigator, and Netscape Communicator are trademarks of Netscape Communications Corporation in the USA and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other countries, and are used under license.

All other company, product or service names referenced in this document are used for identification purposes only and may be trademarks of their respective owners.

Screen shots used within this manual comply with the copyright guidelines of Microsoft Corporation.

[Use in situations which demand a high degree of safety]

This product has been developed, designed, and manufactured with the intention that it be used in general purpose office, personal, home and industrial situations. It was not developed, designed, and manufactured for use in situations (hereinafter High Safety Situations), such as control of the nuclear reactions in nuclear power plants, autopiloting of airplanes, air traffic control, operational control of mass-transport systems, life preserving medical devices, missile fire control and other military systems, etc., in which an extreme degree of safety is required, or for which there would be a direct risk to life and limb if, for some reason, such safety could not be guaranteed.

Please do not attempt to use this product in such High Safety Situations, unless you otherwise guarantee the required level of safety. FUJITSU and its associate companies will accept no responsibilty for and damages that may occur to you or any other third party resulting from such High Safety Situation use.

All Rights Reserved, Copyright (C) Fujitsu Limited 2000 - 2003.

How to Use This Manual

About this manual This Portalworks instruction manual is aimed at users new to Portalworks.

Who Should Read this manual This manual is intended for those who will install and operate Portalworks. · Knowledge of how to use a Web browser is assumed.

Contents

The following table describes the organization and contents of this manual.

Chapter Title Contents

1 Overview This chapter is an explanation of what kind of system you can construct using Portalworks.

2 Functions of Portalworks This chapter explains the main functions of Portalworks.

3 Constructing a Portalworks System

This chapter is an overview of the tasks required to install and operate Portalworks.

4 Operating and Managing Portalworks

This chapter is an overview of operating and managing Portalworks.

ii

Chapter Title Contents

- Glossary Explains the terms use in this manual.

Related manuals

This manual provides an overview of the Portalworks functions and tasks. For more detailed information, refer to the following manuals: · Interstage Portalworks Administrator's Guide

Referred to as Portalworks Administrator's Guide in this manual. · Interstage Portalworks User's Guide

Referred to as Portalworks User's Guide in this manual. · Interstage Portalworks Scenario Creator Guide

Referred to as Scenario Creator Guide in this manual. · Interstage Application Server Installation Guide.

Conventions used in this manual This manual uses the following conventions.

References to directory paths

Descriptions of file/folder (directory) paths in the text and window examples comply with Windows NT(R) Server. If you are using Solaris(TM) Operating Environment (hereinafter referred to as "Solaris OE")/Linux for your operating system, you should assume the Solaris OE/Linux equivalent description formats whenever the Windows formats are shown in this manual.

The contents of each operating system are included in case they differ.

Use of brackets ([ ])

Windows, menus, commands, buttons, tabs, combo boxes, pages, fields, check boxes, and keys are displayed in square brackets.

Example: [--] field

Notes

Important notes and tips are marked with the following symbols:

An important note is given like this.

Useful information is given like this.

Abbreviation of product names

The following is a list of the abbreviations used in this manual to refer to other products. Where necessary, the full name is used.

Windows (R)

The following is a list of how Windows products are abbreviated. Note that Windows NT (R) Server refers to both Windows NT (R) Server and Windows (R) 2000 Server or Windows Server(TM) 2003 if there is no difference in their usage, otherwise they are referred to separately.

Windows(R) refers to: · Microsoft(R) Windows(R) 95 operating system · Microsoft(R) Windows(R) 98 operating system · Microsoft(R) Windows NT(R) Workstation operating system Version 4.0 · Microsoft(R) Windows(R) 2000 Professional operating system · Microsoft(R) Windows(R) Millennium Edition operating system · Microsoft(R) Windows(R) XP Home Edition operating system · Microsoft(R) Windows(R) XP Professional operating system

iii

Windows NT (R) Server refers to: · Microsoft (R) Windows NT (R) Server 4.0 · Microsoft (R) Windows NT (R) Server Enterprise Edition 4.0

Windows (R) 2000 Server refers to: · Microsoft (R) Windows (R) 2000 Advanced Server · Microsoft (R) Windows (R) 2000 Server

Windows Server(TM) 2003 refers to: · Microsoft(R) Windows Server(TM) 2003 Standard Edition · Microsoft(R) Windows Server(TM) 2003 Enterprise Edition

Interstage

The following is a list of the abbreviations used in this manual to refer to other Interstage related products. Where necessary, the full name is used.

Function Name

Application servers provided by following servers. · Interstage Application Server · Interstage Application Server Plus · Interstage Application Server Plus Developer · Interstage Application Framework Suite · Interstage Apworks

Interstage Application Server or Interstage

1

Chapter 1 Overview

This chapter provides an overview of the types of system that can be constructed using Portalworks.

1.1 What is Portalworks?

Portalworks is a server-based software program that facilitates the construction of web-based corporate portals. It integrates large amounts of data from both inside and outside a corporation, as well as existing applications, and information systems. Portalworks facilitates the construction of corporate portals as a single gateway, tailored to your individual business needs.

This section discusses current problems with corporate business systems and describes the solutions offered by Portalworks.

1.1.1 Current Status of Corporate Portals

Today, the business environment both within and between corporations is drastically changing due to the rapid growth of Internet technology and changes in market environments. For a corporation to deal effectively with these changes in the commercial climate, and to profit, it is necessary to foster cooperation between your business and its customers and partners, and to have an effective corporate plan in place.

The key is to construct a business system that efficiently uses data and information stored both inside and outside your corporation. The three following problems must be taken into account before you construct such a system: · System interfaces

When accessing data stored in different formats in different places, users must identify what programs, systems, and formats to use when accessing data. This is not efficient.

· The distributed nature of information It is difficult to quickly find information that you need from the huge amount of information scattered around inside and outside of your corporation.

· Data is stored in different formats Because data is stored in different formats, it is difficult to collate and cross-reference results.

Because of the above problems, it takes a lot of work and adjustments to construct a service that integrates multiple related systems. The following diagram is a summary of the current situation:

1.1.2 Corporate portal provided by Portalworks

The aim of Portalworks is to construct a portal that is not only an information portal, but is also flexible and user-centered.

Using Portalworks provides an environment with the following features: · Integration of existing systems

You can define roles which specify the tasks that can be performed and information that can be viewed by each role. Each user is then assigned a role. Roles can be grouped together according to specific business

2

needs, and displayed hierarchically on the Portal Page. This means you can provide the integrated access environment best suited for each user.

· Quick access to necessary information The scenario function and the USP (both described below) can be used to retrieve information about multiple Web sites in a single operation. When sites requiring authentication information (for example, passwords) are accessed, Portalworks securely saves the authentication information for re-use in subsequent visits.

A portal constructed by Portalworks provides an integrated business environment with advanced functions as shown in the following diagram.

1.2 Portalworks features

This section is an overview of Portalworks features.

1.2.1 Advanced Architecture

Portalworks provides every user with information optimized to their business scenarios (task procedures and user information) and provides an access environment which is built on advanced components such as the brick service and Universal Service Plug (USP).

3

· Brick Services

This service distributes information according to the roles assigned to users and the needs of each user. · USP (Universal Service Plug-in)

Provides a connection to outside resources with a plug-in module that unites input and output using XML. You can access contents by integrating each USP.

1.2.2 Providing Suitable Work Environments

Portalworks provides an access environment that integrates information and services in the best format for users, using business scenarios (Processes and Data) and advanced technology.

This is called the IT desktop. By using the IT desktop, you can efficiently perform tasks that use multiple existing systems

4

· Brick Service

Distributes information necessary for each business scenario to each View (brick). It then composes and displays them on one screen. These bricks can be grouped according to the type of business they represent and displayed in a hierarchy.

· Personalization Portalworks supports the customization of the user interface, called the Portal page

· Seamless Cooperation with existing services User identifiers and passwords for disparate services can be set-up and managed to enable seamless access to multiple services.

· Categorize services by role and restrictions You can group services according to roles and limitations of users This enables you to provide integrated views by roles with restrictions enabling you to manage access rights.

1.2.3 Simple Integration with External Resources

Portalworks provides a plug-in (USP) to integrate with information and services outside of your corporation. Existing systems do not need to be modified to use this plug-in which provides seamless access from portal servers to outside resources.

1.2.4 Administrators and user roles

The Portalworks administrators, managers, and user roles are as follows: · Administrator

Manages the overall operation of Portalworks. · Service provider

Provides outside resources (information and services) that are linked by USPs. · Role manager

Manages roles that are assigned by administrator. · Group manager

Individually manages the role group hierarchy displays that are assigned by the administrator.

5

1.3 Portalworks Function Overview

This section is an overview of Portalworks functions.

1.3.1 Presentation Function

This function provides individual users with the IT desktop environment that best suits them. The presentation function is composed of the following functions: · Brick Service

Manages the layout of multiple bricks in one display window. · Personalization Function

Allows users to customize the contents to be displayed and the layout of their windows. · Role Function

Sets and provides services to users depending on their specified role. Roles can be grouped according to the type of business they represent and displayed in a hierarchy. This means that access to differing services can be restricted according to various business requirements.

· Authentication Function Based on the standard [JAAS (Java Authentication and Authorization service)] Java technology. LDAP server can be used for authentication instead of standard Portalworks authentication. A proxy logon function is provided that allows users to logon to the existing services with basic authentication, form authentication and Proxy server authentication. Also provided is a certificate management function, which is used when secure sites are accessed. This provides seamless access to information and services.

· User Information Management Function Easily manages user information, such as logon ID and password, and profile information.

· Window Customization Function This allows the administrator to control the degree of window customization allowed to each user. It also allows the administrator to customize the portal page of all users in a single operation.

Using the IT Desktop and User Roles

The role management function can be used by administrators to create a variety of roles and then to define the tasks that can be performed and information that can be viewed by each role.

Each user is then assigned one or more roles. Service providers define the services and data that are available to each user role. Once roles are assigned, users are restricted in the information they have access to. In addition, the role can be used to focus their attention on the relevant data. This helps to provide stable corporate policy in regard to access to information.

The services and data that each user can use are processed by a brick service and displayed in one window. Only the services and data that can be accessed by a user are processed. Users can change the layout and design of the window using the personalization function. They can also customize the window by adding a preferred service to the contents (as a Private Brick).

6

When there are a variety of possible businesses and services (roles), they can be grouped according to the role details, then displayed in a hierarchy on the portal page.

1.3.2 Information/Service Connector

This function creates and manages connections to existing information servers. Each connector is implemented as a plug-in which transforms XML data.

The following plug-ins are provided by default: · Web Server USP

A plug-in to view information stored on the Internet and Intranets. · Web To Host USP

A plug-in for connecting to mainframe and office computers.

1.3.3 Administrative Function

This function lets you easily specify the system settings to manage Portalworks.

The management functions include registering, modifying, or deleting users, starting and stopping systems, and setting operational parameters. In addition, the administrator can change the style of the portal page in a single operation. It also provides many log functions that are necessary for system maintenance.

This makes the administrator's job easier.

This function further facilitates ease of operation by making it possible to control the degree of window customization of each user as well as providing a logon policy (invalidating accounts due to illegal logons)

This allows the administrator to easily configure a secure environment

1.4 System Configuration When Using Portalworks

This section explains the recommended system setup when using Portalworks in an internet environment.

1.4.1 Using Portalworks in an Internet Environment

When using Portalworks in an Internet environment, it is recommended that a reverse proxy server be set up on a DMZ, and access to Portalworks be made through reverse proxy to the business server segment.

7

8

9

Chapter 2 Functions of Portalworks

This chapter explains the main functions of Portalworks.

2.1 Presentation Function

This function lets you customize the IT desktop environment so that it best suits the purposes of users and their defined roles.

2.1.1 Brick Service

The Brick Service arranges the output of applications in brick format and displays them in a window. Bricks from multiple applications can be integrated into one Web browser window.

The following is an example of a brick service:

2.1.2 Personalization Function

This function allows users to customize the contents and structure of a window. Users can change the IT desktop layout to suit their needs. The administrator can also control the level of customization allowed by each user through the Role Management and Window Customization functions. It also allows the administrator to customize the window style and layout of all users in one step.

10

2.1.3 Role Management Function

The role management function allows you to define roles that specify the tasks that can be performed and information that can be viewed by each role.

Each user is then assigned one or more roles. Administrators can provide services to only the users that need them. Users then have seamless access to services.

11

When there are multiple services (roles), the roles can be grouped. Roles that are grouped, are displayed on the portal page in a hierarchy. By grouping the roles according to business type or other relationship, the complexity of operations from large numbers of services can be reduced.

The Role Management function allows you to customize the portal pages of all of the users for each role.

2.1.4 Proxy Logon Function

Authentication information for each user (passwords and login names, etc.) can be saved for multiple services. The stored authentication information can then be used to automatically make subsequent logins.

12

2.1.5 Certificate admin function

The certificate admin function manages certificates that are sent by connecting to an encrypted site (that supports SSL). The certificate shows the user that the site that is connected to is a "safe" site.

2.1.6 User Information Management Function

This function is used to manage user profile information. User Profile Information includes the logon ID and password to log into Portalworks. It also includes basic information such as name and address.

2.1.7 Window Customization Function

The Window Customization function allows the portal pages to be customized. It also allows the style and design of a portal page to be changed for all users at once. Such customization may be done at a Page Level, Panel (Role) Level, or Group Level.

Page Level Customization

An administrator may restrict a user's ability to customize, while also customizing the following items at the page level: · Layout & design of the various areas of the logon & portal pages · Overall page layout & design · Role display order · Active role settings

13

Panel (Role) Level Customization

An administrator or role manager may customize the following items at the panel (role) level: · Brick layout · Brick status (default show/don't show in panel status) · Brick design

Group Level Customization

An administrator may customize the following items at the in group level: · Group roles / Group tab designs

2.2 Information/Service Connector

This function integrates outside resources (such as existing information and services) and allows access to all resources at once. It uses plug-in modules to access the interface of each outside resource, providing easy connection to external systems.

14

The following plug-in modules are provided by Portalworks as Information/Service Connector: · Web Server USP

A plug-in to view information stored on the Internet and Intranets. Web content can be retrieved by specifying a URL.

· Web To Host USP A plug-in for connecting to mainframe and office computers. This is a plug-in for connecting to mainframe and office computers that have been specified as Web based by Server2000. You can also perform host tasks from Portalworks windows.

2.3 Administrative Function

This function lets you specify system settings to easily manage Portalworks.

The management functions are performed from the GUI and include registering/changing/deleting users, starting/stopping systems, linking active sources, and setting operational parameters. The range of user customizations and the logon policy (such as disabling illegally logged on accounts) can be easily set. It also provides many log functions for system maintenance. These functions decrease the load on the administrator.

Business portals can be constructed quickly, thereby reducing the load on the administrator.

You can also retrieve log information that is necessary for system maintenance.

15

· Access Log This log includes a history of user logon/logoff and the start/end time of each service. The access log makes it possible to calculate how each user accesses the various services and how each service is collectively accessed.

· Execution Log This log includes error information, warning information, and progress information, as well as information on Portalworks service start times. The level of logging to this log can be set to Error Only, Error and Warning or All in the Administrative Function service.

16

17

Chapter 3 Constructing a Portalworks System

This chapter is an overview of the tasks required to design and install a Portalworks system.

3.1 Procedures Before Installation

This chapter explains the tasks required to install and operate Portalworks.

3.1.1 Overview

The tasks necessary for installing and operating Portalworks are performed in the following order:

3.1.2 Tasks Before Installation

The following tasks are necessary before installing Portalworks:

· Estimating target service users

One must consider which services to provide to which users. It is necessary to clarify end users, service management users, and users who require authentication processes depending on the nature of their tasks.

· Planning Portalview It is important to consider what kind of new services to provide using the existing tasks. It is recommended to take note where existing services need to be improved. This may include, for example, difficulties in managing the services and difficulties the user may have in using the service. After collecting this information, you can consider combining existing services into a single

18

· Grouping users Think about how to group users to use a new service. You can plan this when estimating target service users.

· Designing business scenarios Perform the following tasks based on the estimations of users and on what services you have selected:

- Designing roles Users in the same group will be assigned the same role. Plan which services to provide to which role.

The following point also needs to be considered: · Estimating disk space and memory needed

Use these operation plans to calculate how much disc space and memory will be needed on the server in order to run Portalworks. For detailed information about estimation, refer to the "Portalworks Administrator's Guide".

3.1.3 Installation

Install Portalworks and the necessary software to a server environment and check the operation.

Refer to "Interstage Application Server Installation Guide" for details.

3.1.4 Constructing the Operation Environment

This section explains how to construct the Portalworks operation environment. · Setting up the operating system environment

When using Windows NT (R) Server, optimize memory to improve the speed of processing. When using Solaris OE or Linux, the time zone and locale should be set. Refer to the "Portalworks Administrator's Guide" for more information.

· Setting up the Portalworks operation environment Construct the operation environment based on the pre-installation plans. The following tasks are involved in constructing the operation environment:

- Managing users - Setting environment for Information/Service Connector - Managing roles

Refer to the "Portalworks Administrator's Guide" for details on these tasks.

3.1.5 Operation and Maintenance

Administrators need to operate and maintain Portalworks, so that it functions correctly. The following is a list of operation and maintenance tasks: · View log information and change system status, monitoring options and log options · Backup/Restore

19

Chapter 4 Operating and Managing Portalworks

This chapter is an overview of operating and managing Portalworks.

4.1 Overview of Managing Portalworks

This section is an overview of managing Portalworks.

4.1.1 Administrative Function Service

The Web based Administrative Function Service is used to administer Portalworks. The following is an example of Administrative Function Service:

The next section is an overview of the Administrative Function Service. Refer to the "Portalworks Administrator's Guide" for instructions about operating the Administrative Function Service.

4.1.2 System Management

You can set and view Portalworks system information and settings.

The following system management tools are available: · Status monitor

Starts and stops Portalworks. It also can be used to temporarily suspend user logon. · Access Control

Controls the following information about user access: - Maximum number of concurrent users (sessions). - Automatic logoff time. - Multiple Logons. · Proxy server

A server can be specified to view data via a proxy by specifying the proxy server's URL. · Own server

A server can be specified as your own server by specifying an alias name, the server name, and the port number of the server.

· Self-registry When authenticating Portalworks, specify whether or not to use the self-registry function. This function allows users who do not have accounts in Portalworks to register an account.

· Custom field You can modify the names of user information custom fields.

· Setting HTTPS Sets the path for CA Certificates, which is necessary when communicating through HTTPS. Secure communication environment can be ensured with HTTPS communication.

· Selecting Language Changes the default language which displays the Administrative function service and portal page. This function

20

can only be used when "Use multiple languages" is selected during Portalworks installation. · Authentication server

If using LDAP server authentication, any changes made to the LDAP server's IP address, etc. will be reflected in Portalworks.

· LDAP-related support If using LDAP authentication, Portalworks custom items support LDAP attributes.

· Logon policy If using Portalworks authentication, sets a logon policy (handling of login failures, setting of password expiry dates, etc.)

· Post-logoff URL setting User can decide what web page is to appear in the browser after logging off Portalworks.

· Window customization (Logon page and portal page) Customizes the style and design of the logon page and the portal page.

4.1.3 User Management

Portalworks supports two authentication systems: Portalworks authentication, LDAP server. If Portalworks authentication is used, user management is via the Administrative Function Service. Otherwise refer to "4.2 Managing Users by LDAP Server".

The following tasks must be performed to use Portalworks authentication: · Creating user information

Register a Portalworks logon ID and password. You can also assign roles to each user. · Viewing and deleting user information

User information stored in Portalworks can be deleted if it is no longer necessary. The user cannot use Portalworks thereafter.

· Modifying user information You can modify user profiles.

· Displaying a list of all users currently logged on Displays a list of all users currently logged onto Portalworks. (Can also be used when using a LDAP server.)

· Unlock user accounts Unlocks accounts that have been locked according to the conditions of the system administration logon policy. (Can also be used when using a LDAP server.)

4.1.4 Service Management

You can manage the information necessary for using services.

The following service management tools are available: · Registering an alias, modifying an alias, referencing/deleting an alias

You can register new aliases, and modify or delete existing aliases in the Portalworks system. New services are created based on already registered USPs and scenarios.

· Registering scenarios, modifying scenarios, referring/deleting scenarios You can register, modify, refer or delete scenarios in the Portalworks system.

· USP lists A list of USPs can be displayed. Each USP can be managed from this list.

· Registering USPs, modifying USPs, referencing/deleting USPs You can register, modify, refer or delete a USP in the Portalworks system.

4.1.5 Role Management

Manages the roles that can be assigned to Portalworks users.

The following role management tasks can be done: · Registering, modifying, and deleting roles

You can register, modify or delete roles in the Portalworks system. · Registering, modifying, and deleting groups

You can register, modify or delete groups in the Portalworks system. You can register more than one role/group in a group.

4.1.6 Log Management

You can manage the logs stored in the Portalworks system.

The following log management tasks can be performed: · Setting access log

You can specify whether or not to keep a log of user logon/logoff and starting/stopping of services.

21

· Setting execution log You can specify whether or not to output information such as errors, warnings and information messages that occurred during operation.

4.2 Managing Users by LDAP Server

After registering Portalworks users in an LDAP server, you can authenticate users with the LDAP server authentication process.

Portalworks supports the following LDAP servers: If one of these LDAP servers has already been set, you can use that LDAP server. For detailed information about user management tasks, refer to the appropriate LDAP server guide. · InfoDirectory (V1.0L10) · Netscape (R) Directory Server Version. 3.11 (compatible only with Windows NT (R)) When using LDAP authentication, Portalworks customized items can support LDAP attributes. Related items can also be used as search topics.

22

23

Glossary

Access log

This is a log for viewing the access records of the Portalworks system. It includes output of user logon and logoff status as well as start and end usage of each service. This information is output as a record and saved in the log. An administrator can view each user's usage status of Portalworks system by accessing this log file.

Administrative function

A series of functions for administrating Portalworks.

Administrative function service

A service that provides a series of functions for administrating Portalworks.

Administrator

A person responsible for managing a Portalworks installation.

Alias

An alternative name.

Applet Proxy

A proxy function that is implemented through an Applet. It is downloaded from a server running Portalworks, and run on a browser window that accesses Portalworks.

ASCII character

An alphanumeric character represented in the American Standard Code for Information Interchange system.

Authentication server

A server that performs logon authentication. In Portalworks, in addition to the default Portalworks authentication system, an LDAP server (such as InfoDirectory) can be used for authentication.

24

Automatic logoff time

The period of time after which, if a user performs no actions in Portalworks, that user is automatically logged off.

Basic authentication

An authentication method for HTTP protocol level. From the user's point of view, basic authentication is a page that displays a browser window for entering a user ID and a password.

Brick

A basic (minimum) unit used for window display in Portalworks. A brick is displayed in a browser. A brick is rectangular in shape and has a title bar.

Business logic

This indicates business procedures and usage information and roles of people.

Certificate

When connecting to encrypted sites compatible with SSL, it informs the users that the site is secure.

Contents

This indicates information and services that are displayed in each brick of a portal page.

Custom field

A field for adding individual user information (name and address) displayed on the portal page [Profile] in addition to the standard fields.

Custom items

Each item that is in a custom field.

Encrypted site

A site in which data is encrypted so that a third person cannot modify the contents during data communication.

Execution log

When Portalworks is running, it outputs error information, warning information and other information to the Windows

25

NT(R) Server event log, where it can be viewed by an administrator. In Solaris or Linux, this information is output to syslog. The level of output can be set in the administrative function service.

Form authentication

An authentication method that uses service-specific logon screens created with HTML form tags. From the user's point of view, when the form authentication page is accessed, service-specific logon screens are presented for the user to enter their user ID and password.

Group administrator

Administrator of role groups. A Group administrator is appointed by the administrator.

Groupware

Software used to support group work. Examples are Teamware Office, Lotus Notes/Domino and Microsoft(R) Exchange.

HTML

Hyper Text Markup Language. The standard language for creating documents for use on the World Wide Web.

HTML file

A document created in HTML. The search service supports this format.

HTTP

HyperText Transfer Protocol.

A protocol for sending and receiving documents written in HTML from a Web server to a Web client.

Information/Service connector

It provides an environment for connecting to the existing external information and services (business applications and database) by a format of plug-in (USP) that is easy to set.

Internet

The name given to the worldwide computer network connected by TCP/IP-based network protocols.

26

Intranet

An internal network system that links a group of computers within a company.

Java

A platform independent programming language developed by Sun Microsystems.

JSP

JavaServer Pages. A technology developed by Sun Microsystems and IBM that can directly embed Java codes into HTML and XML documents. JSP is compiled and executed when it is called and the results are sent to a Web browser in the form embedded into HTML and XML documents.

LDAP

Lightweight Directory Access Protocol. A standard Internet protocol for accessing a directory database.

Link

Click an anchor to display a linked window. Usually, the link is in blue and underlined.

Logoff

This means that a user ends the current Portalworks session, terminating the connection between the client and the server.

Logon

Enables the User to start a Portalworks session (establishes a connection between the client and server).

Logon policy

Rules to logon to Portalworks that the administrator applies for security such as the number of password entry attempts and the period of password validity.

Page

The largest area displayed in a Portalworks window in a browser.

27

Page root

A common display area in a page. This is displayed outside of a brick display area.

Panel

A window structure unit that is created for each role unit. A brick is placed in a panel according to the layout. Layout can be specified for each panel.

Panel tab

A tab that is attached to each panel. A role name is written in each panel tab.

Plug-in

A file that adds functions to applications.

Portal

An entry (portal) for accessing various kinds of distributed information.

Portal page

This indicates a Web window that is provided by Portalworks.

Portalworks

One of the Interstage Portal Server packages. Portalworks is software that supports the construction of a corporate portal. It provides easy access to information that is distributed inside and outside of a corporation and also provides interactive usage that corresponds to various business activities.

Portalworks authentication

Authentication provided by Portalworks. In Portalworks, in addition to the default Portalworks authentication system, an LDAP server (such as InfoDirectory) can be used for authentication.

Presentation function

A function that arranges user views of Portalworks according to system definition and user settings.

28

Proxy logon function

When users need to use services on the network, this function allows Portalworks to logon to services instead of users.

Proxy server authentication

An HTTP protocol level authentication method. Proxy server authentication is used to limit access to specific services to specific users. From the user's point of view, when the authentication page is accessed, a browser window is presented for the user to enter their user ID and password.

Public role

A role to which all users of Portalworks are set is called a public role. A public role is automatically created when installing Portalworks.

Repository

A database for storing detailed information of users and management information of roles and services. The database provided by Portalworks or an outside database can be used as a repository.

Role (name)

A role is a unit that controls services that are available to users depending on the organization system (for example, job position, job type) and available tasks. An administrator or a role manager defines roles.

Role-group

A set of more than one roles groups together based on various relationships.

Role-group hierarchy display

Groups multiple role-groups in business units and other relationships.

Panels on portal pages are displayed in hierarchy in these group units.

Role management function

A function that manages roles defined by Portalworks.

Role manager

A person who manages specific roles. An administrator sets a role manager.

29

Self-registry

A function that allows users to register their own account. The administrator can define whether or not this function is available.

Service

A series of business functions that are provided to users through a Portal Page is referred to as a service.

Servlet

This is a Java program that is like an applet in a server that is called by HTTP. It runs in Servlet execution environment added onto a server.

Session Bean

EJB component in which business process and business logic are implemented. It is an object that exists only in sessions.

SSL

Secure Sockets Layer. An HTTP protocol that adds a Netscape security function.

URL

Universal Resource Locator. An address standard that is used on the World Wide Web. It contains the server name and the path to a file on the server.

User

A person who uses each service provided by Portalworks from a Web browser.

User management function

A function that manages user information (such as by creating, updating, and deleting entries).

User information

Basic personal information, including the logon ID and password used to access Portalworks, as well as the user's name and address.

30

USP

Universal Service Plug-In. By embedding outside resources (information and services) in Portalworks, this function makes seamless access to outside resources possible.

Web application

A general term for HTTP and HTML-based applications (CGI, ASP, Servlet and JSP that have a URL, and those that perform input and output by HTTP/HTML).

Web browser

A browser that views Internet sites. Portalworks is accessed through Web browsers.

Web server USP

A USP that enables the handling of information distributed throughout the Internet and Intranet, in Portalworks bricks.

Web To Host USP

A plug-in for connecting to mainframe and office computers. This USP can connect to mainframe and office computers that are Web-based, which is done by Server2000.

Web USP

This indicates Web server USP.

Window Customization Function

A function that allows the administrator to customize style and design of the guest window and post logon window.