Release Notes for Phone.com Connector 1.0

This document covers the following topics:

• Introduction
• Target Audience
• Installing the Phone.com Connector
• Required Software
• Licenses
• Installed Files
• Known Issues
• Customer Support

Introduction

The Phone.com Connector brings wireless application protocol (WAP) functionality to the BusinessWare environment; it enables a BusinessWare server to send notifications to wireless devices, such as mobile phones, via a Phone.com UP.Link Server (a WAP Gateway). The Phone.com Connector is an additional component for BusinessWare that requires a separate license.

The Phone.com Connector is comprised of a target flow, a connection model template, and the underlying .jar files that comprise these software components. The package also includes Linar J-Integra, a COM-Java bridging tool. A license for J-Integra is included in the package.

Target Audience

The Phone.com Connector is intended for BusinessWare users who want to incorporate WAP-based notifications in their BusinessWare solutions.

Installing the Phone.com Connector

The file PhoneDotCom_1.0_Setup.exe comprises the installation package for the Phone.com Connector for Windows NT. Double-clicking on the file (or executing file from the Windows NT Run dialog or a command line) launches the InstallShield wizard, which guides the installation process. See Installing Phone.com Connector on Windows NT for more information.

System requirements for this release are discussed in Required Software.

Required Software

The Phone.com Connector requires:

• BusinessWare 3.0.2
• Windows NT 4.0 (Server or Workstation, with Service Pack 5 installed)
• Openwave UP.SDK 4.1
• Linar J-Integra 1.3.7
• JDK 1.2.2 (also a requirement for the BusinessWare installation)

Licenses

The Phone.com Connector 1.0 requires a separate license from Vitria; contact your Vitria representative to obtain the appropriate license.

Installed Files

The Phone.com Connector installation file is available for Windows NT:

PhoneDotComConnector_1.0_Setup.exe

When the Phone.com Connector is installed, the following files are added to the BusinessWare installation directory. The default BusinessWare directory is \program files\vitria\BW3x\ for Windows NT :

inderdef
Filename	Description
vtPhoneDotComConnectorEvents.idl	IDL (interface definition language) file for the Phone.com events.
jintegra
JintegraLicense.class	License from Linar that enables use of the J-Integra COM-Java bridge with the Phone.com Connector.
ntvinv.dll	Library that enables native mode support for software bridge.
setdllhost.exe	Utility program to register the COM-Java bridge.
java\win32\
jintegra.jar	Java archive (Linar J-Integra) that comprises a software bridge between Microsoft COM (component object model) used by Phone.com library and the Java classes that comprise the connector
pdcupnotify.jar	Java archive generated by J-Integra that maps to Phone.com notification library (...\UPSDK\lib\UPNotify.dll).
java\win32\com\vitria\connectors\phonedotcom\msg
PhoneDotComMessages.class	Java class file containing all message text and labels for the connector.
java\win32\com\vitria\connectors\phonedotcom\util
StartClient.bat	Batch file that launches the Java command-line utility (TestWindow.class and several linked .class files) for testing Phone.com configuration.
TestWindow.class	Main class for the Java command-line utility for testing the connector in conjunction with Openwave UP.Simulator.
doc\connector\phonedotcom
wap_connector.html	Phone.com Connector information and usage guide
wap_connector_relnote.html	Phone.com Release Notes (this document)
wap_connector_install_nt.html	Installing the Phone.com Connector on Windows NT

Known Issues

• To implement security in this release of the Phone.com Connector, you must manually launch the BusinessWare service (rather than running as a Windows NT Service in the control panel). After installing the connector, you should:
1. Open the Windows NT Services control panel and stop the BusinessWare service.
2. Open a Windows NT command prompt and then navigate to the %VITRIA%\data sub-directory.
3. Enter java com.vitria.bserv.BServMain to launch BusinessWare. (By launching Bserv within this sub-directory, your BusinessWare instance will load any existing connection models and other BusinessWare objects that you may have already configured.)
4. Open the BusinessWare Console from the Windows NT start menu and create your connection models as you normally would.
• SkipOn does not work correctly. This problem will be fixed in the BusinessWare 3.1.2 release.
• If you purge a connection model that includes the Multi-threaded Subscriber flow, you must also purge the channel itself before re-starting the connection model; if you don't, the connection model will process events from the channel a subsequent time. The Channel Source flow does not have this issue. If you do not plan on implementing multi-instancing in the connection model, you should use a Channel Source flow instead of the Multi-threaded Subscriber in the model and avoid this issue entirely.
• For general connector known issues see the BusinessWare Release Notes.

Copyright � 1995-2001 Vitria Technology, Inc. All rights reserved.
Last updated: 24-Feb-2024 [Defunct]