P rereq u i si t e K n o w l ed g e R eq u i rem en t s
Before you use the webMethods BroadVision Adapter, you should be familiar with the
following:
g webMethods Developer
g webMethods Integration Server
g JavaScripts
g BroadVision One-to-One Enterprise Server
System Requirements
The following sections describe the software and hardware requirements of the
BroadVision Adapter. Be sure the systems on which you will use the BroadVision
Adapter meet these requirements before you proceed with the installation.
The BroadVision Adapter distribution consists of two adapters:
g The Integration Server (IS)-BroadVision Adapter, which is an inbound adapter.
g The BroadVision-IS Adapter, which is an outbound adapter.
g Solaris
g HP-UX
Hardware Requirements
The BroadVision Adapter has no hardware requirements beyond those of the
webMethods Integration Server and the BroadVision Server. You will find the hardware
requirements for these products described in the documentation that came with those
products.
I n st al l i n g t h e B ro ad V i si o n A d ap t er
The BroadVision Adapter consists of two pieces: the IS-BroadVision Adapter and
the BroadVision-IS Adapter.
Stage Description
1 Install the IS-BroadVision Adapter.
3 Verify and enable the installation of the CORBA Service piece of the IS-
BroadVision Adapter.
4 Verify and enable the installation of the Session Portal piece of the IS-
BroadVision Adapter.
A log of the installation is saved for each adapter that you install, as follows:
Adapter Log File
IS-BroadVision ServerDirectory\BroadVisionInstall.log
BroadVision-IS $BV1TO1\BroadVisionInstall.log
If the Integration Server and the BroadVision Server are installed on the same machine,
both logs will be combined and saved as $BV1TO1/ BroadVisionInstall.log.
Caution: If you have not yet installed the webMethods Integration Server, install it
before you complete the following procedure.
• In a UNIX console:
JVMExecutable –cp WmBroadVision_en_US.jar run -console
/opt/webMethods/IntegrationServer4
5. If you are installing on a UNIX platform, the wizard prompts you for the
path of your JVM. The installer requires a JVM to perform certain tasks
during the installation. Valid versions of JVM include Sun’s JDK 1.2 and
1.3. For example:
/usr/local/java/1.2.2/bin/java
6. The wizard installs and enables the BroadVision55 package and the
WmBVExample package on the webMethods Integration Server.
7. Click Exit.
Caution: Under Integration Server version 3.x, the installation program installs some
upgrades for guaranteed delivery. These upgrades will be removed upon un-installation.
Caution: Under Integration Server version 4.0.1 and later, you might need to assign a
webMethods Integration Server Access Control List (ACL). For information about doing
this, see the webMethods Integration Server Administrator’s Guide.
Caution: If you have not yet installed the BroadVision Server, install it before you
complete the following procedure.
Caution: If you are installing under UNIX, and you are using BroadVision One-to-One
version 5.5, you must login as root in order to install the BroadVision-IS adapter.
However, if you are using BroadVision One-to-One version 6.0, you must login as the
user BroadVision in order to install the BroadVision-IS adapter.
bvconf shutdown
• In a UNIX console:
JVMExecutable –cp WmBroadVision_en_US.jar run -console
/opt/bv1to1
7. Specify whether you want the wizard to install the sample scripts required
by the BroadVision Adapter tutorial.
8. If you are installing on a UNIX platform, the wizard prompts you for the
path of your JVM. The installer requires a JVM to perform certain tasks
during the installation. Valid versions of JVM include Sun’s JDK 1.2 and
/usr/local/java/1.2.2/bin/java
10. Click Next. The installation program installs wmbvsn55 in the $BV1TO1
directory on the BroadVision Server.
2. Verify that files OrbixWeb.jar and OrbixNames.jar appear in your Integration Server’s
lib directory.
3. Modify the server.bat file (server.sh on UNIX) to load the OrbixWeb.jar and
OrbixNames.jar.
• If you are running Integration Server 3.6 under HP-UX, update the SHLIB_PATH
command by adding the text in bold shown below:
SET SHLIB_PATH=${JDKDIR}/lib/native_threads:${JDKDIR}/lib/
native_threads/PA_RISC2.0/classic:${SERVDIR}/lib:${SHP}
• If you are running Integration Server 4.0.1 or later under HP-UX, update the
SHLIB_PATH command by adding the text in bold shown below:
SET
SHLIB_PATH=${JAVA_ROOT}/lib/native_threads:${JAVA_ROOT}/lib
/native_threads/PA_RISC2.0/classic:${B2B_ROOT}/lib:${SAVED_
HP}
• If you are running Integration Server 4.0.1 or earlier under UNIX, update the
UMA command by adding the text in bold shown below:
• If you are running Integration Server 4.0.1 under Windows, update the
JAVA_ROOT command to point to the correct JDK. This JDK must be Sun’s
JDK 1.2.2 or later.
• If you are running Integration Server 3.6 or earlier under Windows, update the
SCMD command by adding the text in bold shown below:
• If you are running Integration Server 4.0.1 or earlier under Windows, update the
UMA command by adding the text in bold shown below:
Note: If you shut down and then re-start your BroadVision Server, you must re-enable your IFR
and put your IDL files back into the IFR.
Stage 4 Verifying and Enabling the Installation of the Session Portal Piece of
the IS-BroadVision Adapter
If using Solaris or HP-UX:
Note If you are installing on HP-UX, in the instructions below, replace the suffix .so with the
suffix .sl.
1. Verify that the file libwmSessionPortal.so appears in your Integration Server’s lib
directory.
2. Copy the files libsessionHandle.so.1 and libbvcallin.so.1 from $BV1TO1 to the lib
directory of your Integration Server directory.
libsessionHandle.so.1
libbvcallin.so.1
libwmSessionPortal.so
/etc/opt/BVSNsmgr
Note: Your system administrator should give you the bvsm.cfg file. This file pertains to your
default Interaction Manager (IM). However, if a named IM is running on your BroadVision
server, you should copy that configuration file instead of bvsm.cfg. If you want to change your
configuration file, shut down your Integration Server first.
2. Copy the following files from c:\bv1to1\bin to your Integration Server’s BroadVisiondll
directory.
• bvcore.dll
• bvidl.dll
• callin.dll
• libscfg.dll
• libsmgr_util.dll
• mny204d.dll
• remoteSession.dll
• tls704d.dll
• itglm301.dll
• itlmm301.dll
• itm_m301.dll
• itolm301.dll
• If you are running Integration Server 3.6 or earlier under Windows, update the
PATH command by adding the text in bold shown below:
SET PATH=%SLP%;%SERVDIR%\lib;%SERVDIR%\BroadVisiondll
• If you are running Integration Server 4.0.1 or earlier under Windows, update the
PATH command by adding the text in bold shown below:
SET PATH=%SAVED_PATH%;%B2B_ROOT%\BroadVisiondll
c:\bv1to1_var\BVSNsmgr
Note: Your system administrator should give you the bvsm.cfg file. This file pertains to your
default Interaction Manager (IM). However, if a named IM is running on your BroadVision
server, you should copy that configuration file instead of bvsm.cfg. If you want to change your
configuration file, shut down your Integration Server first.
In this registry key, verify that your system has the following variable:
3. In your BroadVision root directory, verify that the following files are included:
• $BV1TO1/wmbvsn55/CLASSES/wmCorbaServer.jar
• $BV1TO1/wmbvsn55/CLASSES/wmBvIdl.jar
• $BV1TO1/wmbvsn55/CLASSES/client.zip
• $BV1TO1/wmbvsn55/CLASSES/client.jar
• $BV1TO1/wmbvsn55/script_lib/wmMessages.msg
• $BV1TO1/wmbvsn55/script_lib/wmSvr.jsi
• $BV1TO1/wmbvsn55/script_lib/wmBvjSrv.sh
(Note that Execute permission is required.)
• $BV1TO1/wmbvsn55/script_lib/wmMessages.log
• $BV1TO1/wmbvsn55/script_lib/wmComponent.cfg
• $BV1TO1/wmbvsn55/doc/readme.txt
• $BV1TO1/wmbvsn55/doc/ReleaseNotes.html
• $BV1TO1/wmbvsn55/doc/BroadVisionInstallGuide.pdf
• $BV1TO1/wmbvsn55/doc/BroadVisionUserGuide.pdf
If UNIX:
cd $BV1TO1/bin/svr
If Windows 2000:
cd $BV1TO1\bin
5. Run the following command to make a soft link for your CORBA server
wmCorba_srv, which is embedded in wmCorbaServer.jar:
If UNIX:
ln –s $BV1TO1/wmbvsn55/script_lib/wmBvjSrv.sh wmCorba_srv
If Windows 2000:
cp $BV1TO1/wmbvsn55/script_lib/wmBvjSrv.sh wmCorba_srv
WMDIR=$getenv(BV1TO1)+ "/wmbvsn55/script_lib"
d) Search for the string BV_LD_LIBRARY_PATH and append the following lines:
e) Search for the string bv_js_library_dir and append the following lines:
f) Search for the string classpath and add the following lines above the classpath:
IT_JAVA_INTERPRETER=$env(BV1TO1) + "/jre/bin/java"
IT_DEFAULT_CLASSPATH=
$env(BV1TO1_VAR) + "/orb"
+":" + $env(BV1TO1) + "/orbix/lib/OrbixNames.jar"
+":" + $env(BV1TO1) + "/orbix/lib/OrbixWeb.jar"
+":" + $env(BV1TO1) + "/wmbvsn55/CLASSES/wmBvIdl.jar"
+":" + $env(BV1TO1) + "/wmbvsn55/CLASSES/wmCorbaServer.jar"
+":" + $env(BV1TO1) + "/wmbvsn55/CLASSES"
+":" + $env(BV1TO1) + "/orbix/tools/jre/lib/rt.jar"
+":" + $env(BV1TO1) + "/orbix/tools/jre/lib/swingall.jar"
g) Search for the Remarks string Global processes and add the following line:
process wmCorba_srv {
parameter
logdir=$env(BV1TO1_VAR) + ”/logs/hostname”
}
h) Search for the string cachecontrol_path and add the following lines:
36 catalog BroadVision_root_directory/wmbvsn55/script_lib/
wmMessages.msg
For example, if your BroadVision root directory is /opt/bv1to1, then the command will
look like this:
36 catalog /opt/bv1to1/wmbvsn55/script_lib/
wmMessages.msg
Search for the string default_object_path and append the following line:
+ $getenv(BV1TO1) + "/wmbvsn55/lib"
bvconf execute
11. Enable your BroadVision Interface Repository (IFR) by running the following
commands on the BroadVision Server:
Note: If you shut down and then re-start your BroadVision Server, you must re-enable your IFR
and put your IDL files back into the IFR.
I n s t a l l i n g t h e I S - B r o a d V i s i o n A d a p t e r i n a C l u st e r e d
Environment
You must install the IS-BroadVision Adapter on each webMethods Integration
Server in the cluster.
U n - i n st al l i n g t h e B ro ad V i si o n A d ap t er
When you un-install the BroadVision Adapter, you must un-install both the IS-
BroadVision Adapter and the BroadVision-IS Adapter. If both adapters are installed
on the same machine, you can un-install them both at the same time. If this is the
case, a log of the un-installation will be saved as
ServerDirectory\BroadVisionUninstall.log, where ServerDirectory is the
directory in which you installed your Integration Server.
If you un-install just one of the adapters, a log of the un-installation will be saved in one
of the following log files:
Adapter Log File
IS-BroadVision ServerDirectory\BroadVisionUninstall.log
BroadVision-IS $BV1TO1\BroadVisionUninstall.log
3. The un-install program asks you whether you want it to clean the
repository with entries specific to the adapter. If this is an upgrade, the
entries should not be deleted. If the repository is remote, it should be
started for deletions to occur.
3. The un-install program will then prompt you whether you want it to delete
from the repository any entries specific to the adapter. If the repository is
a remote repository, you should start it if you want these entries to be
deleted.
Caution: You must login as root in order to un-install the BroadVision-IS Adapter if
using BroadVision One-to-One 5.5.
However, you must login as BroadVision user in order to un-install the BroadVision-IS
Adapter if using BroadVision One-to-One 6.0.
1. Change directory to $BV1TO1/_uninst/BroadVision.
B
BroadVision-IS
platform support 3
software requirements 3
H
hardware requirements 3
I
installation overview 3
installation prerequisites 2
installing
BroadVision-IS Adapter 5
in clustered environment 14
IS-BroadVision Adapter 4
IS-BroadVision
platform support 2
software requirements 3
P
platform support
BroadVision-IS Adapter 3
IS-BroadVision Adapter 2
R
requirements, system 2
S
software requirements
BroadVision-IS Adapter 3
IS-BroadVision Adapter 3
system requirements 2
U
un-installing the BroadVision Adapter 14
V
verifying and enabling
installation of BroadVision-IS Adapter 11
installation of CORBA Service 7
VERSION 1.2
webMethods, Inc.
3930 Pender Drive
Fairfax, VA 22030
USA
703.460.2500
http://www.webmethods.com
webMethods for Trading Networks, webMethods for Partners, webMethods Developer, webMethods Integration Server,
webMethods EDI Adapter, webMethods Enterprise Integrator, webMethods Enterprise Server, and the webMethods logo are
trademarks of webMethods, Inc. “webMethods” is a registered trademark of webMethods, Inc. All other marks are the property of
their respective owners.
The software described in this manual contains encryption software from RSA Data Security, Inc.
Copyright © 2001 by webMethods, Inc. All rights reserved including the right of reproduction in whole or in part in any form.
The software described in this manual contains International Components for Unicode (ICU4J) software.
Copyright © 1995-2001 by International Business Machines Corporation and others. All rights reserved.
webM-BroadVision-IG-20010719
CONTENTS
iii
iv