Rocket SB/XA SystemBuilder User guide
Reklama
Reklama
Rocket SystemBuilder
Extensible Architecture
SB/XA Getting Started
Version 6.2.4
March 2014
SBX-624-XA-IM-01
2
Notices
Edition
Publication date: March 2014
Book number:
SBX-624-XA-IM-01
Product version: Rocket SystemBuilder Extensible Architecture v6.2.4
Copyright
© Rocket Software, Inc. or its affiliates 1989-2014. All Rights Reserved.
Trademarks
Rocket is a registered trademark of Rocket Software, Inc. For a list of Rocket registered trademarks go to: www.rocketsoftware.com/about/legal . All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names of their respective owners.
Examples
This information might contain examples of data and reports. The examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
License agreement
This software and the associated documentation are proprietary and confidential to Rocket
Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license.
Note: This product may contain encryption technology. Many countries prohibit or restrict the
use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when exporting this product.
Contact information
Website: www.rocketsoftware.com
Rocket Software, Inc. Headquarters
77 4 th
Avenue, Suite 100
Waltham, MA 02451-1468
USA
Tel: +1 781 577 4321
Fax: +1 617 630 7100
Contacting Global Technical Support
If you have current support and maintenance agreements with Rocket Software, you can access the Rocket Customer Portal to report and track a problem, to submit an enhancement request or question, or to find answers in the U2 Knowledgebase. The Rocket Customer Portal is the primary method of obtaining support.
To log in to the Rocket Customer Portal, go to: www.rocketsoftware.com/support
If you do not already have a Rocket Customer Portal account, you can request one by clicking
Need an account? on the Rocket Customer Portal login page.
Alternatively, you can contact Global Technical Support by email or by telephone:
Email:
Telephone:
North America
United Kingdom/France
Europe/Africa
Australia
New Zealand
+1 800 729 3553
+44 (0) 800 773 771 or +44 (0) 20 8867 3691
+44 (0) 20 8867 3692
+1 800 707 703 or +61 (0) 29412 5450
+0800 505 515
3
Table of Contents
Chapter 1
Chapter 2
Chapter 3
Chapter 1: Components of SB/XA
What is SB/XA? . . . . . . . . . . . . . . . . . . .
SB/XA Application Server . . . . . . . . . . . . . .
SB/XA Communications Server . . . . . . . . . . . .
SB/XA Presentation Components . . . . . . . . . . .
Chapter 2: Planning an implementation of SB/XA
A road map of implementation tasks . . . . . . . . . . . .
Planning your implementation of SB/XA . . . . . . . . . .
What is the best configuration of components? . . . . . . .
Two server computers with multiple clients . . . . . . . .
One server computer with multiple clients . . . . . . . .
Three computers . . . . . . . . . . . . . . . . .
Two computers . . . . . . . . . . . . . . . . . .
One computer . . . . . . . . . . . . . . . . . .
Alternative configurations . . . . . . . . . . . . . .
Chapter 3: Installing SB/XA components on Windows
Guidelines for upgrades . . . . . . . . . . . . . . . .
Setting up before you install . . . . . . . . . . . . . . .
Setting up the environment to support SB/XA . . . . . . .
Checking the installed version of SB/XA components . . . .
Determining if you must remove files and components . . . .
Removing existing files and components . . . . . . . . .
Installing components of SB/XA on Windows . . . . . . . .
Installing SB/XA Presentation Components . . . . . . . .
Installing SB/XA Communications Server . . . . . . . .
Installing SB/XA Application Server on Windows . . . . .
Installing MAPI for messaging in the XUI clients. . . . . . . .
Post-installation tips . . . . . . . . . . . . . . . . .
Table of
Contents
Chapter 4
Chapter 5
Chapter 6
Exporting/importing SBClient settings . . . . . . . . .
Renaming the SB administration account . . . . . . . .
Setting up an environment with multiple SB accounts . . . .
Starting SB/XA Application Server from U2 . . . . . . .
Edition-specific information for Windows installations . . . . .
UniData compilation mode . . . . . . . . . . . . .
UniData environment options . . . . . . . . . . . .
Restrictions in the Windows editions . . . . . . . . . .
Chapter 4: Installing SB/XA Application Server on UNIX
Setting up before you install . . . . . . . . . . . . . .
Setting up the environment to support SB/XA Application Server on
UNIX . . . . . . . . . . . . . . . . .
Installing SB/XA Application Server on UNIX . . . . . . . .
Completing the installation checklist . . . . . . . . . .
Downloading installation files . . . . . . . . . . . .
Installing SB/XA Application Server files . . . . . . . .
Installation troubleshooting . . . . . . . . . . . . .
Renaming the SB account . . . . . . . . . . . . . .
Multiple SB accounts . . . . . . . . . . . . . . .
Additional information . . . . . . . . . . . . . . . .
Initiating SB/XA Application Server . . . . . . . . . .
Compilation mode (UniData-based systems) . . . . . . .
Recoverable files . . . . . . . . . . . . . . . . .
Configuring SB Print Management (UniData) . . . . . . . .
Chapter 5: Methods of deploying SB/XA Presentation Components
Deployment of SB/XA Presentation Components . . . . . . .
ClickOnce deployment . . . . . . . . . . . . . . .
Alternative methods of deployment . . . . . . . . . .
Chapter 6: Setting up application connections and configuring clients
Setting up application connections . . . . . . . . . . . .
Why use Single Sign-On? . . . . . . . . . . . . . .
Enabling application connections . . . . . . . . . . .
Centralized client configuration . . . . . . . . . . . . .
Hiding the Options button . . . . . . . . . . . . .
Customizing configuration on the client . . . . . . . . . .
Calling the XUI clients from an application . . . . . . . . .
5 SB/XA Getting Started
Chapter 7
Chapter 8
Running a process from a shortcut . . . . . . . . . . .
Chapter 7: Configuring and managing SB/XA Communications Server
Listing users logged on to SB/XA Communications Server . . . .
Stopping and starting SB/XA Communications Server . . . . .
Stopping SB/XA Communications Server . . . . . . . .
Starting SB/XA Communications Server . . . . . . . .
Overview of authentication types. . . . . . . . . . . . .
Windows authentication . . . . . . . . . . . . . .
SBXAUserNamePassword authentication . . . . . . . .
WindowsUserNamePassword authentication . . . . . . .
Setting up certificates to authenticate clients . . . . . . . . .
Installing the required tools . . . . . . . . . . . . .
Changing the logon properties of the communications service .
Creating a signing certificate . . . . . . . . . . . . .
Creating a server certificate . . . . . . . . . . . . .
Configuring SB/XA Communications Server . . . . . . .
Installing the root certificate on the client computer . . . . .
Configuration for SB/XA Services . . . . . . . . . . .
Chapter 8: Setting up National Language Support in SB/XA for
UniVerse NLS
Overview of National Language Support in SB/XA for UniVerse NLS 8-3
Software requirements . . . . . . . . . . . . . . .
Limitations . . . . . . . . . . . . . . . . . . .
Enabling an SB instance for NLS . . . . . . . . . . . . .
6 SB/XA Getting Started
Chapter 1: Components of SB/XA
Chapter
1
What is SB/XA? . . . . . . . . . . . . . . . . . .
SB/XA Application Server . . . . . . . . . . . . .
SB/XA Communications Server . . . . . . . . . . .
SB/XA Presentation Components . . . . . . . . . . .
This chapter provides an introduction to the components of SystemBuilder
Extensible Architecture (SB/XA).
■
1-2 SB/XA Getting Started
What is SB/XA?
SystemBuilder Extensible Architecture (SB/XA) is an application development tool for building client applications that run on SB accounts on the UniData or UniVerse database server.
SB/XA consists of the following components:
■
■
■
The role of each SB/XA component is described briefly below.
1-3
SB/XA Application Server
SB/XA Application Server is functionally equivalent to SB+ Server in previous versions. The key difference is that SB/XA Application Server is a component of the larger product SB/XA, rather than a standalone product sold separately on its own.
In the SB/XA system architecture, the SB/XA Application Server component resides in the lowest layer, as highlighted in bold in the illustration below.
SB/XA Application Server is a BASIC application that runs on top of the
UniData or UniVerse database server. It runs UniBasic or UniVerse BASIC commands that read and write data to records in SB accounts. An SB account is a SystemBuilder-enabled UniData or UniVerse (U2) account that resides on the database server.
1-4 SB/XA Getting Started
Planning your implementation of this component
The SB/XA Application Server component is available for Windows and
UNIX platforms. You must install SB/XA Application Server on the same computer on which you are running the UniData or UniVerse database server to enable communications and the ability to exchange data.
Your decision on whether to run SB/XA Application Server and the database server on Windows or UNIX is a factor in determining where other components can be placed.
For diagrams and help on planning how to distribute the components of
SB/XA across your network, see Chapter 2,
“Chapter 2: Planning an implementation of SB/XA.”
SB/XA Communications Server
A second component, SB/XA Communications Server, resides in the middle layer of the SB/XA system architecture, as highlighted in bold in the illustration below.
1-5
SB/XA Communications Server is also known as the “middle tier.” It is the middleware server software that enables communications between client applications and SB/XA Application Server on the UniData or UniVerse database server.
SB/XA Communications Server provides a set of services for communicating with SB/XA Application Server on the database server, including the runtime service.
In a production environment, SB/XA Browser Client or SB/XA Rich Client connects to the SB/XA Communications Server run-time service, which establishes communication with SB/XA Application Server. SB/XA
Application Server then runs UniBasic or UniVerse BASIC commands in SB accounts on the UniData or UniVerse database server.
Planning your implementation of this component
SB/XA Communications Server is built on the Microsoft .NET Framework and Windows Communication Foundation (WCF). Because it relies on
Windows technologies, this component is available on Windows platforms only.
■
■
All Windows Components – If you plan to run SB/XA Application
Server and the UniData or UniVerse database server on a Windows computer, SB/XA Communications Server can reside on the same
Windows computer as the database server or on a different Windows computer.
UNIX/Windows Components – If you plan to run SB/XA
Application Server and UniData or UniVerse on a UNIX platform, you must install SB/XA Communications Server on a different server computer that runs on Windows.
For diagrams and help on planning how to distribute the components of
SB/XA across your network, see Chapter 2,
“Chapter 2: Planning an implementation of SB/XA.”
1-6 SB/XA Getting Started
SB/XA Presentation Components
The SB/XA Presentation Components, also known as the “clients,” are the
SB/XA Browser Client and SB/XA Rich Client. They present the SB developed application to users in a Web browser window or as a rich client application that runs natively on the user’s computer. These components reside in the upper layer of the SB/XA system architecture, as highlighted in bold in the illustration below.
Planning your Implementation of these components
The SB/XA Presentation Components are available for Windows platforms only. They can be installed on the same computer as other Windows components or on multiple computers across your network.
For diagrams and help on planning how to distribute the components of
SB/XA across your network, see Chapter 2,
“Chapter 2: Planning an implementation of SB/XA.”
1-7
Deploying SB/XA Presentation Components
For a discussion of ClickOnce technology and other options for deploying the
SB/XA Presentation Components to client computers in your network, see
Chapter 6,
“Chapter 5: Methods of deploying SB/XA Presentation
1-8 SB/XA Getting Started
Chapter 2: Planning an implementation of SB/XA
A road map of implementation tasks . . . . . . . . . . .
Planning your implementation of SB/XA . . . . . . . . . .
What is the best configuration of components? . . . . . .
Two server computers with multiple clients . . . . . . .
One server computer with multiple clients . . . . . . . .
Three computers . . . . . . . . . . . . . . . . .
Two computers . . . . . . . . . . . . . . . . .
One computer . . . . . . . . . . . . . . . . . .
Alternative configurations . . . . . . . . . . . . .
Chapter
2
This chapter provides a discussion on planning your implementation of
SystemBuilder Extensible Architecture (SB/XA).
■
■
A road map of implementation tasks
Planning your implementation of SB/XA
2-2 SB/XA Getting Started
A road map of implementation tasks
You’re ready to get set up and running on SB/XA, but where do you begin?
Before you install software components, some initial planning and setup are required. The following list provides a master plan of tasks to be accomplished when you set up the product for the first time.
1.
2.
3.
4.
5.
Learn about the role of each component of SB/XA.
For information, see Chapter 1, “Chapter 1: Components of SB/XA.”
Plan your implementation of SB/XA.
Components can be installed on one computer or distributed across multiple computers. For a discussion of various implementation strategies, see
“Planning your implementation of SB/XA” on page 2-
Remove old files and components.
For instructions on removing old files and components from
previous installations of SB/XA, see “Removing existing files and components” on page 3-10.
Set up the environment to support Windows components of SB/XA.
SB/XA Application Server can be installed on Windows or UNIX platforms. However, the SB/XA Presentation Components and
SB/XA Communications Server are available only on Windows platforms.
For information on setting up the required hardware and software to support components of SB/XA on Windows platforms, see
“Setting up the environment to support SB/XA” on page 3-4.
Install Windows components of SB/XA.
SB/XA Communications Server and SB/XA Presentation
Components must be installed on Windows platforms. You may also install SB/XA Application Server on Windows. For instructions, see
“Installing components of SB/XA on Windows” on page 3-14.
2-3
2-4 SB/XA Getting Started
6.
7.
8.
9.
Set up the environment to support SB/XA Application Server on
UNIX, if applicable.
For information on setting up the required hardware and software to support SB/XA Application Server on UNIX platforms, see
“Setting up the environment to support SB/XA Application Server on UNIX” on page 4-3.
Install SB/XA Application Server on UNIX, if applicable.
For instructions, see
“Installing SB/XA Application Server on
Deploy the SB/XA Presentation Components to client computers.
Learn about ClickOnce deployment and alternatives for deploying the SB/XA Browser Client and SB/XA Rich Client files to one or more Windows-based computers.
For information, see Chapter 5,
“Chapter 5: Methods of deploying
SB/XA Presentation Components.”
Set up Single Sign-On parameters.
Single Sign-On is an optional feature for reducing the number of steps required to log on to your SB developed applications and connect them to SB/XA Application Server. For step-by-step
Planning your implementation of SB/XA
There is a difference between choosing a method to deploy SB/XA software to computers at your site and deciding which computers will run each component of the product.
In this chapter, we focus only on the first task on your checklist: planning where to install the components of SB/XA, or how to distribute the components of SB/XA across the computers in your network.
What is the best configuration of components?
The components of SB/XA can be installed on one computer or distributed to multiple computers at your site. There are many possible ways to disburse the components of SB/XA across your network; some basic configurations are illustrated in the figures in this section. Your goal is to choose a configuration of components that makes the best use of available computer resources and provides optimal service to SB/XA users.
Your design should take into account several factors, including the number of SB/XA users, the number of computers available for components of
SB/XA, the operating system(s) you plan to use, the disk space available for software on each computer, and whether you want to run all server software on one computer or run SB/XA Application Server and the database server on one computer and SB/XA Communications Server on another.
2-5
Two server computers with multiple clients
In the most typical configuration for a UniData or UniVerse production system, SB/XA components are installed on two server computers and multiple clients.
Figure 1-1 Two servers, multiple clients (Windows/UNIX or Windows only)
This configuration works if you use a combination of Windows and UNIX operating environments or an all-Windows environment.
As shown here, the database server (UniData or UniVerse) and SB/XA
Application Server are installed on one server computer (Windows or UNIX).
SB/XA Communications Server is installed on a second server computer
(Windows). The SB/XA Presentation Components, or clients (SB/XA
Browser Client or SB/XA Rich Client), are installed on multiple PCs and laptops (Windows).
2-6 SB/XA Getting Started
One server computer with multiple clients
In another typical implementation of a production system, SB/XA components are installed on one server computer and multiple clients.
Figure 1-2 One server, multiple clients (Windows only)
This configuration is possible only in an all-Windows operating environment.
As illustrated above, the database server (UniData or UniVerse), SB/XA
Application Server, and SB/XA Communications Server are all installed on one server computer (Windows). The SB/XA Presentation Components
(SB/XA Browser Client or SB/XA Rich Client) are installed on multiple PCs and laptops (Windows).
2-7
Three computers
If you are setting up a test or development system, you might distribute the server components onto two computers and use a third computer for the client.
Figure 1-3 Three computers (Windows/UNIX or Windows only)
This arrangement is possible if you use a combination of Windows and UNIX operating environments or an all-Windows environment.
As shown here, the database server (UniData or UniVerse) and SB/XA
Application Server are installed on one server computer (Windows or UNIX).
SB/XA Communications Server is installed on a second server computer
(Windows). The SB/XA Presentation Components (SB/XA Browser Client or
SB/XA Rich Client) are installed on a single PC or laptop (Windows).
2-8 SB/XA Getting Started
Two computers
Windows-UNIX or Windows only
For a test or development system, you can limit your hardware to two computers by installing the database server and SB/XA Application Server on one computer, and SB/XA Communications Server and the Presentation
Components on another.
Figure 1-4 Two computers (Windows/UNIX or Windows only)
This design can be implemented on a mix of Windows and UNIX platforms or on two Windows computers.
As illustrated above, the database server (UniData or UniVerse) and SB/XA
Application Server are installed on one server computer (Windows or UNIX).
SB/XA Communications Server and the SB/XA Presentation Components
(SB/XA Browser Client or SB/XA Rich Client) are installed on a single PC or laptop (Windows).
2-9
Windows only
As an alternative for a two-computer design, you might put all the server software on one computer and use a second computer for the client.
Figure 1-5 Two computers (Windows only)
This design can be used only if both computers run on Windows platforms.
As shown here, the database server (UniData or UniVerse), SB/XA
Application Server, and SB/XA Communications Server are installed on one server computer (Windows). The SB/XA Presentation Components (SB/XA
Browser Client or SB/XA Rich Client) are installed on a single PC or laptop
(Windows).
2-10 SB/XA Getting Started
One computer
For a test or development system, you might install all components of SB/XA on one computer.
Figure 1-6 One computer (Windows only)
As illustrated here, the database server (UniData or UniVerse), SB/XA
Application Server, SB/XA Communications Server, and the SB/XA
Presentation Components (SB/XA Browser Client or SB/XA Rich Client) are all installed on a single Windows-based computer.
This compact installation of all components on the same computer is possible only if the computer runs on Windows.
Alternative configurations
Figures 1-1 through 1-6 show only the most basic configurations. However, you may be planning a more complex implementation of SB/XA, using additional computers.
2-11
As an example, you may run SB/XA Application Server in multiple environments, such as development, test, and production. In this case, you might install the database server and SB/XA Application Server on three computers—one for each environment.
Figure 1-7 Development, test, and production environments
In another scenario, you might want to install SB/XA Communications
Server on two computers so data is accessible through a redundant resource in the event of a hardware failure.
If you need help with configuring a complex implementation of SB/XA, please contact U2 Technical Support to request assistance.
2-12 SB/XA Getting Started
2
Chapter 3: Installing SB/XA components on Windows
Guidelines for upgrades. . . . . . . . . . . . . . . .
Setting up before you install . . . . . . . . . . . . . .
Setting up the environment to support SB/XA . . . . . .
Checking the installed version of SB/XA components . . . .
Determining if you must remove files and components . . .
Removing existing files and components . . . . . . . .
Installing components of SB/XA on Windows . . . . . . . .
Installing SB/XA Presentation Components . . . . . . .
Installing SB/XA Communications Server . . . . . . . .
Installing SB/XA Application Server on Windows . . . . .
Installing MAPI for messaging in the XUI clients . . . . . . .
Post-installation tips . . . . . . . . . . . . . . . . .
Troubleshooting installation issues . . . . . . . . . .
Exporting/importing SBClient settings . . . . . . . . .
Renaming the SB administration account . . . . . . . .
Setting up an environment with multiple SB accounts . . . .
Starting SB/XA Application Server from U2 . . . . . . .
Edition-specific information for Windows installations . . . . .
UniData compilation mode . . . . . . . . . . . . .
UniData environment options . . . . . . . . . . . .
Restrictions in the Windows editions . . . . . . . . . .
Chapter
3
This chapter provides instructions for setting up the environment to support
SB/XA version 6.x and for installing components of the product on
Windows.
■
■
■
■
■
■
❑
❑
Setting up the environment to support SB/XA
Checking the installed version of SB/XA components
❑
❑
Determining if you must remove files and components
Removing existing files and components
Installing components of SB/XA on Windows
❑
❑
Installing SB/XA Presentation Components
Installing SB/XA Communications Server
❑
Installing SB/XA Application Server on Windows
Installing MAPI for messaging in the XUI clients
Edition-specific information for Windows installations
3-2 SB/XA Getting Started
Guidelines for upgrades
The SB/XA version number consists of four elements separated by dots. For example,
SB/XA v6.2.2.4220 consists of:
version_number.release_number.patch_level.build_number
The installer can perform an upgrade only if any of the first three elements of the new version number is greater. For example, v6.1.3.3330 can be upgraded to: v6.1.4.xxxx, or v6.2.0.xxxx, or v7.1.0.xxxx (when it becomes available)
The program does not check for a difference in the fourth element of the version number (the build number), so it cannot perform an upgrade from a lower build to a higher build of the same release. For example,
SB/XA v6.2.0.4048 (a Beta version) cannot be upgraded to
SB/XA v6.2.0.4056 (a General Availability (GA) version) because only the fourth element is greater.
If you installed a Beta or Early Adopter Program (EAP) version, you must remove old files and components so that you can perform a clean installation of the GA version.
Related Links
Checking the installed version of SB/XA components
3-3
Setting up before you install
Before installing components of SystemBuilder Extensible Architecture
(SB/XA) on Windows, complete the following tasks:
■
■
■
■
Setting up the environment to support SB/XA
Checking the installed version of SB/XA components
Determining if you must remove files and components
Removing existing files and components
Setting up the environment to support SB/XA
Before you copy the SB/XA Presentation Components (client files), install
SB/XA Communications Server, or install SB/XA Application Server on
Microsoft Windows platforms, complete the following tasks.
Procedure
1.
2.
3.
4.
Check that you have the hardware required to support SB/XA components on Windows. See
“Hardware requirements” on page 3-
Be sure the computer’s operating system supports SB/XA components on Windows. See
“Operating system requirements” on page 3-6.
Make sure you have the database server software required for
compatibility with SB/XA components on Windows. See “Database server requirements” on page 3-6.
Be sure you have other software that is compatible with this version
of SB/XA. See “Software requirements” on page 3-7.
3-4 SB/XA Getting Started
Hardware requirements
This section details the amount of hard disk space and other hardware requirements for components of SB/XA on Windows.
Component
SB/XA Presentation Components
■
SB/XA Browser Client
■
SB/XA Rich Client
To run SB/XA Presentation Components, the computer must have a minimum of 1GB of
RAM and a 128-MB graphics card.
SB/XA Communications Server
To run SB/XA Communications Server, the computer must have a minimum of 1GB of
RAM.
SB/XA Application Server for UniData
■
Basic
■
With globally cataloged programs
(UniData only)
Hard disk space required
3MB
3MB
10MB
36MB
Additional 8MB
30MB
SB/XA Application Server for UniVerse
SB/XA Application Server for UniVerse NLS
30MB
Hardware requirements: SB/XA Windows components
Note:
SB accounts are named differently in the UniData edition than in the
UniVerse or UniVerse NLS edition. In the UniVerse or UniVerse NLS edition, the account names include a + (plus) sign; for example, SB+ and SB+.DEFN. In the
UniData edition, the accounts are named without the + sign; for example, SB and
SB.DEFN
. The latter method of notation is used throughout this manual for the purposes of brevity.
3-5
Operating system requirements
The following table lists the operating systems that support components of
SB/XA on Windows. SB/XA works best with the recommended components, but you may test SB/XA on earlier service packs at your own discretion. SB/XA is not supported on the beta version of any operating system.
Operating System Recommended
Windows Server 2008
Windows Server 2012 *
Windows 7
R2 Service Pack 1 or later
Standard edition (64-bit)
Professional, Enterprise, or Ultimate edition,
Service Pack 1 or later
Enterprise edition (64-bit) Windows 8 *
* Certified for SB/XA Rich Client and SB/XA Communications Server only.
Operating system requirements
Microsoft .NET Framework version 4.0 or later is required to support SB/XA.
If you have installed all of Microsoft’s recommended updates for any
Windows platform listed above, you already have Microsoft .NET
Framework version 4.0 or later. If you do not have the required version of
.NET Framework on your computer, you can get it as a free download from the Microsoft product download site.
Windows 8 and Windows Server 2012 install Microsoft .NET Framework version 4.5 by default. However, you might also need to install components of .NET Framework version 3.5 required by SB/XA that are not present in
.NET Framework version 4.5.
Database server requirements
SB/XA Application Server on Windows requires the following minimum version of the UniData or UniVerse database server on Windows platforms:
■
■
UniData 7.1.20 or later, or
UniVerse 10.2.3 (Pick compatibility) or later, or
3-6 SB/XA Getting Started
■
UniVerse 10.2.3 (Pick compatibility) or later with National Language
Support (NLS)
For the latest updates to database server requirements, see the release notes for SB/XA.
Software requirements
Software compatibility statement
The version of all SB/XA v6.x.x components must be an exact match, from the same version, major release, point release, and build number. To be certain that you have matching versions of SB/XA software, install all
SB/XA v6.x.x components from the same SB/XA product download directory.
In v6.2.x, SB/XA Browser Client and SB/XA Rich Client do not support certain functionality that you need for application development work:
■
■
Developing screens
Not available in SB/XA Browser Client
Developing reports
Not available in SB/XA Browser Client or SB/XA Rich Client
SBClient v6.x.x provides support for the functionality that is not available in
SB/XA Browser Client or SB/XA Rich Client. SBClient v6.x.x is also required to complete the script portion of the SB/XA Application Server installation.
SBClient v6.x.x is not sold as a separate product; it is included on the SB/XA v6.x.x product CD and is covered by the same product license. SBClient v6.x.x does not run with SB+ Server v5.x or earlier; it is compatible only with
SB/XA v6.x.x and later.
SBClient v6.x.x is installed as an option of the SB/XA product CD menu. For instructions, see Chapter 2, “Installing SBClient on a Stand-alone PC,” in
SBClient Getting Started. SBClient software authorizes automatically.
3-7
Checking the installed version of SB/XA components
The version number of the SB/XA components that are currently installed on your computer determines if you can upgrade or if you must perform a clean installation.
Prerequisite
Understand the four elements of the version number in
Procedure
1.
2.
Click Start > Control Panel > Uninstall a program.
In the list, scroll to find SB/XA Application Server, SB/XA
Communications Server
, and SB/XA Presentation Components.
The four elements of the version number are listed in the Version column for each installed component.
Next step
Determining if you must remove files and components
Determining if you must remove files and components
In some cases, the installer cannot perform an upgrade, and it is necessary to remove old files and components and then perform a clean installation.
Prerequisite
Checking the installed version of SB/XA components
3-8 SB/XA Getting Started
Procedure
Check the following table to see if it is necessary to remove old files and components before installing SB/XA.
Situation Next step
You have an Early Adopter
Program (EAP) or Beta version of
SB/XA
You must remove old files and components. For
steps, see “Removing existing files and components” on page 3-10.
You have a previous GA version of SB/XA and you want to perform a clean installation
You must remove old files and components. For
steps, see “Removing existing files and components” on page 3-10.
You have an earlier GA version of
SB/XA and you want to upgrade to a later GA version
SB/XA allows the following upgrades:
■ from GA version 5.x to GA version 6.x
■ from GA version 6.x to a later
GA version 6.x
Do not remove old files and components.
Proceed with “Installing components of SB/XA on Windows” on page 3-14.
You are installing SB/XA for the first time on the computer
“Installing components of SB/XA
Determining whether to remove files and components
Next step
See the preceding table.
3-9
Removing existing files and components
Prerequisite
Determining if you must remove files and components
Procedure
1.
2.
3.
In Windows Explorer, change your settings to view hidden folders that you may need to delete.
■
Click Tools > Folder Options > View.
■
■
In the Files and Folders list, under the section “Hidden files and folders,” select the Show hidden files and folders option.
Clear the Hide protected operating system files check box. A warning is displayed. Click Yes to continue.
Click OK to save your changes.
■
The SB/XA Presentation Components (clients) use local storage to cache bitmaps and server definitions. If you previously installed
SB/XA Presentation Components, you may want to delete the local storage folder for the currently installed version to free up disk space. To find the location of the local storage folder for the currently installed version, open SB/XA Browser Client or SB/XA Rich Client and select Options > Client Configuration. In the SB/XA Client
Configuration window, the local storage folder is displayed in the
Application Data Path field.
Stop the SB/XA Communications Server service.
Click Start > Control Panel > Administrative Tools > Services. From the list, select SB/XA Communications Server or SB
Communications Server and click Stop.
3-10 SB/XA Getting Started
4.
Delete all .log files that were created by SB/XA components in any version of SB/XA 6.0.x or later, as detailed below:
■
Delete the logs created by SB/XA Presentation Components
(clients).
■
Versions 6.0.0 and 6.0.1
– The default location of these .log files on Windows XP is
C:\Documents and Settings\username\Application
Data\IBM\SBXALogs\Client
Version 6.0.2 or later
– The default location of these .log files depends on the Windows operating system.
Windows XP:
C:\Documents and Settings\username\Application
Data\Rocket Software\SBXA\Logs\Client
Windows 7, Windows 8, or Windows Vista:
C:\Users\username\AppData\Roaming\Rocket
Software\SBXA\Logs\Client
You may have chosen a different location as your root directory at installation. Navigate to the appropriate location and delete all files with the .log extension in this folder.
Delete the logs created by SB/XA Communications Server (the middle tier).
Versions 6.0.0 and 6.0.1
– The default location of these .log files on Windows XP is
C:\Documents and Settings\LocalService\Application
Data\IBM\SBXALogs\ComServer
Version 6.0.2 or later
– The default location of these .log files depends on the Windows operating system.
Windows XP:
C:\Documents and Settings\LocalService\Application
Data\Rocket Software\SBXA\Logs\ComServer
Windows 7, Windows 8, or Windows Vista:
C:\Windows\System32\config\systemprofile\AppData\
Roaming\Rocket Software\SBXA\Logs\ComServer
You may have chosen a different location as your root directory at installation. Navigate to the appropriate location and delete all files with the .log extension in this folder.
3-11
5.
6.
7.
8.
If you previously installed SB/XA Communications Server, you may need to delete the .config file in which SB/XA Communications
Server stores configuration information.
Versions 6.0.0 and 6.0.1
– The default location of this file on Windows
XP is C:\Documents and Settings\LocalService\Local
Settings\Application Data\IBM\file
Version 6.0.2 or later
– The default location of this file depends on the
Windows operating system.
Windows XP:
C:\Documents and Settings\LocalService\Local
Settings\Application Data\Rocket Software\file
Windows 7, Windows 8, or Windows Vista:
C:\Windows\System32\config\systemprofile\AppData\Local\
Rocket Software\file
You may have chosen a different location as your root directory at installation. Navigate to the appropriate location and delete this
.config file.
If you previously installed SB/XA Presentation Components
(clients), remove the program files.
■
Click Start > Control Panel > Uninstall a program. From the list, select SB/XA Presentation Components and click Uninstall to remove program files and Registry entries.
If you previously installed SB/XA Communications Server, remove the program files.
■
Click Start > Control Panel > Uninstall a program. From the list, select SB/XA Communications Server or System Builder
Communications Server
and click Uninstall to remove program files and Registry entries.
If you previously installed SB/XA Application Server on a Windows computer, manually delete the program files.
Note:
Do not remove SB+ Server or SB/XA Application Server program files from Start > Control Panel > Uninstall or change a program.
3-12 SB/XA Getting Started
9.
10.
■
Navigate to the folder containing the program files.
Versions 6.0.0 and 6.0.1
– The default location of this folder is
C:\IBM\SBXA\ApplicationServer\UniData or
C:\IBM\SBXA\ApplicationServer\UniVerse
Version 6.0.2 or later
– The default location of this folder is
C:\U2\SBXA\ApplicationServer\UniData, or
C:\U2\SBXA\ApplicationServer\UniVerse
Version 6.2.2 or later
– The default location of this folder is
C:\U2\SBXA\ApplicationServer\UniData, or
C:\U2\SBXA\ApplicationServer\UniVerse, or
C:\U2\SBXA\ApplicationServer\UniVerseNLS
Delete the program folder and all of its contents.
Delete SB/XA Application Server entries from the Registry.
■
In the Command Prompt window, type regedit and press Enter.
Version 6.0.0 and 6.0.1
– In the Registry Editor, navigate to My
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\IBM.
Version 6.0.2 or later
– In the Registry Editor, navigate to My
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Rocket
Software.
■
Delete the SB/XA Application Server folder and all of its contents.
If you previously installed the SBXAMAPIBridge component from the Install folder of the product CD, remove it now.
■
Click Start > Control Panel >Uninstall a program. From the list, select SBXAMAPIBridge and click Uninstall to remove program files and Registry entries.
Next step
Installing components of SB/XA on Windows
3-13
Installing components of SB/XA on Windows
Complete the following tasks to install components of SB/XA on Windows:
■
■
■
Installing SB/XA Presentation Components
Installing SB/XA Communications Server
❑
Configuring SB/XA Communications Server for certificates
Installing SB/XA Application Server on Windows
Installing SB/XA Presentation Components
The SB/XA Presentation Components (SB/XA Browser Client and SB/XA
Rich Client) are available for Windows platforms only.
Prerequisite
Determining if you must remove files and components
Procedure
1.
2.
3.
4.
5.
Log on to Windows on the computer on which you want to copy the
SB/XA Presentation Components (client files).
For help with deciding where to place the client files, see
“Planning your implementation of SB/XA” on page 2-5.
Turn off any virus protection software because it can interfere with the installation.
Close all Windows programs. This frees up memory for installation and prevents possible conflicts between the SB/XA installation program and other programs.
In the SB/XA product download directory, navigate to the SB/XA installation program, AutoRun.exe, and open it.
From the SystemBuilder Extensible Architecture Setup Menu, select the Install SB/XA Presentation Components option.
3-14 SB/XA Getting Started
6.
7.
Follow the steps in the installation wizard.
When you are asked to select a setup type, the Complete option is selected by default. With this option, the program installs both the
SB/XA Browser Client and the SB/XA Rich Client.
If you want to install only the SB/XA Browser Client or the SB/XA
Rich Client, select the Custom option. With this option, you can select the component(s) to install.
When the program finishes copying files, the InstallShield Wizard
Complete
window displays a message indicating that the installation completed successfully.
To close the wizard, click Finish.
Next step
Installing SB/XA Communications Server
3-15
Installing SB/XA Communications Server
SB/XA Communications Server is built on Microsoft Windows technologies, so this component is available on Windows platforms only.
Prerequisite
Installing SB/XA Presentation Components
Procedure
1.
2.
3.
4.
5.
6.
7.
Log on to Windows on the computer on which you want to install
SB/XA Communications Server.
For help with deciding where to install this component, see
“Planning your implementation of SB/XA” on page 2-5.
Turn off any virus protection software because it can interfere with the installation.
Close all Windows programs. This frees up memory for installation and prevents possible conflicts between the SB/XA installation program and other programs.
If the SystemBuilder Extensible Architecture Setup Menu is not already open on this computer, open the SB/XA 6.x.x download directory. Navigate to the SB/XA installation program,
AutoRun.exe
, and open it.
From the SystemBuilder Extensible Architecture Setup Menu, select the Install SB/XA Communications Server option.
Follow the steps in the installation wizard.
When the program finishes copying files, the InstallShield Wizard
Complete
window displays a message indicating that the installation completed successfully.
The Start SB/XA Communications Server service check box is selected by default. With this check box selected, the service is started automatically when you click Finish. If you do not want to start the service now, clear this check box.
To close the wizard, click Finish.
3-16 SB/XA Getting Started
Next step
Configuring SB/XA Communications Server for certificates
Configuring SB/XA Communications Server for certificates
Prerequisite
Installing SB/XA Communications Server
About this task
SB/XA Browser Client or SB/XA Rich Client must authenticate to
SB/XA Communications Server before a connection can be established. Some authentication types require certificates to establish a connection.
After installing SB/XA Communications Server, you may need to configure the software to use certificates to authenticate clients.
It is best to configure SB/XA Communications Server for certificates right after installing this component. You may also set up certificates as a maintenance task. If you set up application connections on the
SB/XA Communications Server computer before changing the logon properties from LocalService to a user in the Administrators group, you must re-enter application connection details.
The procedure for setting up certificates is detailed in Chapter 7,
“Chapter 7: Configuring and managing SB/XA Communications
Procedure
Optional: Setting up certificates to authenticate clients
Next step
Installing SB/XA Application Server on Windows
or
Chapter 4: Installing SB/XA Application Server on UNIX
3-17
Installing SB/XA Application Server on Windows
Prerequisite
Installing SB/XA Communications Server
About this task
The SB/XA Application Server component is available for Windows or UNIX.
You must install SB/XA Application Server on the same computer on which you are running the UniData or UniVerse (U2) database server. This is necessary to enable communications and the ability to exchange data.
■
■
If you are running the U2 database server on a UNIX computer, see Chapter 4,
“Chapter 4: Installing SB/XA Application Server on UNIX.”
If you are running the U2 database server on a Windows computer, complete the following procedures to install SB/XA
Application Server on the same Windows computer:
Procedure: Part 1 – The installation wizard guides you through
this part of the installation.
Procedure: Part 2 – Run the additional script part of the
installation from SBClient.
Procedure: Part 1
1.
2.
3.
Log on to Windows on the computer on which you want to install
SB/XA Application Server. This must be the same computer on which the UniData or UniVerse database server is installed.
Turn off any virus protection software because it can interfere with the installation.
Close all Windows programs. This frees up memory for installation and prevents possible conflicts between the SB/XA Application
Server installation program and other programs.
3-18 SB/XA Getting Started
4.
5.
6.
7.
8.
If the SystemBuilder Extensible Architecture Setup Menu is not already open on this computer, open the SB/XA 6.x.x download directory. Navigate to the SB/XA installation program,
AutoRun.exe
, and open it.
From the SystemBuilder Extensible Architecture Setup Menu, select the Install SB/XA Application Server option.
Follow the steps in the installation wizard.
If SB/XA Application Server is already installed in the directory you select, a Setup Type window gives you the option of overwriting your existing version.
■
To overwrite the folders containing the existing version of
SB/XA Application Server, select the Overwrite the existing
configuration
check box.
If the Overwrite the existing configuration check box is not selected, the existing folders are renamed. (SB is renamed
SB.OLD and SB.DEFN is renamed SB.DEFN.OLD.)
When the program has finished copying files, a message window indicates that installation completed successfully and instructs you to log on to the SB administration account to complete the installation. Click OK to proceed.
In the InstallShield Wizard Complete window, the View Release
Notes
check box is selected by default. If you do not want to read the
SB/XA Application Server release notes, clear the check box.
To close the wizard, click Finish.
Procedure: Part 2
After you have finished the installation wizard part of the setup, run the script from SBClient to finish installing SB/XA Application Server.
3-19
1.
2.
3.
Open SBClient. The appropriate version depends on whether you are upgrading to version 6.0.2 or later, or performing a clean installation.
■
■
If you are upgrading to version 6.0.2 or later and you want to save your existing SBClient settings, open SBClient 6.0.1 or earlier.
If you are performing a clean installation or you do not want to save your existing SBClient settings, open SBClient 6.0.2 or later.
■
SBClient 6.x.x must be an exact match to all other SB/XA 6.x.x components, from the same version, major release, point release, and build number.
Start a session, using no script, to log on to the host computer on which InstallShield placed the SB/XA Application Server files.
Your next action depends on whether you are installing the UniData,
UniVerse, or UniVerse NLS edition.
UniData – At the command line prompt, log to the SB administration account in the installation directory in which
InstallShield placed the SB/XA Application Server files. The default name of the administration account is SB on the UniData edition. For example,
■
■
LOGTO C:\U2\SBXA\ApplicationServer\UniData\SB
UniVerse – At the prompts, enter your UniVerse user name and password. Next, enter the path to the SB administration account in the installation directory in which InstallShield placed the
SB/XA Application Server files. The default name of the administration account is SB+ on the UniVerse edition. For example,
C:\U2\SBXA\ApplicationServer\UniVerse\SB+
UniVerse NLS – At the prompts, enter your UniVerse user name and password. Next, enter the path to the SB administration account in the installation directory in which InstallShield placed the SB/XA Application Server files. The default name of the administration account is SB+ on the UniVerse NLS edition.
For example,
C:\U2\SBXA\ApplicationServer\UniVerseNLS\SB+
3-20 SB/XA Getting Started
4.
5.
6.
7.
The installation script first updates file pointers.
For UniData only
, when pointer updates are complete, the following prompt is displayed:
SB/XA is about to install Release 6.2.2 on your computer.
Do you want to continue (Y/<N>):
■
UniData users: Enter Y to continue.
The installation script next catalogs all SB/XA programs.
For UniData only
, the following prompt is displayed:
The SB/XA programs are catalogued globally by default.
Do you want to catalog the programs locally using the
DIRECT option (Y/<N>):
■
UniData users: Select the appropriate catalog option:
To use the default option to catalog programs globally, enter N.
This option is the best choice if you install only one instance of
SB/XA Application Server on this host computer.
Otherwise, to catalog programs locally, enter Y.
On successful completion of the installation, the following prompt is displayed:
Type SB to start...
: or
Type SB+ to start...
:
■
At the command line prompt, enter SB for UniData or SB+ for
UniVerse or UniVerse NLS.
In the logon window, enter your credentials as follows:
In the User ID field, enter SB (the default user name of the SB user).
The default password of the SB user is null. Leave the Password field blank and press Enter.
In the Terminal ID field, enter the terminal ID; otherwise, enter GUI or CHAR.
In the Congratulations window, press any key to continue.
3-21
8.
9.
10.
11.
12.
Enter the product license details for SB/XA Application Server.
After entering all required information, the following prompt is displayed:
Accept/Change/Delete/File (A/C/D/F) A
■
Press Enter to accept the product license details.
The following prompt is displayed:
OK to Continue (Y/N):
■
Enter Y to continue.
When you are prompted to print License Agreement letter, press
Enter
to print the license letter now. Otherwise, press Esc to continue.
You can print the license letter at a later time.
Still in the SB or SB+ account, enter the SB host name as follows:
■
Enter /SB.PARMS in any input field.
■
In the SB Control Parameters form, select the GUI Parms tab.
In the SB+ Host Name field, enter a unique name for the host computer on which this instance of SB/XA Application Server is installed.
To save the changes to GUI parameters, press F2.
Log off from SB+ Server.
In SBClient, log on to SB/XA Application Server and log directly to the SBDEMO account.
This step is required to complete updates to SB/XA Application
Server and to update the version of the U2 database server account.
3-22 SB/XA Getting Started
13.
In the SBDEMO account, regenerate expressions as follows.
This step is required to correct a porting issue in version 6.x.x. The issue will be resolved in a later version of the product.
■
Enter /REGEN.EXP in any input field.
■
In the Regenerate Expressions window, enter the following values when running this process for the first time in an account after installation:
In the Dict File Name field, enter ALL to regenerate expressions from all dictionaries.
From the Regenerate Global Expressions list, select Yes.
From the Quiet Mode list, select No to display all messages on screen.
Tip:
Running the process in quiet mode captures all output and writes it to the xxLOGS directory file. If you later regenerate expressions in the same account, you can select either of the other options:
– Yes
to capture all output and write it to xxLOGS.
– Error
to capture only errors and write them to xxLOGS.
■
From the Data Files Only list, select the appropriate option based on the volume of files to regenerate. If you have a large number of process and definition files and you want to save time, select Yes. Otherwise, to regenerate expressions for data files as well as process and definition files, select No.
Warning:
Selecting Yes causes REGEN.EXP to not regenerate xxDEFN and xxPROCESS. Failing to regenerate the process and definition files may cause problems if field positions have been altered or if regenerated items are otherwise out of date. Select this option only if all items being regenerated, and their associated processes and definitions, are up to date. Otherwise, select No so that xxDEFN and xxPROCESS are regenerated, correcting any out-of-date definitions or processes.
For more information about REGEN.EXP, consult the SB/XA
Application Server Reference Manual.
To start the process, press F2.
When asked to confirm that you want to regenerate all expressions, click Yes to continue.
3-23
14.
15.
Whenever the regeneration process encounters a field used in a logical file definition, click Yes to update the logical file dictionary and continue.
After the regeneration process finishes, log off from the SBDEMO account.
Log to the account that contains your SB developed application(s).
At any prompt, enter /REGEN.EXP to regenerate expressions in this
account, the same as detailed in step 13 above.
Repeat this step for each account in this instance of SB/XA.
3-24 SB/XA Getting Started
Installing MAPI for messaging in the XUI clients
The same electronic mail functionality that is incorporated into SBClient is available as an optional add-on for SB/XA Browser Client and SB/XA Rich
Client. All clients use Microsoft's Messaging Application Program Interface
(MAPI). MAPI makes the client programs email messaging-aware; it interfaces SB messaging-based services to Microsoft Outlook.
The 32-bit version of MAPI is built into SBClient, and it is available as an addon for the SB/XA Presentation Components. The 64-bit version of MAPI is available as an add-on for SBClient or the SB/XA Presentation Components.
Two versions of the MAPI installation program are provided in the SB/XA product download directory:
■
■
A 32-bit MAPI installation program for the 32-bit version of
Microsoft Outlook
A 64-bit MAPI installation program for the 64-bit version of
Microsoft Outlook
SB/XA uses version control checking to determine if an existing
SBXAMAPIBridge component needs to be upgraded. If so, it returns an error message. For further information, see “MAPI Errors” in Chapter 5, “MAPI
Mail Integration,” in the Client Programmer’s Guide.
The SB server routines in the TUBP library have not been altered for the XUI clients. Existing email programs that run in SBClient also run in SB/XA
Browser Client and SB/XA Rich Client without modification. For details about the MAPI routines, see Chapter 5, “MAPI Mail Integration,” in the
Client Programmer’s Guide.
Prerequisite
Installing SB/XA Presentation Components
Procedure
1.
Navigate to the Install folder in the SB/XA product download directory.
3-25
2.
Open the appropriate version of the .msi program file to run the installation.
Run this program: On client computers with:
SBXAMAPIBridge.msi
The 32-bit version of Microsoft Outlook.
SBXAMAPIBridge64.msi
The 64-bit version of Microsoft Outlook.
MAPI installation programs
3-26 SB/XA Getting Started
Post-installation tips
Troubleshooting installation issues
The SB/XA Application Server installation scripts and documentation are platform-specific. Should a problem occur, the first step is to ensure that the installation instructions and version of SB/XA Application Server are for the correct platform. Next, review the installation instructions to ensure that you have followed them correctly. This includes naming conventions, environment variables, user/group permissions, recompiling/recataloging of programs, and licensing.
Exporting/importing SBClient settings
Existing customers who installed SBClient 6.0.1 or earlier may have session configurations, scripts, phone books, toolbars, and Smart Query definitions that can be used in SBClient 6.0.2 or later.
If you want to save settings from SBClient 6.0.1 or earlier, you can export your settings before installing SBClient 6.0.2 or later. After installing SBClient 6.0.2 or later, you can then import these settings to version 6.0.2 or later. For instructions, please see “Exporting/Importing SBClient Settings” in SBClient
Getting Started.
Renaming the SB administration account
SB/XA Application Server is normally installed as SB or SB+, depending on whether you are using UniData or UniVerse as the database server. The SB naming convention is used throughout this manual as it works for all environments supported by SB/XA Application Server. When using the account creation functions of SB/XA Application Server, all file and program pointers in the application being created are set relative to the SB account.
This means that SB/XA Application Server can be installed under a name other than SB and whatever name you choose, application accounts will always be created with the correct file and program pointers.
3-27
Be aware that if you change the name of the SB and SB.DEFN accounts after application accounts have been created, the file and program paths in the
VOCs of those application accounts are not updated automatically and the application may not function until the paths and pointers have been reset.
Any new application accounts created subsequently will have the correct paths to SB/XA Application Server programs and files (for example, they will point to the new SB account), but you need to manually reset the path of existing accounts, as described below.
When renaming the SB account, the SB.DEFN account must also be renamed to be consistent. That is, whatever name is used for the SB account, the
.DEFN account must contain that name with ‘.DEFN’ appended (for example, SB6 and SB6.DEFN).
Setting up an environment with multiple SB accounts
The SB main account does not have to be called SB, and more than one version of SB/XA Application Server can reside on the same system at the same time, under different names. However, note the following:
■
■
The internal structure of the COMMON block changed between versions 5.4.2 and 6.0.0. This means that subroutines cannot be shared between earlier and later versions. Where multiple versions of SB/XA Application Server are installed, each application account must have all of its file and program pointers set to only one SB account at a time (but different application accounts can point to different SB accounts).
Even though UniData would allow more than one SB account with the same name if you were to place them in different directories, only one account should be named SB. With more than one SB account, conflicts will arise due to the use of globally cataloged programs and common system files. In UniData, starting at SB+ Server version 3, it has been possible to catalog directly instead of globally. This is the preferred option if you are installing more than one version of
SB/XA Application Server. If you are installing more than one version of SB/XA Application Server globally, only one version should use the default prefix of ‘_SB_’, and other versions should use different prefixes to avoid conflicts. Refer to the upgrade notes on cataloguing for additional information.
3-28 SB/XA Getting Started
■
Each version of SB/XA Application Server must be fully licensed before attempting to install another version. Any attempt to install a second version before licensing the first version will result in security violations when attempting to use either version.
Changing SB paths and fixing Pointers
Take care to reset all VOC pointers (including ‘C’atalog, ‘F’ile, ‘Dir’ectory,
‘P’ointer, ‘R’emote, and ‘V’erb) to point to the new SB/XA Application Server location/version. Pointers to both SB and SB.DEFN need to be reset. Within the renamed SB account itself, the pointers to SB.DEFN also need to be reset.
In SAPROGS, run the program FIX.SBPLUS.POINTERS to fix the pointers in the SB, SB.DEFN, and SBDEMO accounts. (This is done automatically if the
SB account is being installed under a different name directly from the CD media.)
If the SB account has been renamed, or if you want to switch an application account between different versions of SB/XA Application Server on the same computer, you need to change the program and file pointers in the VOC of each application account to point to the new location/version.
UniData or UniVerse stores the full path in the VOC entry, so you must ensure that the full path is reset correctly. You can also run the program
FIX.SBPLUS.POINTERS in each application account to redirect the pointers to the new/renamed SB and SB.DEFN accounts. As the existing VOC entry still points to the old account, you must first reset it using the SETFILE command.
Note:
The SETFILE command syntax is similar to “SETFILE full_path
SAPROGS”. However, refer to your database documentation for the exact syntax of the SETFILE command on your system. Note that the ‘full path’ includes
SAPROGS
(for example,
C:\U2\SBXA\ApplicationData\UniData\SB\SAPROGS
).
For UniData-based systems, answer
Y
to the following prompts:
‘Ok to establish pointer’ and
‘Pointer already exists, do you want to overwrite’
(displayed if an entry exists already).
3-29
The program
FIX.SBPLUS.POINTERS
is then run with the path to the new SB account on the command line:
RUN SAPROGS FIX.SBPLUS.POINTERS C:\
full_path
\newSB
Each application upgrades (or downgrades) itself to the version level of its new SB/XA Application Server parent the first time a user logs to it. Of course, an application that takes advantage of the features of a later version of SB/XA Application Server may well have problems after it has been downgraded to an earlier version.
Starting SB/XA Application Server from U2
You can access SB/XA Application Server on Windows from a console session or through a Telnet connection across a network. At the UniData or
UniVerse logon prompt, enter your Windows user name and password. This logs you on to the default start-up directory, which is usually the UniData
‘demo’ account or UniVerse user account. At the ECL/TCL prompt, log to the
SB
account. For example:
LOGTO C:\U2\SBXA\ApplicationServer\UniData\SB
3-30 SB/XA Getting Started
Edition-specific information for Windows installations
This section contains information that is specific to the UniData, UniVerse, or
UniVerse NLS edition for Windows platforms:
■
■
■
Restrictions in the Windows editions
UniData compilation mode
All of SB/XA Application Server has been compiled using
BASICTYPE
‘
P
’.
Any code that SB/XA Application Server generates is also compiled using
BASICTYPE
‘
P
’.
The SB/XA Application Server object code is cataloged globally by default.
Program names have the prefix ‘_SB_’ in the global catalog space. From version 3, it has been possible to catalog the object directly (using the DIRECT option with the
CATALOG
verb). You are prompted during the installation process for the catalog mode and the prefix to use if the object is to be cataloged globally.
UniData environment options
The following UniData environment options are set as part of the SB/XA
Application Server logon procedure:
■
■
BASICTYPE ‘P’ - Sets the current BASICTYPE to be Pick-compatible.
HUSHBASIC ON - Suppresses UniBasic error messages, leaving only UniQuery error messages to display for UniQuery statements that execute from a UniBasic program.
3-31
3-32 SB/XA Getting Started
■
UDT.OPTIONS set by SB/XA Application Server. (Note that the default setting of all options is OFF.)
Option
2
3
4
6
8
9
11
21
41
Description
Use P command parser, which follows the Pick query language syntax and keywords.
No pause when printing non-existent keys after UniQuery command.
Date conversion; convert all characters (month name) to uppercase.
Clear the return stack when a CHAIN command is issued in a UniBasic program.
Pass the last value of @SYSTEM.RETURN.CODE back to calling process.
Preserve ‘Printer On’ flag when executing other processes.
Clear the DATA stack prior to EXECUTE or CHAIN command.
After completing a UniQuery report with the output to the screen, wait for the RETURN key in order to return to the
ECL prompt.
Return control to UniBasic program if execution of
UniQuery command fails.
UDT.OPTIONS set by SB/XA Application Server
Restrictions in the Windows editions
This section details the restrictions that are specific to Windows-based installations:
■
■
UniVerse or UniVerse NLS edition
UniData edition
Disabled options
■
■
■
■
■
■
■
The following SB/XA Application Server options have been set as disabled:
Create Account
Delete Account
Backup
SB Patching
File Resizing
List Avail Disk Space
USAM:Print Interface
Creating an account
To create an SB account, run the
newacct
command from the DOS shell and then use the Update Account menu option in the SB administration account or set a pointer to the DM file in the SB.DEFN account and run the
SB.INITIATE
program.
UniVerse or UniVerse NLS edition
Disabled options
The following SB/XA Application Server options have been set as disabled:
■
■
Create Account
Delete Account
3-33
■
■
■
■
Backup
SB Patching
File Resizing
List Avail Disk Space
Creating an account
To create an SB account, use the UV Admin tool and then use the Update
Account
menu option in SB administration account.
3-34 SB/XA Getting Started
1
Chapter 4: Installing SB/XA
Application Server on UNIX
Setting up before you install . . . . . . . . . . . . . .
Setting up the environment to support SB/XA Application Server on
UNIX . . . . . . . . . . . . . . . . . . . . .
Installing SB/XA Application Server on UNIX . . . . . . . .
Completing the installation checklist . . . . . . . . . .
Downloading installation files . . . . . . . . . . . .
Installing SB/XA Application Server files . . . . . . . .
Installation troubleshooting . . . . . . . . . . . . .
Renaming the SB account . . . . . . . . . . . . . .
Multiple SB accounts . . . . . . . . . . . . . . .
Additional information . . . . . . . . . . . . . . . .
Initiating SB/XA Application Server . . . . . . . . . .
Compilation mode (UniData-based systems) . . . . . . .
Recoverable files . . . . . . . . . . . . . . . . .
Configuring SB Print Management (UniData) . . . . . . . .
Chapter
4
This chapter provides instructions for setting up the environment to support
SB/XA Application Server on UNIX platforms and installing this component of the product on UNIX.
■
■
■
■
Installing SB/XA Application Server on UNIX
Configuring SB Print Management (UniData)
4-2 SB/XA Getting Started
Setting up before you install
This section summarizes the preliminary setup work you need to perform before installing SB/XA Application Server on UNIX.
Setting up the environment to support SB/XA Application
Server on UNIX
Before you install SB/XA Application Server on UNIX platforms, complete the following tasks.
Procedure
1.
2.
3.
4.
Make sure you have the hardware required to run SB/XA
Application Server on UNIX. See “Hardware requirements” on page 4-4.
Be sure the computer’s operating system supports SB/XA
Application Server on UNIX. See
“Operating system requirements” on page 4-4.
Make sure you have the database server software required for compatibility with SB/XA Application Server on UNIX. See
“Database server requirements” on page 4-4.
Be sure you have client software that is compatible with SB/XA
Application Server. See “Software requirements” on page 4-5.
4-3
Hardware requirements
This section details the amount of hard disk space required for SB/XA
Application Server on UNIX.
Component
SB/XA Application Server for UniData
■
Basic
■
With globally cataloged programs
(UniData only)
Hard disk space required
36MB
Additional 8MB
SB/XA Application Server for UniVerse
30MB
SB/XA Application Server for UniVerse NLS
30MB
Hardware requirements: SB/XA Application Server on UNIX
Note:
SB accounts are named differently in the UniData edition than in the
UniVerse or UniVerse NLS edition. In UniVerse, the account names include a +
(plus) sign; for example, SB+ and SB+.DEFN. In UniData, the accounts are named without the + sign; for example, SB and SB.DEFN. The latter method of notation is used throughout this manual for the purpose of brevity.
Operating system requirements
SB/XA Application Server runs on any UNIX operating system that supports the UniData or UniVerse database server. For information on versions of
UNIX that support the database server, see the UniData or UniVerse documentation.
Database server requirements
SB/XA Application Server on Windows requires the following minimum version of the UniData or UniVerse database server on UNIX platforms:
■
■
■
UniData 7.1.20 or later, or
UniVerse 10.2.3 (Pick compatibility) or later, or
UniVerse 10.2.3 (Pick compatibility) or later with National Language
Support (NLS)
4-4 SB/XA Getting Started
For the latest updates to database server requirements, see the release notes for SB/XA Application Server.
Software requirements
Software compatibility statement
The version of all SB/XA v6.x.x components must be an exact match, from the same version, major release, point release, and build number. To be certain that you have matching versions of SB/XA software, install all
SB/XA v6.x.x components from the same SB/XA product download directory.
In v6.2.x, SB/XA Browser Client and SB/XA Rich Client do not support certain functionality that you need for application development work:
■
■
Developing screens
Not available in SB/XA Browser Client
Developing reports
Not available in SB/XA Browser Client or SB/XA Rich Client
SBClient v6.x.x provides support for the functionality that is not available in
SB/XA Browser Client or SB/XA Rich Client. SBClient v6.x.x is also required to complete the script portion of the SB/XA Application Server installation.
SBClient v6.x.x is not sold as a separate product; it is included on the SB/XA v6.x.x product CD and is covered by the same product license. SBClient v6.x.x does not run with SB+ Server v5.x or earlier; it is compatible only with
SB/XA v6.x.x and later.
SBClient v6.x.x is installed as an option of the SB/XA product CD menu. For instructions, see Chapter 2, “Installing SBClient on a Stand-alone PC,” in
SBClient Getting Started. SBClient software authorizes automatically.
4-5
Installing SB/XA Application Server on UNIX
Completing the installation checklist
Use the following checklist to note details about your computer and its environment that you will need to perform the installation successfully. You may require the services of your System Administrator to complete the checklist or to perform some of the administration tasks it describes.
Procedure
Gather the following information on the installation checklist:
■
■
■
■
The superuser name and password.
The name of the UNIX group to which all the SB accounts will belong
(this may be sb or some other specially created group).
This is a system administration task. Your system administrator can provide you with the correct name to use, or details of how to create a name for this purpose. This should be done before installing
SB/XA Application Server.
The pathname of the directory in which SB/XA Application Server is to be installed.
Your system administrator is responsible for selecting this location.
The pathname of the UniData or UniVerse home directory.
After logging on to UNIX as the superuser, you must use the Bourne shell and have the UniData/UniVerse pathname available.
Your system administrator can provide you with the pathname to the
UniData or UniVerse home directory on your computer. For
UniData, this is usually similar to
/usr/ud
, depending on where
UniData was installed. For UniVerse, it is similar to
/usr/uv
, depending on where UniVerse was installed.
4-6 SB/XA Getting Started
■
The pathname of the UniData or UniVerse bin directory.
The System Administrator can provide you with the pathname to the
UniData or UniVerse bin directory on your computer. For UniData, this is usually similar to
/usr/ud/bin
, depending on where UniData was installed. For UniVerse, it is similar to
/usr/uv/bin
, depending on where UniVerse was installed.
Downloading installation files
Before installing SB/XA Application Server on UNIX platforms, you must first download the installation files from the SB/XA product download directory.
Complete the following steps to copy installation files from a Windows computer. You can copy the installation files from a Windows PC on a
TCP/IP network.
Procedure
1.
2.
3.
On the Windows PC, open the Command Prompt window and start an FTP session to the UNIX host.
Change the local directory to the path of the required installation file in the SB/XA product download directory. The cpio files are contained in the UNIX_Install subdirectory.
Change the target directory to the /tmp directory on the UNIX host.
4-7
4.
In binary transfer mode, transfer the install file to the /tmp directory on the UNIX host.
In the following example, the install file is copied from a Windows
PC to the UNIX host by FTP in a Command Prompt window:
C:\> ftp sbxa_as
Connected to sbxa_as.host.corporation.com
220 sbxa_as.host.corporation.com FTP server (Version 2.1
WU(1)) ready.
User (sbxa_as.host.corporation.com:(none)): mario
331 Password required for mario.
Password:
230 User mario logged in.
ftp> lcd z:\install\
Local directory now Z:\install ftp> cd /tmp
250 CWD command successful.
ftp> bin
200 Type set to I.
ftp> put sb622_udt_cpio
200 PORT command successful.
150 Opening BINARY mode data connection for sb622_udt_cpio
226 Transfer complete.
nn bytes sent in nn.nn seconds ( nn.nn Kbytes/sec).
ftp> bye
Goodbye.
Installing SB/XA Application Server files
Procedure
1.
Start SBClient 6.x.x.
Note that SBClient 6.x.x must be an exact match to all other SB/XA
6.x.x components, from the same version, major release, point release, and build number.
4-8 SB/XA Getting Started
2.
3.
4.
5.
6.
Log on to UNIX as root or as superuser.
Make sure that you are running the Bourne shell, that the pathname to UniData or UniVerse is set up, and that umask
is set correctly.
For UniData, specify the following: sh
UDTHOME=<pathname from checklist item 4>; export UDTHOME
UDTBIN=<pathname from checklist item 5>; export UDTBIN
PATH=$PATH:$UDTBIN; export PATH umask 007
For UniVerse, specify the following: sh
PATH=$PATH:<pathname from checklist item 5> export PATH umask 007
If you are installing SB/XA Application Server on a non-English version of UNIX, you must set the language environment variable
(LANG) to C for the installation procedure. For example:
LANG=C export LANG
Change directories to the working directory where you intend to load the SB, SB.DEFN, and SBDEMO accounts. This is found in checklist item 3.
For example, this may be the
/u/ sbxa directory, so: cd /u/sbxa
If the installation file has a .Z extension, the file must be extracted as follows:
■
■
On UNIX systems, run the uncompress command. For example: uncompress sb622
_udt_cpio.Z
On Linux systems, run the gunzip command. For example: gunzip sb622
_uv_cpio.Z
4-9
7.
8.
9.
Run the following command:
■
For UniData on UNIX: cpio -icvBdum < /tmp/ sb622
_udt_cpio or on Linux:
■ cpio -ivBdum < /tmp/ sb622
_udt_cpio
For UniVerse on UNIX: cpio -icvBdum < /tmp/ sb622_uv_cpio or on Linux: cpio -ivBdum < /tmp/ sb622_uv_cpio
If you intend to use nonstandard names for the SB accounts, move
(mv) SB and SB.DEFN to their new locations here. In the rest of this document, substitute your names wherever SB and SB.DEFN are mentioned.
For more information, see “Renaming the SB account” on page 4-15.
Change directories to the SB installation directory that was loaded by the cpio
command. For example, enter: cd SB
4-10 SB/XA Getting Started
10.
Start UniData by entering
udt
or UniVerse by entering
uv
in this directory.
In certain operating environments, such as Linux, UniData responds with a message, such as:
This machine is a low byte machine. VOC is high byte machine 2.0 static version.
If you receive this message, run the following commands from the parent directory of SB, SB.DEFN, and SBDEMO: convcode .
convdata -r .
and then start UniData by entering
udt
.
In certain operating environments, such as Linux, UniVerse responds with a message, such as:
Byte-swapped magic number in operating system file “VOC”, use
“fnuxi VOC” to convert
.
If you receive this message, run the following command from the parent directory of SB+, SB+.DEFN, and SBDEMO: find SB+ SB+.DEFN SBDEMO -print -exec fnuxi {} \; and then start UniVerse by entering
uv
.
4-11
11.
12.
The installation program starts by changing all the file pointers to point to the directories you have just created.
After fixing the file pointers, the installation program prompts you for further input:
a.
A prompt asks if you want to install SB/XA Application Server.
If you enter
N
, the program logs off. To begin installing SB/XA
Application Server, enter
Y
.
For UniData-based systems, the following applies:
You are prompted for the catalog mode. (For information, see
“Compilation mode (UniData-based systems)” on page 4-19.) To
accept the default (global catalog and program prefix of ‘_SB_’), press
ENTER
at the prompts.
The next prompt asks if you want to use the USAM:Print facilities. Enter
Y
or
N
.
b.
You are then prompted to enter the name of the UNIX group in which to install SB/XA Application Server. You can find the
UNIX group name in checklist item 2.
Messages indicate the status of the installation process.
On successful completion of the installation, a message explains how to log to the SB administration account. Make note of these instructions. Press
ENTER
to return to the UNIX prompt. The instructions are typically as follows: umask 007 newgrp sb cd /u/sbxa/SB
./.profile
Note:
The newgrp sb
(shown for illustration purposes above) is completed because SB/XA Application Server assumes that all SB users belong to a common UNIX group called, in this case, sb. The root user must belong to group sb so that any files created in SB/XA Application Server have the correct UNIX characteristics to be accessed by other SB users.
4-12 SB/XA Getting Started
13.
14.
15.
16.
17.
For system security and efficient use of UNIX system resources, give each user of the UNIX system a unique logon ID. This logon ID must belong to the group assigned to SB/XA Application Server. The initial logon directory must be a path to a valid SB/XA Application Server UniData/UniVerse account. Also, the initial shell must be the Bourne shell (that is,
/bin/sh
) and the umask must be set up as ‘007’.
It is important to run these commands before creating any SB accounts. This invokes the SB+ logon screen.
Log on to SB.
Enter the product license details for SB/XA Application Server.
In the SB or SB+ account, enter the SB host name as follows:
■
Enter /SB.PARMS in any input field.
■
In the SB Control Parameters form, select the GUI Parms tab.
In the SB+ Host Name field, enter a unique name for the host computer on which this instance of SB/XA Application Server is installed.
To save the changes to GUI parameters, press F2.
Log off from SB.
Log on to SB/XA Application Server and log directly to the
SBDEMO account.
This step is required to complete updates to SB/XA Application
Server and to update the version of the database server account.
4-13
18.
In the SBDEMO account, regenerate expressions as follows.
This step is required to correct a porting issue in version 6.x.x. The issue will be resolved in a later version of the product.
■
Enter /REGEN.EXP in any input field.
■
In the Regenerate Expressions window, enter the following values when running this process for the first time in an account after installation:
In the Dict File Name field, enter ALL to regenerate expressions from all dictionaries.
From the Regenerate Global Expressions list, select Yes.
From the Quiet Mode list, select No to display all messages on screen.
Tip:
Running the process in quiet mode captures all output and writes it to the xxLOGS directory file. If you later regenerate expressions in the same account, you can select either of the other options:
– Yes
to capture all output and write it to xxLOGS.
– Error
to capture only errors and write them to xxLOGS.
■
From the Data Files Only list, select the appropriate option based on the volume of files to regenerate. If you have a large number of process and definition files and you want to save time, select Yes. Otherwise, to regenerate expressions for data files as well as process and definition files, select No.
Warning:
Selecting Yes causes REGEN.EXP to not regenerate xxDEFN and xxPROCESS. Failing to regenerate the process and definition files may cause problems if field positions have been altered or if regenerated items are otherwise out of date. Select this option only if all items being regenerated, and their associated processes and definitions, are up to date. Otherwise, select No so that xxDEFN and xxPROCESS are regenerated, correcting any out-of-date definitions or processes.
For more information about REGEN.EXP, consult the SB/XA
Application Server Reference Manual.
To start the process, press F2.
When asked to confirm that you want to regenerate all expressions, click Yes to continue.
4-14 SB/XA Getting Started
19.
20.
Whenever the regeneration process encounters a field used in a logical file definition, click Yes to update the logical file dictionary and continue.
After the regeneration process finishes, log off from the SBDEMO account.
Log to the account that contains your SB developed application(s).
At any prompt, enter /REGEN.EXP to regenerate expressions in this
account, the same as detailed in step 18 above.
Repeat this step for each account in your implementation of SB/XA.
Installation troubleshooting
The SB/XA Application Server installation scripts and documentation are platform-specific. Should a problem occur, the first step is to ensure that the installation instructions and version of SB/XA Application Server are for the correct platform. Next, review the installation instructions to ensure that you have followed them correctly. This includes naming conventions, environment variables, user/group permissions, recompiling/recataloging of programs, licensing, and so on.
Renaming the SB account
SB/XA Application Server is normally installed as SB or SB+, depending on whether you are using UniData or UniVerse as the database. The SB naming convention is used throughout this manual as it works for all environments supported by SB/XA Application Server. When using the account creation functions of SB/XA Application Server, all file and program pointers in the application being created are set relative to the SB account. This means that
SB/XA Application Server can be installed under a name other than SB and whatever the name chosen, application accounts will always be created with the correct file and program pointers.
4-15
Be aware that if you change the name of the SB account after application accounts have been created, the file and program paths in the VOCs of those application accounts will not be updated automatically and the application may not function until the paths and pointers have been reset. Any new application accounts created subsequently will have the correct paths to
SB/XA Application Server programs and files (for example, they will point to the new SB account), but you need to manually reset the path of existing accounts, as described below.
When renaming the SB account, the SB.DEFN account must also be renamed to be consistent. That is, whatever name is chosen for the SB account, the
‘defn’ account must have that name with .DEFN appended to it (for example,
SB6
and SB6.DEFN).
Multiple SB accounts
Since the SB main account does not have to be called SB or SB+, it follows that more that one version of SB/XA Application Server can reside on the same system at the same time, but under different names. However, note the following:
1.
2.
3.
The internal structure of the COMMON block changed between versions 5.4.2 and 6.0.0. This means that subroutines cannot be shared between earlier and later versions. Where multiple versions of SB/XA Application Server are installed, each application account must have all of its file and program pointers set to only one SB account at a time (but different application accounts can point to different SB accounts).
The structure of some control records, and even the files in which they reside, changed between versions 5.4.2 and 6.0.0. For this reason, different versions of SB/XA Application Server cannot share files, nor should application accounts that point to different versions of SB/XA Application Server attempt to share files.
The named COMMON block used to implement the file caching scheme has changed between versions 5.4.2 and 6.0.0. This could cause a problem when logging between earlier and later versions, due to ‘named common block size mismatch’. This can be resolved by logging off completely from the older version, and then logging on to the new version, or vice versa.
4-16 SB/XA Getting Started
4.
5.
Even though UniData or UniVerse allows more than one SB account to use the same name if you place the accounts in different directories, only one account should be named SB. If you use the name SB for more than one account, conflicts will arise due to the use of globally cataloged programs and common system files and records (for example, UV.ACCOUNT in UniVerse).
In UniData, starting at SB+ Server version 3, it has been possible to catalog directly instead of globally. This option is preferable if more than one version of SB/XA Application Server is to be installed. If more than one version of SB/XA Application Server is to be installed globally, then only one version should use the default prefix of
‘_SB_’, the other versions should use different prefixes to avoid conflicts. Refer to the upgrade notes on cataloguing for additional information.
Each version of SB/XA Application Server must be fully licensed before any attempt is made to install another version. Any attempt to install a second version before licensing of the first version is complete will result in security violations when attempting to use either version.
Changing SB paths and fixing pointers
Take care to reset all VOC pointers (including ‘C’atalog, ‘F’ile, ‘Dir’ectory,
‘P’ointer, ‘R’emote, and ‘V’erb) to point to the new SB/XA Application Server location/version. Pointers to both SB and SB.DEFN need to be reset. Within the renamed SB account itself, you also need to reset the pointers to
SB.DEFN
. In SAPROGS, run the program
FIX.SBPLUS.POINTERS
to fix the pointers in the SB, SB.DEFN, and SBDEMO accounts. (If the SB account is being installed under a different name, this fix program runs automatically.)
If the SB account has been renamed, or if you want to switch an application account between different versions of SB/XA Application Server on the same computer, you need to change the program and file pointers in the VOC of each application account to point to the new location/version.
4-17
Because UniData or UniVerse stores the full path in the VOC entry, you must ensure that the full path is reset correctly. The program
FIX.SBPLUS.POINTERS
can be run in each application account to redirect the pointers to the new/renamed SB and SB.DEFN accounts. As the existing
VOC entry still points to the old account, it must first be reset via the SETFILE command.
Note:
The SETFILE command syntax is similar to “SETFILE full_path
SAPROGS”. However, you should refer to your database documentation for the exact syntax of the SETFILE command on your system. Note that the ‘full path’ includes SAPROGS (for example,
/u/sbplus/SB/SAPROGS
).
In the case of UniData-based installations, a few additional prompts are displayed. Answer Y to these prompts
‘Ok to establish pointer’ and
‘Pointer already exists, do you want to overwrite’
(displayed if an entry exists already).
The program
FIX.SBPLUS.POINTERS
is then run with the path to the new SB account on the command line:
RUN SAPROGS FIX.SBPLUS.POINTERS /
full_path
/newSB
Each application upgrades (or downgrades) itself to the version level of its new SB/XA Application Server parent the first time a user logs to it. Of course, an application that takes advantage of the features of SB/XA
Application Server may well have problems after it has been downgraded to an earlier version.
4-18 SB/XA Getting Started
Additional information
Initiating SB/XA Application Server
The SB/XA Application Server installation process creates in the SB and
SBDEMO
accounts a
.profile
script that contains the appropriate UNIX commands to correctly set up the user environment for SB/XA Application
Server. The same script is copied to each new SB/XA Application Server– based user/application account that is created. It is very important that each user of SB/XA Application Server belongs to the appropriate group specified when SB/XA Application Server is installed and that they execute the
.profile
script before entering SB/XA Application Server. This is particularly important for the root user before creating any new accounts.
Failure to do so will result in users having insufficient privileges to access required files and directories.
Compilation mode (UniData-based systems)
All of SB/XA Application Server has been compiled using
BASICTYPE
‘
P
’.
Any code that SB+ generates is also compiled using
BASICTYPE
‘
P
’.
The SB/XA Application Server object code is cataloged globally by default.
Program names have the prefix ‘_SB_’ in the global catalog space. From version 3.x it has been possible to catalog the object directly (using the
DIRECT option with the
CATALOG
verb). You are prompted during the installation process for the catalog mode and the prefix to use if the object is to be cataloged globally.
UniData options set by SB/XA Application Server
The following UniData environment options are set as part of the SB/XA
Application Server logon procedure:
■
■
BASICTYPE ‘P’ - Sets the current BASICTYPE to be Pick-compatible.
HUSHBASIC ON - Suppresses UniBasic error messages, leaving only UniQuery error messages to display for UniQuery statements that execute from a UniBasic program.
4-19
■
UDT.OPTIONS set by SB/XA Application Server. (Note that the default setting of all options is OFF.)
Option
2
3
4
6
8
9
11
21
34
41
Description
Use P command parser, which follows the Pick query language syntax and keywords.
No pause when printing nonexistent keys after
UniQuery command.
Date conversion; convert all characters (month name) to uppercase.
When a CHAIN command is issued in a UniBasic program, clear the return stack.
Pass the last value of
@SYSTEM.RETURN.CODE
back to calling process.
Preserve ‘Printer On’ flag when executing other processes.
Clear the DATA stack prior to
EXECUTE
or
CHAIN command.
After completing a UniQuery report with the output to the screen, wait for the RETURN key in order to return to the ECL prompt.
If USAM:Print has been enabled, this option is set to
ON
.
If execution of UniQuery command fails, return control to UniBasic program.
UDT.OPTIONS set by SB/XA Application Server
Recoverable files
On UniData, if the Recoverable File System (RFS) is installed, SB/XA
Application Server provides the opportunity to create files using the
‘Recoverable’ keyword.
4-20 SB/XA Getting Started
The FC (file create) process has a field/prompt to allow users to nominate the file as recoverable. In UniData-based systems, SB/XA Application Server can create files outside the FC tool (for example, batch files created through the
Create Batch File process, index files, and SB/XA Application Server system files created when a new module or account is created) and if transaction processing is active for the current module, SB/XA Application Server prompts you to choose whether to make these files recoverable when they are being created. The normal response is
Y
or
N
(for ‘yes’ or ‘no’). However, processes that create a number of files at once (for example, when a new module or account is being created), will accept additional responses of
A
and
S
, meaning respectively all files to be created recoverable and suppress further questions about recoverable files (default all answers to subsequent questions to No).
In UniVerse it is possible to tell from Data/Basic whether a file is recoverable
(either via FILEINFO or through examining the UV.TRANS file), but it is not possible to force a file to be created with logging enabled. Therefore, if transaction processing is active for the current module, the user will simply be given a reminder to consider whether logging should be enabled (at the system/operating environment level) once the file has been created.
4-21
Configuring SB Print Management (UniData)
SB/XA Application Server supports native UniData print management.
With native UniData print management, printing is directed to the standard operating system spooler supported by UniData. Advanced print management functions such as starting and stopping printers or managing spooled reports are not supported.
4-22 SB/XA Getting Started
Chapter 5: Methods of deploying
SB/XA Presentation Components
Chapter
5
Deployment of SB/XA Presentation Components . . . . . . .
ClickOnce deployment . . . . . . . . . . . . . . .
Alternative methods of deployment . . . . . . . . . .
Deployment of SB/XA Presentation Components
Deciding on a method to deploy software components to client computers is a separate process from planning how to distribute SB/XA components across computers on your network.
This section explains methods for deploying the SB/XA Presentation
Components to the client computers on your network:
■
■
Alternative methods of deployment
ClickOnce deployment
Microsoft’s ClickOnce technology simplifies the work of deploying and updating Windows-based client applications. Here we provide a brief introduction to ClickOnce as an option for distributing the SB/XA
Presentation Components (SB/XA Browser Client and SB/XA Rich Client files) to client computers.
For more in-depth information about ClickOnce, please see Microsoft’s discussion of the subject at the following URL: http://msdn2.microsoft.com/en-us/library/142dbbz4.aspx
Overview of ClickOnce
ClickOnce is incorporated into Microsoft .NET Framework version 3.5. It makes use of functionality that existed in older versions of the .NET
Framework and run time, as well as some capabilities developed specifically to support ClickOnce when it was introduced in version 2.0.
A primary objective of ClickOnce is to provide a secure and reliable deployment method that allows users to download and run applications from centrally managed servers without logging on as administrator on the client computer. Using ClickOnce, you can deploy applications in an isolated environment that ensures they will not affect or corrupt other applications and data on the client computer.
5-2 SB/XA Getting Started
ClickOnce allows you to deploy a Windows-based client application to a client computer by putting the application files on a Web or file server available to the client and giving the user a link.
When the user clicks the link on a Web page or in an e-mail, the application files are downloaded to the user's computer and executed. The application is executed in a space secured by .NET code access security (CAS), which controls what the program is allowed to do. When you put a new version of the application on the server, connected clients detect it automatically, and the update is downloaded. ClickOnce also allows you to deploy an application so it behaves as though it were installed on the client computer.
Your role in ClickOnce deployment
Publishing the SB/XA Presentation Components
When a new version of SB/XA is released, your role in ClickOnce deployment begins by publishing the SB/XA Presentation Components to the deployment server.
To publish the SB/XA Presentation Components, you simply copy all the application files into a folder on the Web or file server, along with the application and deployment manifest files that describe the deployment to the ClickOnce run time.
■
■
The application manifest describes the application itself, including the assemblies, dependencies and files that make up the application, the required permissions, and the location where updates will be available. We provide you the application manifest.
The deployment manifest describes how the application is deployed, including the location of the application manifest, and the version of the application that clients should run. An administrator creates the deployment manifest using the manifest generation tool (Mage.exe) in the .NET Framework SDK.
The SB/XA Presentation Components can be published as either a launched application or an installed application. We’ll discuss the differences in these types later.
5-3
Providing a link
After publishing the SB/XA Presentation Components to the deployment server, you provide the user with a link to the deployment manifest as a URL
(hyperlink or shortcut).
When the user clicks the link, the .NET run time on the client computer recognizes the file extension and downloads and executes the application on the user's computer.
The files are downloaded to a cache under the logged-on user's profile in an obfuscated location on the user’s computer. The application then executes in the secure context of CAS.
Deployment examples
The next two figures give you an idea of how you might deploy the SB/XA
Presentation Components as a ClickOnce application on a Web or file server.
These illustrations show just two options among many alternatives to help you visualize some possible deployment scenarios.
5-4 SB/XA Getting Started
Published application on SB/XA Communications Server computer
The following figure illustrates a typical scenario for deploying the SB/XA
Presentation components as a ClickOnce application, with the published application on the same computer as SB/XA Communications Server.
Figure 3-1 Published application on SB/XA Communications Server computer
As shown above, users on the client PCs and laptops click a link to access the
SB/XA Presentation Components on the file server computer.
5-5
Published application on Web Server computer
As an alternative, a ClickOnce deployment of SB/XA Presentation
Components may put the published application on a Web server computer.
Figure 1-1 Published application on Web Server computer
Here, users on the client PCs and laptops click a link to access the SB/XA
Presentation Components on a Web server computer.
Launched application vs. installed application
In this section, we briefly explain the difference between a ClickOnce
launched application and a ClickOnce installed application.
5-6 SB/XA Getting Started
Launched application
If you publish the SB/XA Presentation Components as a launched application, the user has to start the application using the link provided.
Every time the user clicks the link, the .NET run time on the user's computer checks the version in the local cache against the version on the deployment server. If new files are available, they are downloaded before the application is started. The locally cached version is then executed on the user's computer.
Installed application
If you publish the SB/XA Presentation Components as an installed application, the application launches when the user clicks the link for the first time. Additionally, a shortcut is added to the Start menu, so on subsequent occasions the user can launch the program from the Start menu. Also,
ClickOnce creates an item on the Control Panel > Add or Remove Programs list to allow the user to uninstall the application. The uninstall process merely removes the Start menu shortcut and clears the files from the cache under the user's profile.
Updates for an installed application are more complex because of the many possible options, including
■
■
■
■ whether the application checks for updates automatically whether updates are required when the application checks for available updates whether the update is downloaded before the application launches or in the background while the application is running.
Optionally, you can perform updates programmatically using the ClickOnce
API and skip the automatic update feature altogether.
Alternative methods of deployment
ClickOnce is a feature that SB/XA inherits from the Microsoft .NET
Framework on which the SB/XA Presentation Components are built. It offers many advantages, minimizing the work involved in deploying and updating the SB/XA Presentation Components on multiple client computers.
5-7
That said, we can also advise that use of the ClickOnce feature is not required.
You still have the option of installing SB/XA Presentation Components by copying the SB/XA Browser Client and/or SB/XA Rich Client files manually to each user’s computer. This may make sense if you are running SB/XA in a limited test or development environment, or if you have a very small number of users in a production environment.
5-8 SB/XA Getting Started
Chapter 6: Setting up application connections and configuring clients
Setting up application connections . . . . . . . . . . . .
Why use Single Sign-On? . . . . . . . . . . . . . .
Enabling application connections . . . . . . . . . . .
Centralized client configuration . . . . . . . . . . . . .
Hiding the Options button . . . . . . . . . . . . .
Customizing configuration on the client . . . . . . . . . .
Calling the XUI clients from an application . . . . . . . . .
Running a process from a web page . . . . . . . . . .
Running a process from a shortcut . . . . . . . . . . .
Chapter
6
This chapter provides information on setup tasks for enabling the user to connect to SB developed applications and configuring SB/XA Browser Client and SB/XA Rich Client for efficient use in a business environment:
■
■
■
■
Setting up application connections
Centralized client configuration
Customizing configuration on the client
Calling the XUI clients from an application
6-2 SB/XA Getting Started
Setting up application connections
SB/XA offers Single Sign-On as an optional feature for reducing the repetitive work of signing on to your SB developed applications and connecting to SB/XA Application Server.
In this section, we first look at advantages—as well as some possible drawbacks—of enabling the Single Sign-On feature for use with your applications. Next, we walk you through the steps for entering settings on the server and the client to enable the user to connect to SB developed applications.
■
■
Enabling application connections
Why use Single Sign-On?
Single Sign-On is an optional security feature of SB/XA that reduces the number of steps required to sign on to your SB developed applications and connect to SB/XA Application Server.
Without Single Sign-On, the user may potentially complete four logons:
■
■
■
■
User’s PC
SB/XA Communications Server
Database server (UniData or UniVerse)
SB developed application
With Single Sign-On enabled, the user must only log on to the PC. This feature offers convenience and time savings for users who log on numerous times throughout the workday.
6-3
When you should not use Single Sign-On
In a typical business environment, Single Sign-On provides adequate security to protect data and application development work against unauthorized access. However, certain situations require the additional security of multiple logons (for example, if more than one person logs on as the same user).
Even if the Single Sign-On feature is not a good choice for some or all users in your business environment, you must complete all the steps in this chapter to configure communication between SB/XA Communications Server and
SB/XA Application Server on the server side and the client side, except as noted.
Enabling application connections
Enabling application connections is accomplished in two main tasks:
■
■
Setting up application connections on SB/XA Application Server
Setting up application access on the client
Setting up application connections on SB/XA Application Server
This section contains the steps for setting up connections to SB developed applications on SB/XA Application Server.
Procedure
1.
2.
Start SBClient 6.x.x.
Note that SBClient 6.x.x must be an exact match to all other SB/XA
6.x.x components, from the same version, major release, point release, and build number.
Log on to SB/XA Application Server and log to the SB administration account. The default name of the administration account is SB on UniData or SB+ on UniVerse.
6-4 SB/XA Getting Started
3.
Set up an SB instance as follows.
a.
In any input field, enter /SBINSTANCE.SETUP
b.
In the SB Instance Setup window, enter details as follows.
In the Name field, enter a name for an SB instance for which you want to set up application connections. An SB instance is an implementation of SB/XA, such as SB/XA for UniData on
Windows, or SB/XA for UniVerse on UNIX, or an SB/XA test system running on UniVerse NLS on UNIX. In this example, we used the name “MASTER” for this implementation of SB/XA.
In the Description field, enter a description of the SB instance that will help you distinguish this instance from any others.
In the Database field, enter udcs for UniData or uvcs for
UniVerse.
In the Machine ID field, enter the full name of the computer on which SB/XA Application Server is installed for this instance. If
SB/XA Application Server for this instance is installed on the local computer, enter localhost.
6-5
6-6 SB/XA Getting Started
In the Code Page field, enter the number of the server code page to use for storing data for this instance, or press F3 to select the code page number from a selection list. The United States code page is 437; the International code page is 850. Other valid code page numbers are also supported. The code page number is replaced with its description when the cursor leaves this field.
In the OEM or ANSI field, enter a value indicating the type of the specified code page: O for OEM or A for ANSI.
In the Admin User field, enter the name of the SB admin user, such as the default admin user name, SB.
In the Path to SB Account field, enter the full path to the SB admin account. The default path is as follows.
C:\U2\SBXA\ApplicationServer\UniData\SB or
C:\U2\SBXA\ApplicationServer\UniVerse\SB+ or
C:\U2\SBXA\ApplicationServer\UniVerseNLS\SB+
In the Unicode | Database Value field, enter pairs of values as follows.
In the Unicode column, enter the Unicode character for a character that is to be stored as a different value in the database.
In the Database Value column, enter the value to be stored on the U2 database server for the specified Unicode character.
In the Default Fail Value field, enter the character to store in the database for any unrecognized character entered. The default value is 63, which is the decimal value for the ASCII character
“?”.
Press F2 to save the details for the SB instance.
Repeat step 3b for each SB instance to be set up.
4.
Optional: If you have existing XAML theme files, you can create a theme definition for each XAML theme that is to be made available to one or more applications within this SB instance.
a.
b.
In any input field, enter /THEME.DEFN
In the Theme Definition window, enter details as follows.
In the Theme Name field, enter the unique name of the theme.
The theme name must belong to an existing XAML theme. In this example screen, we used the name of a custom theme created in a test environment.
SB/XA uses this name to load the theme. You will enter the theme name later in /HK.CONTROL or in the application definition.
In the Description field, enter a description of the theme.
In the Options Menu Text field, enter the text to be displayed on the Options > Themes menu to identify this theme as a menu selection.
In the Type field, enter the type code for the file or resource containing the theme.
Code
X
A
Description
XAML
Assembly. (This option is currently not supported.)
Type codes
6-7
6-8 SB/XA Getting Started
In the Assembly or File Name field, enter a name, based on the type code of the file or resource containing the theme.
For type:
X
A
Enter:
The name of the file in which the XAML code for this theme resides: typically, xxTHEMES or [global sysid]THEMES.
The name of the Assembly Definition that defines the assembly containing the theme.
Assembly or file name
In the Class or Item Name field, enter one of the following:
■
For type:
X
A
Enter:
The item name that contains the XAML code for the
ResourceDictionary.
The fully qualified name of the class to be invoked as the theme.
Assembly or file name
After entering all details for the theme, press F2 to save the theme definition.
Repeat step 4b for each theme to be set up.
5.
Optional: If you have created theme definitions, you can set up themes for each account as follows.
a.
In any input field, enter /UPDATE.ACCOUNT.
b.
In the Update An Account window, press F7 to set up themes for the account.
6-9
c.
In the Themes window, enter details as follows.
6-10 SB/XA Getting Started
d.
In the Available Themes field, enter the name of each theme to be made available for use in this account; otherwise, press F3 to select themes from a list. The theme must have an existing theme file and theme definition (/THEME.DEFN).
In the Default Theme field, enter the name of the default theme for this account.
Press F2 to save the theme details.
In the Update An Account window, press F2 to save updates to the account.
Repeat step 5 b and c for each account that requires a theme.
6.
Set up applications to which the user requires access as follows.
a.
In any input field, enter /APPLICATION.SETUP
b.
In the Application Setup window, enter details as follows.
In the Application Name field, enter the name of an existing SB application to be accessed.
In the Application Description field, enter a description that identifies the application.
In the Instance field, enter the name of the SB instance in which the SB application exists.
In the Account Path field, enter the full path to the account associated with this application.
In the SBXA Admin Account field, enter Y if the account is the
SB administration account, or N if it is not.
Press F2 to save Application Setup details.
Repeat step 6b for each application to be set up (such as SB,
SBDEMO, and each SB developed application).
When completed, the Application Setup window for SBDEMO looks similar to the following example:
6-11
7.
Add application connection details in the user security record as follows.
a.
In any input field, enter /SEC.USER.SETUP
b.
In the SB+ Prompt window, type the password of the SB/XA user you are currently logged on as and click Accept.
In the User Security Setup window, enter details in the Name tab as follows.
In the User ID Code field, enter the user ID of the SB/XA user for whom you want to set up application connections.
In the First Name field, enter the user’s first name.
In the Surname field, enter the user’s last name.
6-12 SB/XA Getting Started
c.
Click the Password tab and enter details as follows.
In the Autologin field, enter a value to enable or disable Single
Sign-On for the user.
Value
0
1
2
Description
Disable Single Sign-On.
Enable Single Sign-On with autologin.
Enable Single Sign-On with autologin and standard logon allowed.
Autologin options
In the New Pwd Next Login field, enter a value specifying whether the user must enter a new password on the next logon to SB/XA.
Value
Y
N
Description
Require new password on next logon.
Do not require new password on next logon. This is the default setting.
New password on next login options
6-13
6-14 SB/XA Getting Started
d.
Click the Single Sign-On tab.
Regardless of whether you enable Single Sign-On for the user, you must enter details required to establish connections to applications as follows.
In the Windows ID field, enter the user’s Windows identity credentials, based on the authentication type. Details for each authentication type are listed in the following table.
Authentication type Description
Windows Enter the Windows domain name or local name and user name of the SB/XA user for whom you are setting up application connections. These are the credentials the user enters to log on to his or her computer
(the client computer). The Windows identity is case-sensitive.
An example of a domain name and user name might be ROCKET1\MGRIFFIN as shown in the preceding example.
An example of a computer’s local name and user name might be BROWN\cbrown
The user can check the Windows identity used to log on to his or her computer by pressing Ctrl + Alt + Delete.
■
On Windows XP: This opens the
Windows Security screen, where Logon
Information displays the user’s
Windows identity (domain name or local name and user name).
■
On Windows 7, Windows 8, and
Windows Vista: Click the Change
Password
option. The first field displays the user’s Windows identity (domain name or local name and user name).
SBXAUserNamePassword Enter the credentials for the SB/XA
Application Server computer used as the administration server, not the credentials for a client computer. This is the Windows domain name and user name of an authorized user on the SB/XA administration server domain. The
Windows identity is case-sensitive.
An example of a domain name and user name might be XYZServer\administrator.
Windows ID by authentication type
6-15
6-16 SB/XA Getting Started
Authentication type Description
WindowsUserNamePassword Enter the credentials for the SB/XA
Communications Server computer, not the credentials for a client computer. This is the Windows domain name and user name of an authorized user on the SB/XA
Communications Server domain. The
Windows identity is case-sensitive.
An example of a domain name and user name might be:
XYZServer\administrator
Windows ID by authentication type (continued)
In the Allow Local Storage of User IDs and Passwords field, enter a value as follows.
Value
Y
N
Description
Allow storage of user IDs and passwords on SB/XA
Communications Server. This setting is required for
Single Sign-On.
A value of Y has no effect when Autologin is set to 0 in the user security record.
Do not allow storage of user IDs and passwords on
SB/XA Communications Server. This setting disallows
Single Sign-On.
Allow local storage options
If this field is left blank and the Allow Local Storage of User IDs
and Passwords
flag in the group security record contains a value, SB/XA uses the value in the group record by default.
In the Don’t automatically add Group Applications field, enter a value as follows.
Value
Y
N
Description
Applications do not automatically become available to a user when they are added to that user’s group. This is the default setting.
Applications automatically become available to a user when they are added to that user’s group.
Don’t automatically add Group Applications options
Tip:
Choosing “N” in the Don’t Automatically add Group
Applications
field and setting the users’ Application Hierarchy
Mode
flag to “Hierarchy no ripple” creates an auto-add and auto-remove functionality. An administrator who needs to perform work on an application can remove it from a user group to perform work on it, and the users in that group automatically lose access to the application. When the administrator finishes work on the application and returns it to the user group, all of the users in that group automatically regain access to the
6-17
6-18 SB/XA Getting Started application.
For more information on Application Hierarchy Mode, see
“Admin Menu” in Administering SB/XA.
For information on associating applications to a group, see
“Security Tasks” in Administering SB/XA.
In the Valid Applications field, on each line of the grid enter the name of an SB developed application to which this SB/XA user requires access, such as SB, SBDEMO, or any other application.
In the OS User ID field, in the row for each application enter the
Windows or UNIX user ID that the SB/XA user enters to log on to the operating system on the database server computer on which UniData or UniVerse is installed.
Tip:
If you leave the OS User ID field blank:
❑
SB/XA uses the value in the Windows ID field by default.
❑
For SB/XAUserNamePassword authentication type only, if the user enters the operating system user ID when logging on to SB/XA, the value is saved to the OS User ID field in the user security record.
In the Auto OS field, select a value to enable or disable autofill of the operating system user ID for the application in this row.
Value
Y
N
Description
Enable autofill of operating system user ID.
Disable autofill of operating system user ID.
Autofill operating system user ID options
In the SB User field, on the row for each application enter the
SB/XA user ID of the user for whom you are setting up application connections. If you leave this field blank, SB/XA uses the value of the User ID Code entered in User Security
Setup by default.
In the Auto SB field, select a value to enable or disable autofill of the SB user ID for the application in this row.
e.
Value
Y
N
Description
Enable autofill of SB user ID.
Disable autofill of SB user ID.
Autofill SB user ID options
To save the application connection details, press F2.
To save the User Security Setup details, press F2.
6-19
Setting up application access on the client
This section contains the steps for setting up application connections on the client side:
■
■
On first connection
On the first time SB/XA Browser Client or SB/XA Rich Client is opened in an SB instance, complete the following steps on the computer running
SB/XA Communications Server to configure its connection to SB/XA
Application Server.
Procedure
1.
2.
If the SB/XA Communications Server service is not currently running, start it now.
Click Start > Control Panel > Administrative Tools > Services. From the list, select SB/XA Communications Server and click Start.
On first use, you must run SB/XA Browser Client or SB/XA Rich
Client as administrator on the SB/XA Communications Server computer as follows.
a.
b.
c.
Run the Command Prompt window as administrator.
Change directories to the location in which InstallShield placed the SB/XA Presentation Components (client) folders:
The default location of SB/XA Browser Client is
C:\U2\SBXA\PresentationComponents\BrowserClient.
The default location of SB/XA Rich Client is
C:\U2\SBXA\PresentationComponents\RichClient
To start SB/XA Browser Client, enter
SBXAWinFxBrowser.xbap
or
To start SB/XA Rich Client, enter
SBXAWinFxWindow.application
6-20 SB/XA Getting Started
3.
The content of the SB/XA Communications Server Connection window is based on the user’s authentication type. Enter connection details for the user’s authentication type:
– SBXAUserNamePassword authentication
– WindowsUserNamePassword authentication
■
Windows authentication
Enter connection details as follows.
In the Windows Identity field, enter the user’s current Windows identity is displayed, as shown in this example.
In the Communications Server Name field, enter the IP address or name of the computer on which SB/XA Communications
Server is installed. In this initial setup, SB/XA Communications
Server is running on the same computer as the client, so you can enter localhost.
6-21
■
In the Communications Server Port field, the default port number 808 is displayed. You can accept the default or change it if necessary.
❑
Click Test Network. If the connection to SB/XA
Communications Server is successful, a pop-up window with the message “The network test was successful” is displayed. Click OK to close the pop-up window.
❑
Tip:
If the connection fails, check to make sure you have started the
SB/XA Communications Server service.
To save the SB/XA Communications Server connection details, click Save.
SBXAUserNamePassword authentication
Enter connection details as follows.
6-22 SB/XA Getting Started
In the Windows Identity field, the user’s current Windows identity is displayed, as shown in this example.
In the Communications Server Name field, enter the IP address or name of the computer on which SB/XA Communications
Server is installed. In this initial setup, SB/XA Communications
Server is running on the same computer as the client, so you can enter localhost.
In the Communications Server Port, the default port number
808 is displayed. You can accept the default or change it if necessary.
In the Application User Name field, enter the user name of the
SB/XA user on the SB/XA administration server. The user name is case-sensitive.
■
In the Application Password field, enter the password of the
SB/XA user on the SB/XA administration server.
❑
Click Test Network. If the connection to SB/XA
Communications Server is successful, a pop-up window with the message “The network test was successful” is displayed. Click OK to close the pop-up window.
❑
Tip:
If the connection fails, check to make sure you have started the
SB/XA Communications Server service.
To save the SB/XA Communications Server connection details, click Save.
WindowsUserNamePassword
authentication
Enter connection details as follows.
The Windows Identity field contains the user’s current
Windows identity, as shown in the example.
In the Communications Server Name field, enter the IP address or name of the computer on which SB/XA Communications
Server is installed. In this initial setup, SB/XA Communications
Server is running on the same computer as the client, so you can enter localhost.
In the Communications Server Port field, the default port number 808 is displayed. You can accept the default or change the port number if necessary.
In the Windows User Name field, enter the Windows user name on the SB/XA Communications Server domain. The user name is case-sensitive.
6-23
6-24 SB/XA Getting Started
In the Windows Password field, enter the password of the user on the SB/XA Communications Server domain.
❑
Click Test Network. If the connection to SB/XA Communications Server is successful, a pop-up window with the message “The network test was successful” is displayed.
Click OK to close the pop-up window.
❑
Tip:
If the connection fails, check to make sure you have started the
SB/XA Communications Server service.
To save the SB/XA Communications Server connection details, click Save.
4.
Enter configuration details for SB/XA Administration Server as follows.
In the U2 Server Name field, enter the IP address or full name of the
Windows or UNIX computer on which SB/XA Application Server is installed. If SB/XA Application Server is installed on the local computer, enter localhost. If you are running SB/XA Application
Server on multiple computers, enter the name or IP address of the
SB/XA Application Server computer used as the Administration
Server.
In the U2 Account Name or Path field, enter the full path of the SB administration account.
In the U2 Database Type field, enter the code for the database type.
The default type is udcs for UniData or uvcs for UniVerse.
In the U2 Server User Name field, enter the user name of the administrator of the Windows or UNIX computer on which SB/XA
Application Server is installed.
In the U2 Server Password field, enter the password of the administrator of the Windows or UNIX computer on which SB/XA
Application Server is installed.
In the Validate U2 Server Password field, re-enter the same password for verification.
6-25
5.
■
Click Test Details.
If SB/XA Communications Server connects successfully with
SB/XA Application Server and all details pass the test, the message “The Administration Server details are valid” is displayed.
If SB/XA Communications Server does not connect successfully with SB/XA Application Server or the details are incorrect, an error message is displayed, indicating the type of error condition.
Tip:
If you did not run the client as administrator, SB/XA returns the error message, “You have no permission to set Administration Server
Configuration. Please login as Windows Administrator.” Close the
client and return to step 2 to run the client as administrator.
To save the SB/XA Administration Server details, click Save.
■
Enter information in the SB/XA Administration Login window to establish a connection through the SB/XA administration server, as follows.
6-26 SB/XA Getting Started
In the User Name field, enter the domain name or local name and
Windows or UNIX user ID you use to log on to the operating system on the U2 database server computer running UniData or UniVerse and the SB/XA Application Server used as the administration server.
In the Password field, enter the password for the Windows or UNIX user ID.
In the SB/XA User Name field, enter the user name of the SB admin user.
In the SB/XA Password field, enter the password of the SB admin user.
Click Connect.
6.
If you have not entered a license number and details, the license reminder window is displayed. This window prompts you to take action with your SB/XA license.
7.
Click the appropriate button to enter your license number, enter license details, or print the license letter. Otherwise, click Continue.
Log off from SB/XA Application Server and close the SB/XA
Browser Client or SB/XA Rich Client window.
6-27
On subsequent connections
After the initial connection between SB/XA Communications Server and
SB/XA Application Server has been configured for an SB instance, users who log on to SB developed applications in this instance are prompted for application connection details.
The user is prompted to enter credentials for an application only on the first time to access that application.
Procedure
1.
Open SB/XA Browser Client or SB/XA Rich Client by doubleclicking the desktop icon.
Otherwise, if desktop icons are not present, open the client as detailed here.
a.
Navigate to the location in which InstallShield placed the SB/XA
Presentation Components (client) folders:
The default location of SB/XA Browser Client is
C:\U2\SBXA\PresentationComponents\BrowserClient.
b.
The default location of the SB/XA Rich Client is
C:\U2\SBXA\PresentationComponents\RichClient
To start SB/XA Browser Client, open the BrowserClient folder and double-click the file SBXAWinFxBrowser.xbap or
To start SB/XA Rich Client, open the RichClient folder and double-click the file SBXAWinFxWindow.application
6-28 SB/XA Getting Started
2.
In this step, the user authenticates to SB/XA Communications Server in one of three ways, based on the authentication type configured on the client computer:
– SBXAUserNamePassword authentication
– WindowsUserNamePassword authentication
■
Windows authentication
The user logs on to the same domain or a trusted domain of
SB/XA Communications Server, and is authenticated to SB/XA
Communications Server automatically.
■
SBXAUserNamePassword authentication
Enter credentials to authenticate through the SB/XA administration server, as follows.
In the User Name field, enter the SB/XA user name on the
SB/XA Application Server computer used as the administration server. The user name is case-sensitive.
In the Password field, enter the password of the SB/XA user.
If you are allowed to store your user name and password, a Save
Credentials
check box is present after your first login. To save your credentials, select the check box. When this check box is selected, your user account credentials are stored in the Control
Panel > User Accounts > Credential Manager
on the SB/XA
Application Server computer used as the administration server.
❑
Click Connect.
6-29
■
WindowsUserNamePassword authentication
Enter credentials for SB/XA Communications Server, as follows.
3.
In the User Name field, enter the Windows user name on the
SB/XA Communications Server domain. The user name is casesensitive.
In the Password field, enter the password of the user on the
SB/XA Communications Server domain.
If you are allowed to store your user name and password, a Save
Credentials
check box is present after your first login. To save your credentials, select the check box. When this check box is selected, your user account credentials are stored in the Control
Panel > User Accounts > Credential Manager
on the SB/XA
Application Server computer used as the administration server.
❑
Click Connect.
The Connect to Application window contains a list of all applications that have been set up for the user. Connect to an application as follows.
6-30 SB/XA Getting Started
From the Application Name list, select the name of the application to which you want to connect.
■
Click Connect.
If Autologin is set to 1 in the user security record, logon is
Otherwise, continue with steps
4 and 5 to enter credentials for
the U2 database server and SB/XA.
4.
In the U2 Database Server Login window, enter your credentials to connect to the U2 database server, as follows.
5.
In the User Name field, enter the Windows or UNIX user ID you use to log on to the operating system on the U2 database server computer running UniData or UniVerse and the SB/XA Application Server used as the administration server.
For SB/XAUserNamePassword authentication type only, if the
OS User ID
field in the user security record was initially left blank, the value entered here in the User Name field is saved to the OS User ID field in the user security record.
In the Password field, enter the password for your Windows or
UNIX user ID.
■
Click Connect.
In the SB/XA Login window, enter your logon credentials for SB/XA
Administration Server, as follows.
In the User Name field, enter your SB/XA user name on the SB/XA
Application Server computer used as the administration server.
In the Password field, enter the password for your SB/XA user name.
■
Click Connect.
6-31
6.
If you have not entered a license number and details, the license details window is displayed.
■
Click the appropriate button to enter your license number, enter license details, or print the license letter now. Otherwise, press
Continue
to open the application.
6-32 SB/XA Getting Started
Centralized client configuration
As of version 6.1.0, it is possible to configure SB/XA workstations from a central location via a common configuration file. In order to do this, you must place an XML document, named SBXAConfiguration.xml, in the same folder as the .xbap or .application file used to launch the client.
This option simplifies the deployment of the clients, as it eliminates the need to configure each client individually. In addition, if a change is required (for example, a change to the SB/XA Communications Server), you can edit the central configuration file and all clients will pick up the change the next time they start.
The value of a specific property that is used by the application is determined in the following priority order:
1.
2.
3.
The value set by the user in the SB/XA Client Configuration form.
The value set by the common configuration file,
SBXAConfiguration.xml.
The system default value.
The XML document should contain all properties that need to be set to values other than their defaults. Any properties that start with an underscore (_) are there to assist U2 Technical Support if necessary, and are never used to set any properties on the client.
Hiding the Options button
In the SB/XA Browser Client or SB/XA Rich Client main window, the
Options
button is shown by default. This button provides access to a menu of configuration settings for the client and SB/XA Communications Server.
If the Options button is shown, users can access the SB/XA Client
Configuration form and change their own configuration settings. You can configure clients to hide the Options button by setting a property in the centralized configuration file.
6-33
Procedure
1.
To hide the Options button, insert the following lines in the XML document:
<Property>
<Name>enableOptionsMenu</Name>
<Value>False</Value>
</Property>
Example XML document
<?
xml version = " 1.0
" encoding = " utf-8 " ?>
< SBXAConfiguration xmlns:xsd = " http://www.w3.org/2001/XMLSchema " xmlns:xsi = " http://www.w3.org/2001/XMLSchema-instance " >
< ConfigurationCollection >
< Configuration Name = " Current " >
< ClientConfiguration >
< Properties >
< Property >
< Name > defaultApplication </ Name >
< Value > SBDEMO </ Value >
</ Property >
< Property >
< Name > _Version </ Name >
< Value > 6.1.0.3023
</ Value >
</ Property >
< Property >
< Name > _WindowsIdentity </ Name >
< Value > COMPANYDOMAIN\joeuser </ Value >
</ Property >
< Property >
< Name > _RenderingTier </ Name >
< Value > 0 </ Value >
</ Property >
< Property >
< Name > _TerminalServices </ Name >
< Value > True </ Value >
</ Property >
</ Properties >
</ ClientConfiguration >
< CommunicationServerConnectionConfiguration >
< CommunicationServers >
< CommunicationServer Name = " CommunicationServer "
ServerName = " c1commsserver " Port = " 808 " AuthenticationType = " Windows "
/>
</ CommunicationServers >
</ CommunicationServerConnectionConfiguration >
</ Configuration >
</ ConfigurationCollection >
</ SBXAConfiguration >
6-34 SB/XA Getting Started
Customizing configuration on the client
SB/XA workstations inherit configuration properties from the common
SBXAConfiguration.xml file or from the system defaults, as detailed in
“Centralized client configuration” on page 6-33.
Complete the following steps to customize properties on the client and set up the SB/XA Communications Server connection. The settings in the SB/XA
Client Configuration form override those in the common
SBXAConfiguration.xml file or the system defaults.
Procedure
1.
2.
3.
Open SB/XA Browser Client or SB/XA Rich Client.
In the main window, the Options button is shown by default.
If the button is currently shown, go to step 3.
If the button is currently hidden, complete the following actions to show it.
a.
In the centralized configuration file, change the OptionsMenu property to True.
b.
Restart SB/XA Browser Client or SB/XA Rich Client.
In the main window, select Options > Configuration.
6-35
4.
In the SB/XA Client Configuration form, create a new configuration or select an existing configuration and customize it, as detailed in this procedure.
6-36 SB/XA Getting Started
The Configuration Name drop-down list can contain multiple configuration profiles. Select the name of the configuration to display. Otherwise, if you want to create a new configuration profile, type a name for the new configuration.
The buttons in the upper right corner of the form take action on the client configuration:
5.
■
■
■
To add or update the selected configuration profile in the
SBXAConfiguration.xml file, click Export Configuration. If the
.xml file did not previously exist, SB/XA creates it for you. The information that is copied to the file includes configuration information for SB/XA Communications Server.
After creating or updating the SBXAConfiguration.xml file, you can then copy it to the location of the .xbap or .application file
(the location from which the client is launched).
To reset the values of all properties in the selected configuration profile back to the defaults shipped with the product, click Reset
Configuration
.
To reload the SBXAConfiguration.xml file, click Reload
Configuration
. Reloading the file overwrites any changes made in the SB/XA Client Configuration form.
In the Client tab, view or change the settings for properties that control how the client behaves:
To save warnings to a log, set the value of Log Warnings to True.
To save information messages to a log, set the value of Log
Information
to True.
In development mode, SB/XA Browser Client or SB/XA Rich Client displays messages to inform the developer about features that are not yet implemented in this version of SB/XA. To work in development mode in this client, set the value of In development
mode
to True.
The Options button in the lower right corner of the client main window is shown by default. To configure clients to hide this button, set the value of Enable Options Menu to False.
Change any other settings as necessary.
6-37
6.
In the Communications Server Connections tab, view or change the
SB/XA Communications Server connections available to the client.
6-38 SB/XA Getting Started
From the connections listed on this page, you can select the SB/XA
Communications Server to which the client connects. The available connections are based on the source network and the authentication type.
Each connection has its own configuration profile. On starting
SB/XA Browser Client or SB/XA Rich Client, if multiple configuration profiles are present in the SBXAConfiguration.xml configuration file, the user is presented with a list of configuration profiles from which to select. After the user selects a configuration, the client computer goes through all of the SB/XA Communications
Server connections defined and determines which one to use.
The client determines the connection to use in the following priority order:
a.
A partial or exact match of the local IP address to the source network address.
For example, if the IPv4 address of the client computer is
172.16.2.15 and the source network is 172.16.7, that connection is not valid for the client. However if the source network is 172.16, that connection is used for the client.
b.
If there are no connections with a specified source network that matches the local IP address and there is a connection with no specified source network, that connection is used.
The Name column lists the name of each Communications Server connection that has been defined for the client. The connection used in the current session is selected by default. Click the name of a connection to select it.
The Server Name field contains the name of the server computer on which the SB/XA Communications Server component is installed.
You can change the server name, if necessary. Enter the name of an existing server computer.
The Port field contains the port number on which the client connects to the associated SB/XA Communications Server. The default port number is 808. You can change the port number, if necessary. Enter the 1- to 3-digit number of an available port on the client computer.
The Source Network field contains the partial or full IPv4 address of the network on which the client connects to SB/XA Communications
Server, if specified. You can change the source network address, if necessary. Enter a partial or full IPv4 address of the network.
The Authentication Type field indicates the type of authentication that the client uses to connect to SB/XA Communications Server:
_ Windows (default)
_ SBXAUserNamePassword
_ WindowsUserNamePassword
You can select a different authentication type from the drop-down list. For detailed information about the authentication types, see
“Overview of authentication types” on page 7-7.
6-39
The Reliable check box indicates whether the Windows
Communication Foundation (WCF) reliability option is enabled for the connection. WCF reliability provides an additional measure of reliability in connectivity for Transmission Control Protocol (TCP)guaranteed transport options. The Reliable check box is selected by default. To enable WCF reliability, select the check box; to disable
WCF reliability, clear the check box.
From the Security drop-down list, select an option for configuring the resiliency and encryption properties of the connection:
_ Message: This option ensures a resilient and secure connection that survives temporary disconnection from the network. For example, the connection is not interrupted when switching from
LAN to wireless operation, even if the dynamic IP address of the client computer changes. This option incurs the largest overhead, with a packet size approximately 10 times greater than that with the Transport security option.
_ Transport (default): This option ensures confidentiality by encrypting the connection with the AES-256 algorithm.
Encryption with this algorithm prevents intermediaries from tampering with the session. This option incurs approximately 10 percent more overhead than a non-encrypted packet.
_ None: With this option, packets are not encrypted, and the overhead is about the same as the SBClient-SBXA protocol. This option is not valid for all authentication types.
The following table lists valid options for each authentication type:
Authentication Type Reliable options Security options
Windows True|False Message|Transport
SBXAUserNamePassword True|False Message*†|Transport*†|None
WindowsUserNamePassword True|False Message†|Transport†
Valid options by authentication type
* For the SBXAUserNamePassword type with Message or Transport security, you must supply the Windows credentials for SB/XA
Communications Server in the Windows Credential Manager before connecting. If you do not set up these credentials first, the connection fails and the user is not presented a login prompt.
6-40 SB/XA Getting Started
7.
†
For the SBXAUserNamePassword type with Message or Transport security and for the WindowsUserNamePassword type, you must configure SB/XA Communications Server to use a server certificate.
For steps, see
“Setting up certificates to authenticate clients” on page 7-16.
Optional. To add a new connection, click Add Connection at the bottom of the SB/XA Client Configuration form.
In the Connection Name field, enter a unique name for the
Communications Server connection.
In the Communications Server Name field, enter the name of the server computer on which the SB/XA Communications Server component for this connection is installed.
I
n the Communications Server Port field, enter the 1- to 3-digit port number on which the client computer connects to SB/XA
Communications Server. The default port number is 808.
Optional: In the Source Network field, you can set up network matching for the connection by specifying a partial or exact match of the local IP address to the source network address. Enter the partial or full IPv4 address of the network on which the client connects to
SB/XA Communications Server. Otherwise, if you do not want to use network matching for this connection, leave this field blank.
6-41
6-42 SB/XA Getting Started
From the Authentication Type drop-down list, select the type of authentication the client uses to connect to SB/XA Communications
Server:
– Windows (default)
– SBXAUserNamePassword
– WindowsUserNamePassword
Some options are not valid for all authentication types. See the
“Valid options by authentication type” table on page 6-40.
The ReliableSessionPmpt check box indicates whether the
Windows Communication Foundation (WCF) reliability option is enabled for the connection. WCF reliability provides an additional measure of reliability in connectivity for Transmission Control
Protocol (TCP)-guaranteed transport options. The Reliable check box is selected by default. To enable WCF reliability, select the check box; to disable WCF reliability, clear the check box.
From the EndpointSecurityPmpt drop-down list, select an option for configuring the resiliency and encryption properties of the connection:
■
_ Message: This option ensures a resilient and secure connection that survives temporary disconnection from the network. For example, the connection is not interrupted when switching from
LAN to wireless operation, even if the dynamic IP address of the client computer changes. This option incurs the largest overhead, with a packet size approximately 10 times greater than that with the Transport security option.
_ Transport (default): This option ensures confidentiality by encrypting the connection with the AES-256 algorithm.
Encryption with this algorithm prevents intermediaries from tampering with the session. This option incurs approximately 10 percent more overhead than a non-encrypted packet.
_ None: With this option, packets are not encrypted, and the overhead is about the same as the SBClient-SBXA protocol. This option is not valid for all authentication types. See the
“Valid options by authentication type” table on page 6-40.
To add the connection, click Apply. The new connection is listed in the Communications Server Connections page.
Otherwise, to cancel the operation, click Cancel.
8.
9.
Optional: To delete an existing connection, select the connection in the list and click Delete Connection. The connection is removed from the list in the Communications Server Connections page, and the associated configuration profile is deleted from the Connection
Name
drop-down list.
To save the changes in both tabbed pages of the SB/XA Client
Configuration form, click Save.
Otherwise, to discard changes in both tabbed pages, click Cancel.
Data from SB/XA sessions is stored in a cache on the client computer.
To clear the cache on the client computer, click Clear Local Cache.
SB/XA deletes the data that was stored in the cache.
6-43
Calling the XUI clients from an application
If you run the same SB process often, you can save steps by calling SB/XA
Browser Client or SB/XA Rich Client from an application and passing through the process to the client. To do this, use one of the following techniques:
■
■
Running a process from a web page
Running a process from a shortcut
Running a process from a web page
Use this technique to start SB/XA Browser Client or SB/XA Rich Client, connect to an application, and run a process in the client from a web page.
Procedure
1.
In a web page, create a link to start the client, connect to an application, and run a process.
■
For SB/XA Browser Client, enter the following URL for the link:
■
SBXAWinFxBrowser.xbap?StartApplication=[applicationN
ame]&StartProcess=[processName]&StartSystemId=[syste
mID]
For SB/XA Rich Client, enter the following URL for the link:
SBXAWinFxWindow.application?StartApplication=[applic
ationName]&StartProcess=[processName]&StartSystemId=
[systemID]
Running a process from a shortcut
Use this technique to start SB/XA Browser Client or SB/XA Rich Client, connect to an application, and run a process from a desktop shortcut.
6-44 SB/XA Getting Started
Procedure
1.
From a shortcut, enter a URL to start the client, connect to an application, and run a process.
■
For SB/XA Browser Client, enter the following URL: http://localhost/Clients/Browser/SBXAWinFxBrowser.xb
ap?StartApplication=[applicationName]&StartProcess=[
processName]&StartSystemId=[systemID]
■ assuming that the client application is available from http://localhost/Clients/Browser/SBXAWinFxBrowser.xbap
For SB/XA Rich Client, enter the following URL:
"C:\Program Files (x86)\Internet
Explorer\iexplore.exe"
"http://localhost/Clients/Rich/SBXAWinFxWindow.appli
cation?StartApplication=[applicationName]&StartProce ss=[processName]&StartSystemId=[systemID]" assuming that the client application is available from http://localhost/Clients/Rich/SBXAWinFxWindow.application
6-45
Chapter 7: Configuring and managing SB/XA
Communications Server
Listing users logged on to SB/XA Communications Server . . .
Stopping and starting SB/XA Communications Server . . . . .
Stopping SB/XA Communications Server . . . . . . . .
Starting SB/XA Communications Server . . . . . . . .
Overview of authentication types . . . . . . . . . . . .
Windows authentication . . . . . . . . . . . . . .
SBXAUserNamePassword authentication . . . . . . . .
WindowsUserNamePassword authentication . . . . . . .
Setting up certificates to authenticate clients . . . . . . . . .
Installing the required tools . . . . . . . . . . . . .
Changing the logon properties of the communications service .
Creating a signing certificate . . . . . . . . . . . . .
Creating a server certificate . . . . . . . . . . . . .
Configuring SB/XA Communications Server . . . . . . .
Installing the root certificate on the client computer . . . . .
Configuration for SB/XA Services . . . . . . . . . . .
Chapter
7
This chapter discusses tasks for managing SB/XA Communications Server:
■
■
■
■
Listing users logged on to SB/XA Communications Server
Stopping and starting SB/XA Communications Server
Overview of authentication types
Setting up certificates to authenticate clients
7-2
Listing users logged on to SB/XA Communications
Server
Before performing maintenance or stopping the SB/XA Communications
Server service, you may want to see a list of users who are currently logged on to that instance of SB/XA Communications Server.
Procedure
1.
2.
3.
Open SB/XA Browser Client or SB/XA Rich Client.
Log on to the host computer and log to an application in the SB instance in which SB/XA Communications Server service is running.
Enter /LISTMT at any prompt. The List SBXA Communications
Server Users
window is displayed.
7-3 SB/XA Getting Started
Check the list of users.
When finished, click OK to close the window.
Stopping and starting SB/XA Communications Server
SB/XA Communications Server is a executable program that runs as a service on the Windows computer on which it has been installed. After you finish installing SB/XA Communications Server, the service starts immediately by default and runs in the background without user intervention as long as Windows is running.
There are a number of conditions that require you to stop and start SB/XA
Communications Server to break communication and then re-establish it.
The SB/XA Communications Server service can be stopped and started manually when required.
■
■
Stopping SB/XA Communications Server
Starting SB/XA Communications Server
Stopping SB/XA Communications Server
You must stop the SB/XA Communications Server service in certain situations to break communication with client applications and with SB/XA
Application Server on the UniData or UniVerse database server. Some of the circumstances that require manually stopping the service include the following:
■
■
■
Before performing maintenance on SB/XA Communications Server or SB/XA Application Server.
Before uninstalling and reinstalling or upgrading SB/XA
Communications Server software.
If you run SB/XA Communications Server locally on your laptop, you must stop the service each time you want to log on to SB/XA from your laptop after switching to a new location on a different network.
For example, John runs SB/XA Communications Server locally on his laptop. He logged on at the office on his laptop in the morning, and later logs on to his home network on the same laptop. He must stop SB/XA Communications Server and start the service again before he can connect to SB/XA.
7-4
Procedure
1.
Click Start > Control Panel > Administrative Tools > Services.
The list of Windows services that are currently installed on the computer populates in the Services panel.
7-5 SB/XA Getting Started
2.
From the list, select SB/XA Communications Server and click Stop.
Starting SB/XA Communications Server
In certain cases, you must start SB/XA Communications Server manually to establish or re-establish communication with client applications and with
SB/XA Application Server. Some of the circumstances that require manually starting the service include the following:
■
■
■
If you cleared the check box for starting SB/XA Communications
Server automatically by default after installing this component on
Windows.
After performing maintenance on SB/XA Communications Server or SB/XA Application Server.
After stopping SB/XA Communications Server upon switching to a new location on a different network.
Procedure
1.
2.
Click Start > Control Panel > Administrative Tools > Services.
The list of Windows services that are currently installed on the computer populates in the Services panel.
From the list, select SB/XA Communications Server and click Start.
7-6
Overview of authentication types
Beginning with version 6.1.0, SB/XA Browser Client and SB/XA Rich Client can authenticate using any of three options:
■
■
■
SBXAUserNamePassword authentication
WindowsUserNamePassword authentication
The client inherits a default authentication method from the system default or from the common configuration file, if any. For details on the inheritance of client settings, see
“Centralized client configuration” on page 6-33.
Regardless of the client’s inherited settings, the user can select an authentication type in the SB/XA Client Configuration form, and this setting overrides system or common configuration file defaults. For details, see
“Customizing configuration on the client” on page 6-35.
7-7 SB/XA Getting Started
Windows authentication
The Windows authentication type relies on the standard Microsoft Windows authentication protocol. This option is good for a scenario in which the user logs on to a Windows client computer on the same domain or a trusted domain of SB/XA Communications Server.
An advantage of this option is that Windows authentication is performed transparently and requires only minimal setup. The user does not have to do anything other than log on to his or her Windows computer.
Checklist of setup tasks
The Windows authentication type requires only minimal setup.
■
■
On the SB/XA Communications Server computer
❑
No server certificate or advance setup is required on the server computer.
On the client computer
❑
SB/XA Browser Client or SB/XA Rich Client must be configured with the name of the SB/XA Communications Server computer, and the Authentication Type must be set to Windows.
For details on configuring the client, see “Customizing configuration on the client” on page 6-35.
Handshake
With Windows authentication, the handshake between the client and SB/XA
Communications Server is completed as follows:
1.
2.
3.
The user logs on to a Windows computer, entering the
domain_name\user_name (such as ROCKETA\cabrowne) and password.
The user opens SB/XA Browser Client or SB/XA Rich Client on the client computer.
The client sends a connection request to the SB/XA Communications
Server specified in the client configuration, which is running on the same domain (ROCKETA in our example) or a trusted domain (such as ROCKETB).
7-8
7-9 SB/XA Getting Started
4.
The following exchange takes place during the handshake:
■
SB/XA Communications Server verifies that the client belongs to its own domain or a trusted domain.
■
The client verifies that it is communicating with the SB/XA
Communications Server computer specified in the client configuration.
If the exchange is successful, the connection is opened.
Otherwise, an error message is displayed on the client and the connection request is closed.
SBXAUserNamePassword authentication
The SBXAUserNamePassword authentication type relies on an internal
SB/XA authentication protocol, not on the Microsoft Windows authentication protocol.
With this authentication type, the user opens a connection to SB/XA
Communications Server by entering his or her SB/XA logon credentials.
This alternative works well when there are a large number of users connecting to one or several SB/XA Communications Server computers.
The Windows authentication type does not work in this situation because users connect from untrusted domains.
The WindowsUserNamePassword authentication type would work in this scenario. However, the advantage of using SBXAUserNamePassword authentication is that it eliminates the need for the administrator to set up and maintain a large number of user accounts on the SB/XA
Communications Server computer(s).
Checklist of setup tasks
Depending on the Security option, SBXAUserNamePassword authentication may require minimal setup on the client computer or certificate setup on the communications server and client computers.
■
On the SB/XA Communications Server computer
If the Security option is None, no set up is required on the SB/XA
Communications Server computer. Data sent between the client and
SB/XA Communications Server is not encrypted.
If the Security option is Message or Transport, the following setup tasks are required:
❑
Install the tools needed to create certificates.
For steps to obtain tools, see “Installing the required tools” on page 7-17.
7-10
7-11 SB/XA Getting Started
■
❑
❑
❑
❑
Change the logon properties of the SB/XA Communications
Server service from LocalService to a user in the Administrators group.
For steps to change logon properties, see
“Changing the logon properties of the communications service” on page 7-18.
The administrator must create or obtain a signing certificate. The signing certificate is to be used to sign a server certificate for
SB/XA Communications Server.
The administrator needs to create a server certificate for SB/XA
Communications Server. With the SBXAUserNamePassword authentication type, SB/XA Communications Server sends a server certificate to the client during the handshake. The server certificate contains the name of SB/XA Communications Server and the trust chain of certificate issuers.
For steps to create a server certificate, see “Creating a server certificate” on page 7-23.
The administrator must configure the SB/XA Communications
Server to use the server certificate.
For steps to configure SB/XA Communications Server, see
“Configuring SB/XA Communications Server” on page 7-25.
On client computer
❑
❑
Regardless of the Security option, SB/XA Browser Client or
SB/XA Rich Client must be configured with the name of the
SB/XA Communications Server computer, and the
Authentication Type must be set to SBXAUserNamePassword.
For details on configuring the client, see “Customizing configuration on the client” on page 6-35.
If the Security option is Message or Transport, the root certificate must be installed in the Trusted Root Certification Authorities store on the client computer. This is necessary so that the client can verify the server certificate sent by SB/XA Communications
Server.
For steps to install the root certificate, see
“Installing the root certificate on the client computer” on page 7-27.
Handshake
With SBXAUserNamePassword authentication, the handshake between the client and SB/XA Communications Server is completed as follows:
1.
2.
3.
4.
5.
6.
The user logs on to a Windows computer on a network connection.
The user opens SB/XA Browser Client or SB/XA Rich Client on the client computer.
The client displays a logon prompt requesting the user’s SB/XA user
ID and password.
At the logon prompt, the user enters his or her SB/XA user ID and password.
SB/XA Communications Server passes the credentials entered by the user to SB/XA Application Server.
The following exchange takes place during the handshake:
■
■
If the Security option is Message or Transport, SB/XA
Communications Server sends a server certificate to the client containing the name of the SB/XA Communications Server computer and the trust chain of certificate issuers.
If the Security option is Message or Transport, the client verifies that it is communicating with the SB/XA Communications
Server computer specified in the client configuration.
■
If the Security option is Message or Transport, the client checks its Trusted Root Certification Authority store for the root certificate in the trust chain used to sign the server certificate.
■
SB/XA Application Server checks the validity of the user’s
SB/XA logon credentials.
If every part the exchange is successful, the connection is opened.
Otherwise, an error message is displayed on the client and the connection request is closed.
7-12
WindowsUserNamePassword authentication
The WindowsUserNamePassword authentication type relies on a variation of the Microsoft Windows authentication protocol. This option allows the user to connect to SB/XA Communications Server from any Windows computer.
Checklist of setup tasks
■
On SB/XA Communications Server computer
❑
❑
❑
❑
❑
Install the tools needed to create certificates.
For steps to obtain tools, see “Installing the required tools” on page 7-17.
Change the logon properties of the SB/XA Communications
Server service from LocalService to a user in the Administrators group.
For steps to change logon properties, see
“Changing the logon properties of the communications service” on page 7-18.
The administrator must create or obtain a signing certificate. The signing certificate is to be used to sign a server certificate for
SB/XA Communications Server.
The administrator needs to create a server certificate for SB/XA
Communications Server. With WindowsUserNamePassword authentication, SB/XA Communications Server sends a server certificate to the client during the handshake. The server certificate contains the name of SB/XA Communications Server and the trust chain of certificate issuers.
For steps to create a server certificate, see “Creating a server certificate” on page 7-23.
The administrator must configure the SB/XA Communications
Server to use the server certificate.
For steps to configure SB/XA Communications Server, see
“Configuring SB/XA Communications Server” on page 7-25.
7-13 SB/XA Getting Started
■
On client computer
❑
❑
SB/XA Browser Client or SB/XA Rich Client must be configured with the name of the SB/XA Communications Server computer, and the Authentication Type must be set to
WindowsUserNamePassword.
For details on configuring the client, see “Customizing configuration on the client” on page 6-35.
The root certificate must be installed in the Trusted Root
Certification Authorities store on the client computer. This is necessary so that the client can verify the server certificate sent by SB/XA Communications Server.
For steps to install the root certificate, see
“Installing the root certificate on the client computer” on page 7-27.
Handshake
With WindowsUserNamePassword authentication, the handshake between the client and SB/XA Communications Server is completed as follows:
1.
2.
3.
4.
5.
The user logs on to a Windows computer on a network connection.
The user opens SB/XA Browser Client or SB/XA Rich Client on the client computer.
The client displays a logon prompt requesting credentials for SB/XA
Communications Server.
At the logon prompt, the user enters the user name and password for the SB/XA Communications Server computer domain.
The following exchange takes place during the handshake:
■
■
■
SB/XA Communications Server checks the validity of the user name and password entered.
SB/XA Communications Server sends a server certificate to the client containing the name of the SB/XA Communications
Server computer and the trust chain of certificate issuers.
The client verifies that it is communicating with the SB/XA
Communications Server computer specified in the client configuration.
7-14
7-15 SB/XA Getting Started
■
The client checks its Trusted Root Certification Authority store for the root certificate in the trust chain used to sign the server certificate.
If every part the exchange is successful, the connection is opened.
Otherwise, an error message is displayed on the client and the connection request is closed.
Setting up certificates to authenticate clients
SB/XA Browser Client or SB/XA Rich Client must authenticate to SB/XA
Communications Server before a connection can be established. Some authentication types require certificates to establish a connection.
Procedure
You must set up certificates for certain authentication types, as detailed in the following table
3.
4.
1.
2.
5.
6.
For authentication type: Certificate setup is:
Windows Not required.
SBXAUserNamePassword
■
Not required if Security = None.
■
Required if Security = Message or Transport.
Complete the tasks in the following list.
WindowsUserNamePassword Required. Complete the tasks in the following list.
Valid options by authentication type
Changing the logon properties of the communications service
Creating a signing certificate
Configuring SB/XA Communications Server
Installing the root certificate on the client computer
7-16
Installing the required tools
Complete this procedure to obtain and install the tools needed to create and set up certificates.
Procedure
1.
2.
You need to use SB/XA Rich Client to perform several steps in this procedure.
If you have not already done so, install SB/XA Rich Client on the same computer on which SB/XA Communications Server is installed.
You will need to use the makecert and certmgr tools to perform certificate setup tasks.
If you have not already done so, get these tools from the
Extra\Certificate Tools folder on the SB/XA product CD image.
Next step
Changing the logon properties of the communications service
7-17 SB/XA Getting Started
Changing the logon properties of the communications service
Complete this task to change the logon properties of the SB/XA
Communications Server service from LocalService to a user in the
Administrators group.
It is best to configure SB/XA Communications Server for certificates right after installing this software component. If you set up application connections on the SB/XA Communications Server computer before changing the logon properties from LocalService to a user in the
Administrators group, you must re-enter application connection details.
Prerequisite
Procedure
1.
2.
Stop the SB/XA Communications Server service.
Click Start > Control Panel > Administrative Tools > Services. From the list, select SB/XA Communications Server and click Stop.
Leave the Services panel open for use in the next step.
Change the logon properties of the SB/XA Communications Server service from LocalService to a user who is a member of the
Administrators group of the computer, as follows.
In the Services panel, right-click SB/XA Communications Server and click Properties.
7-18
3.
In the SB/XA Communications Server Properties window, click the
Log On
tab and enter information as follows:.
7-19 SB/XA Getting Started
In the Log on as options, This account is selected by default. The field is populated with the domain_name\LocalService. Change the value in this field to the Windows identity of a user who is a member of the Administrators group of this computer, as shown in the next example.
In the Password field, enter the password for the specified user.
In the Confirm password field, re-enter the same password for verification.
The window should now look similar to the following example.
■
To save your changes, click OK.
Next step
Creating a signing certificate
7-20
Creating a signing certificate
The administrator needs to obtain or create a signing certificate. This certificate is used to sign the server certificate for SB/XA Communications
Server.
One option is to purchase a signing certificate from a commercial certificate authority (CA).
The other option is to create a self-signed signing certificate. To perform this task, you need the makecert tool that is included in the Extra\Certificate
Tools folder in the SB/XA product download directory.
Prerequisite
Changing the logon properties of the communications service
Procedure
1.
2.
Log on as administrator to the SB/XA Communications Server computer.
Run the Command Prompt as administrator, and enter the makecert command with options as follows: makecert -n “CN=signing_certificate_name” -r -sv
signing_certificate_name.pvk
signing_certificate_name.cer
For example: makecert -n “CN=RocketU2” -r -sv RocketU2.pvk
RocketU2.cer
The makecert tool prompts you to enter a password for the private key file. Enter a password at this prompt, and make note of it for use in the next task.
This command creates two signing certificate files with these file extensions:
❑
❑
.pvk – The private key file, which the server retains for its own use.
.cer – The public key file, which the server shares externally.
7-21 SB/XA Getting Started
Next step
7-22
Creating a server certificate
The administrator needs to create a server certificate for SB/XA
Communications Server.
To perform this task, you need the makecert and certmgr tools that are included in the Extra\Certificate Tools folder in the SB/XA product download directory.
Prerequisite
Creating a signing certificate
Procedure
1.
2.
If you are not already logged on as administrator to the SB/XA
Communications Server computer from the previous task, do so now.
Run the Command Prompt as administrator, and enter the makecert command with options as follows: makecert -sk signed_by_certificate_authority_name -iv
signing_certificate_name.pvk -n
"CN=SBXACommunicationsServer_name" -ic
signing_certificate_name.cer
SBXACommunicationsServer_name.cer -sr LocalMachine -ss
My -sky exchange -pe
For example, makecert -sk RocketU2 -iv RocketU2.pvk -n
"CN=sbxa02.rocketsoftware.com" -ic RocketU2.cer sbxa02.rocketsoftware.com.cer -sr LocalMachine -ss My
-sky exchange -pe
The makecert tool prompts you to enter a password for the private key of the signing certificate. Enter the password at this prompt.
This command adds the certificate to the LocalMachine My store on the SB/XA Communications Server computer.
This command also creates the .cer public key file in the current directory.
7-23 SB/XA Getting Started
3.
Optional. If you want to verify that the server certificate was added to the LocalMachine My store, in the Command Prompt window enter the certmgr command with options as follows: certmgr -v -all -s -r LocalMachine My
This command opens a view of all certificates in the system store location LocalMachine My.
Next step
Configuring SB/XA Communications Server
7-24
Configuring SB/XA Communications Server
In this task, the administrator needs to configure SB/XA Communications
Server to specify the server certificate. SB/XA Communications Server requires this setting to verify its own server certificate when starting the
SB/XA Communications Server service.
Prerequisite
Procedure
1.
2.
3.
If you are not already logged on as administrator to the SB/XA
Communications Server computer from the previous task, do so now.
Run SB/XA Browser Client or SB/XA Rich Client as administrator on the SB/XA Communications Server computer.
In the main window, click Options > Communications Server
Configuration
.
7-25 SB/XA Getting Started
4.
Update details in the SB/XA Communications Server
Configuration
form as follows.
5.
At the User Certificate Name prompt, enter the name of the server certificate for this SB/XA Communications Server computer.
For example, sbxa02.rocketsoftware.com
It is important to enter the name of the certificate correctly. If there is no such certificate or if there is a duplicate certificate, the SB/XA
Communications Server service will fail to start in the next step.
To save the changes, click Save.
Restart the SB/XA Communications Server service.
Click Start > Control Panel > Administrative Tools > Services. From the list, select SB/XA Communications Server or SB
Communications Server and click Restart.
Next step
Installing the root certificate on the client computer
7-26
Installing the root certificate on the client computer
If you created a self-signed signing certificate, that certificate will serve as the root certificate. If you purchased a signing certificate, the root certificate used to sign the signing certificate may need to be installed if it is not already present.
As the final setup task, the administrator needs to install the root certificate in the Trusted Root Certification Authorities store on the client computer.
Prerequisite
Configuring SB/XA Communications Server
Procedure
1.
2.
Navigate to the location containing the root certificate.
Double-click the certificate (.cer) file to open it in the Certificate window.
7-27 SB/XA Getting Started
3.
In the Certificate window, the General tab is open by default. This tab displays the name of the selected root certificate, as shown in the following example.
Click Install Certificate.
7-28
4.
In the Certificate Import Wizard Welcome page, click Next.
7-29 SB/XA Getting Started
5.
Select the certificate store in which to place the root certificate, as follows.
Select the Place all certificates in the following store option and browse to the Trusted Root Certification Authorities store.
To continue, click Next.
7-30
6.
In the Completing the Certificate Import page, check the settings you specified.
7-31 SB/XA Getting Started
If your settings are correct, click Finish. A Security Warning window may ask you to verify that you want to install a certificate from the certification authority (CA) claiming to issue the certificate. Click Yes to install the certificate. The wizard imports the root certificate to the
Trusted Root Certification Authorities store.
Otherwise, if your settings are incorrect, click Back to make changes or click Cancel to quit.
7.
Optional. If you want to verify that the root certificate was installed, in the Command Prompt window enter the certmgr command with options as follows: certmgr -v -all -s -r currentUser Root
This command opens a view of all certificates in the system store location currentUser Root. You can select the Trusted Root
Certification Authorities store to verify that the root certificate is now included in this store.
7-32
Configuration for SB/XA Services
SB/XA v6.2.4 introduces SB/XA Services as a beta program. There are four new flags that pertain to this program on the SB/XA Communications
Server Configuration
screen.
Note:
You should not attempt to use these flags unless you are participating in the beta program because their use might cause problems for your system. Additionally, their use does not enable any functionality unless you have licensed your installation for the services.
For more information about SB/XA Services, see the SB/XA v6.2.4 release notes. If you are interested in participating in the beta program, contact
Rocket U2 at [email protected].
The four new flags on the SB/XA Communications Server Configuration screen are Scheduler host, Scheduler port, Start SB/XA Services, and SB/XA
Services Port
as shown in the following figure.
You must set the value in the Start SB/XA Services field to true to run SB/XA
Services. Do not use this flag unless you are participating in the beta program. If you are participating in the beta program, consult the SB/XA
Services beta documentation sent to you separately by Rocket U2. The
Scheduler host
, Scheduler port, and SB/XA Services Port fields have no effect unless Start SB/XA Services is set to true.
7-33 SB/XA Getting Started
1
Chapter 8: Setting up National
Language Support in SB/XA for
UniVerse NLS
Overview of National Language Support in SB/XA for UniVerse NLS 8-3
Software requirements . . . . . . . . . . . . . . .
Limitations . . . . . . . . . . . . . . . . . . .
Enabling an SB instance for NLS . . . . . . . . . . . . .
Chapter
8
This chapter provides instructions for setting up the environment for
National Language Support (NLS) in SB/XA for UniVerse NLS.
■
■
Overview of National Language Support in SB/XA for UniVerse
❑
❑
Enabling an SB instance for NLS
8-2 SB/XA Getting Started
Overview of National Language Support in SB/XA for
UniVerse NLS
The National Language Support (NLS) feature of the UniVerse database server is incorporated in SB/XA for UniVerse NLS. With the complete functionality of NLS implemented in SB/XA, you have the ability to internationalize SB-developed applications for a diverse customer base.
When you install SB/XA for UniVerse NLS on a system that has an SB account, the account is upgraded to use the NLS-enabled version of
UniVerse.
For more information about the National Language Support feature that is implemented in UniVerse, see the UniVerse NLS Guide.
Software requirements
If you require character-based access to use National Language Support features in SB/XA for UniVerse NLS, in addition to the other software requirements for SB/XA, you must install and configure wIntegrate v6.3.2 or later.
Limitations
The current version of SB/XA for UniVerse NLS has the following limitations:
■
■
Use of NLS with the UniData database server is not supported.
The SBClient user interface is not supported in SB/XA for UniVerse
NLS.
8-3
Enabling an SB instance for NLS
The system administrator must perform a few tasks to enable an SB instance for NLS. After setup is complete, all SB accounts within this instance have the same capabilities of NLS that are available to other UniVerse accounts. You can localize the user interface (UI) in an SB developed application, adapting
UI elements for alternative languages or regional differences.
Prerequisite
After installing UniVerse NLS, you need to set an appropriate map on all files that store multibyte data. Before changing the NLSDEFFILEMAP parameter from its default of ISO8859-1+MARKS, you must convert any files that might contain high-bit data to an explicit map of NONE, using UNICODE.FILE.
Install and configure the required SB/XA components as detailed in:
■
■
Chapter 3,
“Chapter 3: Installing SB/XA components on Windows”
Chapter 4,
“Chapter 4: Installing SB/XA Application Server on
About this task
In addition to this guide, refer to the following manuals to complete this procedure. The manuals are available at http://u2.rocketsoftware.com/resources/technical-documentation
■
■
■
■
UniVerse NLS Guide
Administering SB/XA
Using wIntegrate
UniVerse BASIC
8-4 SB/XA Getting Started
Procedure
1.
Configure UniVerse:
a.
Shut down UniVerse:
# bin/uv -admin -stop b.
Use a text editor (such as vi or Notepad) to edit the uvconfig file for your operating system.
■
For each of the mapping parameters that are listed in the following table, specify a value of
NONE
.
Parameter Description
NLSDEFFILEMAP Specifies the name of the map to use for hashed files without assigned maps. This occurs if a hashed file was not created on an NLS system and has not had a map defined for it by the SET.FILE.MAP command.
NLSDEFDIRMAP Specifies the name of the map to use for type 1 and type 19 files without assigned maps. This occurs if a type 1 or type 19 file was not created on an NLS system and has not had a map defined for it by the SET. FILE.MAP command. This map applies only to the data in records, not to record ID.
NLSNEWFILEMAP Specifies the name of the map to use for new hashed files created when NLS mode is enabled. A value of NONE (the default value) indicates that data is to be held in the internal
UniVerse character set.
NLSNEWDIRMAP Specifies the name of the map to use for new type 1 and type
19 files created when NLS mode is enabled. This map applies only to the data in records, not to record IDs.
NLSDEFPTRMAP Specifies the name of the default map to use for printer output. This map is used if a printer does not have a map defined for it in the &DEVICE& file.
NLSDEFTERMMAP Specifies the name of the default map to use for terminal input or output. This map is used if a terminal does not have a map defined for it in its terminfo definition. The
SET.TERM.TYPE MAP command overrides this setting.
NLS mapping parameters
8-5
Parameter Description
NLSDEFDEVMAP
NLSDEFGCIMAP
NLSDEFSRVMAP
NLSDEFSEQMAP
NLSOSMAP
Specifies the name of the default map to use for device input or output. This map is used for all devices except printers that do not have a map specified in the &DEVICE& file. The
ASSIGN MAP command overrides this setting.
Specifies the name of the default map to use for string arguments passed to and from GCI subroutines. This map is used if the GCI subroutine does not explicitly define a map.
Specifies the name of the default map to use for passing data to and from client programs. This map is used if the client program does not specify a server map.
Specifies the name of the default map to use for sequential input or output for files or devices without assigned maps.
The SET.SEQ.MAP command overrides this setting.
Specifies the name of the map to use for file names or record
IDs visible to the operating system. This chiefly affects
CREATE.FILE and record IDs written to type 1 or type 19 files
NLSDEFSOCKMAP Specifies the name of the map to be associated with sockets that are either explicitly created through Basic APIs or implicitly created through other APIs (that is, CallHTTP).
NLS mapping parameters (continued) c.
d.
■
■
For the NLSMODE parameter, specify a value of 1. This setting is required to turn on NLS.
The default setting for the NLSLCMODE parameter is 0
(Disable locales). Change the value to 1 (Enable locales). This parameter has no effect unless NLSMODE is set to 1.
For more information about the uvconfig file parameters and changing parameter values, see the “Getting Started” chapter of the UniVerse NLS Guide.
Run the UniVerse program uvregen:
# bin/uvregen
Start UniVerse:
# bin/uv -admin -start
8-6 SB/XA Getting Started
2.
3.
4.
Configure SB/XA:
a.
In the SBInstance Setup window, set Code Page to 65001 (UTF-
8).
b.
In the Printer Class Definition window on the Attributes tab, define a default font that will display all of the characters that you require.
For instructions, see “Defining stationery types and attributes for XPS.CLASS” in Chapter 5, “Admin Menu,” in Administering
SB/XA.
If character-based access is required, configure wIntegrate:
In the wIntegrate Terminal window, set the following values:
❑
❑
Terminal emulation: vt220
Extensions
: sb_keys
❑
Host Encoding
: UVUTF-8
For instructions, see “Setting Up Terminal Emulation” in the Using
wIntegrate manual.
Configure UniVerse BASIC:
In the UniVerse file that stores your UniVerse BASIC program source code, make the following NLS function changes:
❑
Change CHAR to UNICHAR. CHAR(X) becomes
UNICHAR(X).
❑
❑
Change SEQ to UNISEQ. SEQ(X) becomes UNISEQ(X).
Change LEN to LENDP. LEN(X) becomes LENDP(X,”UTF8”).
For more information, see the UniVerse BASIC manual.
8-7
Stiahnuť
Verejný odkaz bol aktualizovaný
Verejný odkaz na váš chat bol aktualizovaný. You may view and manage your chat links after registration here.
Verejný odkaz na dokument
Reklama
