Liveinterface Installation Configuration Guide
Liveinterface Installation Configuration Guide
Version 12
Installation and Configuration Guide
DOC-LI12-CG-050108
Installation and Configuration Guide 5 May, 2010
This publication and the software described in it are copyrighted with all rights reserved.
Under the copyright laws, this publication and the software may not be copied, in whole
or part, without written consent of IntelliCorp, Inc. Under the law, copying includes
translating into another language or format.
The software described in this publication is furnished under a license agreement with
IntelliCorp, Inc. and may be used or copied only in accordance with the terms of the
agreement.
IntelliCorp, Inc.
2900 Lakeside Drive, Suite 221
Santa Clara, CA 95054
(408) 454-3500
Technical Support
(408) 454-3555
FAX: (408) 454-3647
livesupport@[Link]
2
Installation and Configuration Guide 5 May, 2010
Contents
INTRODUCTION !5
CONTACTING INTELLICORP !5
SYSTEM REQUIREMENTS !6
HARDWARE !6
SOFTWARE 6!
SAP AUTHORIZATION PROFILES 6!
INSTALLING LIVEINTERFACE !8
PRE-INSTALLATION BACKUP AND PURGE TASKS !9
COPY THE LIVEINTERFACE INSTALLATION FILES !10
RENAME THE .DAT FILES ! 10
CREATE THE LIVEINTERFACE INSTALLATION ROLE !11
LOAD THE INSTALLATION PROGRAM ! 12
RUN THE INSTALLATION PROGRAM ! 15
What the Installation Program Does ! 15
How to Run the Installation Program ! 17
Re-running the Installation Program ! 20
INSTALLATION DETAILS !21
STEP 1: CHECKING FOR DUPLICATE OBJECTS !21
STEP 2: CREATING LIVEINTERFACE DEVELOPMENT CLASSES ! 21
STEP 3: INSTALLING LIVEINTERFACE DATA DICTIONARY OBJECTS ! 21
STEP 4: UPDATING TRANSPORT LAYERS ! 21
STEP 5: IMPORTING LIVEINTERFACE TABLE DATA ! 21
STEP 6: CREATING CONTROL RECORDS AND SETTING LIVEINTERFACE INTERNAL COUNTERS ! 21
STEP 7: INSTALLING AUTHORIZATIONS AND PROFILES ! 22
STEP 8: INSTALLING LIVEINTERFACE EVENTS AND BACKGROUND JOBS ! 22
STEP 9: SYNTAX CHECKING LIVEINTERFACE PROGRAMS AND FUNCTION GROUPS ! 23
POST INSTALLATION PROCEDURES !24
SETTING LIVEINTERFACE SECURITY AND AUTHORIZATIONS !24
Activity Hierarchy ! 26
Creating Authorizations and Profiles ! 26
Assigning Profiles to Users ! 26
CONFIGURING LIVEINTERFACE WORKBENCH USERS ! 27
Setting a User Configuration ! 28
Setting Operational Defaults ! 30
INSTALLING WORKFLOW TASKS ! 32
REVIEWING AND ADJUSTING PRINT SPECIFICATIONS ! 35
UPGRADE PROCEDURES !36
RENAMING INTERFACES !36
REGENERATING INTERFACES ! 36
Mass Generation Utility Prerequisites ! 36
Running the Mass Generation Utility ! 37
CONVERSION PROCEDURES !39
CONVERSION UTILITY !39
Running the Conversion Utility ! 39
3
Installation and Configuration Guide 5 May, 2010
2
Installation and Configuration Guide 5 May, 2010
Introduction
This document describes the installation and configuration of IntelliCorp’s LiveInterface
software. The primary audience is expected to be R/3 administrators who are
responsible for the maintenance of SAP R/3 systems.
For any information that was not available at the time this manual was completed,
please see the Release Notes file, [Link], which is installed to the
LiveInterface\Documentation distribution directory. This directory also contains
the file for this manual, in Word format.
Contacting IntelliCorp
If you have any questions about LiveInterface, you can contact IntelliCorp Technical
Support in a number of ways:
To raise support issues using our on-line Help Desk, please visit:
[Link]
[Link]
The iShare community site allows customers, partners and IntelliCorp staff to share
information about IntelliCorp products. This can be found at:
[Link]
Email: livesupport@[Link]
Email: livesupport@[Link]
3
Installation and Configuration Guide 5 May, 2010
System Requirements
The system requirements for a LiveInterface installation are as follows:
Hardware
The LiveInterface distribution files are delivered as a ZIP file. The contents of the ZIP file
should be extracted to a distribution directory on either your SAP server, or a workstation
that has network access to your SAP server.
The files and logs created on your SAP server during an installation of LiveInterface
require approximately 60 MB of disk space.
Software
LiveInterface is supported for SAP systems running under UNIX or Windows.
LiveInterface supports SAP R/3 releases 4.6x, 4.7x, ECC 5.0, ECC 6.0, SAP APO and
SAP BW.
To create an SAP role which includes the specific authorizations required to install
LiveInterface, see the ‘Create the Live Interface Installation Role’ section on page 11.
When the LiveInterface installation is run by a specific user, all of the standard
LiveInterface Background Jobs and Events that are created are assigned to that user.
For this reason, we recommend that you define a generic SAP user ID for the
LiveInterface installation process on each of the SAP clients where LiveInterface for will
be installed. For example, you might use LI, LI*, or LIADM.
Print specifications should be defined under ‘User Defaults’ for each of these user IDs,
on each of the clients where LiveInterface will be installed. The user name must be the
same on each client, and when installing LiveInterface, you must log on with this name.
You can install LiveInterface on clients other than the one where you are logged on using
the LiveInterface installation client selection screen.
2
Installation and Configuration Guide 5 May, 2010
If the user IDs for each installed client do not exist, are not generic, or do not have valid
print specifications, the following problems may occur:
• Background Jobs - You can install the Background Jobs on a client where you
do not have a user ID defined. This will result in these jobs having invalid user
IDs assigned to them, causing them to fail at runtime. You must ensure that you
have a valid logon on each of the clients on which you want to install the
LiveInterface background jobs.
• Print Specification User Default Settings - In SAP, you should ensure that the
user IDs for each of the clients have Print Specifications defined in the ‘User
Defaults’ section. Otherwise, SAP will terminate the LiveInterface Background
Jobs at runtime. In addition, SAP R/3 will be unable to schedule or release
LiveInterface event driven and periodic jobs. SAP R/3 logs these errors in the
SAP system log.
3
Installation and Configuration Guide 5 May, 2010
Installing LiveInterface
To install LiveInterface, carry out the following steps:
• If you are upgrading from an earlier release of LiveInterface, perform the required
pre-installation backup and purge tasks.
• If you are upgrading from an earlier version of LiveInterface, perform the required
upgrade procedures, such as regenerating your interfaces.
2
Installation and Configuration Guide 5 May, 2010
If you are upgrading from a prior version of LiveInterface, we recommend that you use
the Purge utility to purge all old, unneeded data from LiveInterface tables. This will
improve the performance of the installation program, which must read through and
upgrade all tables as part of the installation process.
For files that you think you may need to restore at some time in LiveInterface, follow the
steps below. Note that you should restore only data that is absolutely necessary, as
restoring too much data will affect the performance of the installation program.
3. Verify that all data has been restored successfully by viewing it using the
LiveInterface Healthbenches and Activity Logs.
3
Installation and Configuration Guide 5 May, 2010
• For UNIX servers, you must log on as the root user ID to copy the files. The
directory to which the files are copied must have read, write and execute
permissions for all users.
• For Windows servers, you must log on as <sid> adm. The directory to which
you copy the files must be in NTFS format, and the copied files must be
writeable.
• If you copy the files to your SAP server using FTP, be sure to transfer them in
binary mode.
• zupi30ag.dat_pre47
• zupi30ag.dat_47+
2
Installation and Configuration Guide 5 May, 2010
• For UNIX servers, you must log on with the root user ID to copy the files and
then set the authorization mode of both the copied files and the directory to
read, write, execute for all users (chmod 777).
• For Windows servers, you must log on as <sid> adm. The directory to
which you copy the files must be in NTFS format, and the copied files must
be writeable.
• If you copy files from the distribution directory to your SAP server using FTP,
be sure to transfer the files in binary mode.
3. Use the STMS transaction to import the transport. This provides an SAP role
named /ICORP/LI_AUTHS.
3
Installation and Configuration Guide 5 May, 2010
2. Check to make sure that you do not have any objects whose names conflict with
the names of the LiveInterface installation objects:
Development Class
/ICORP/ZUIP
Installation Programs/Includes
/ICORP/ZUININS0
/ICORP/ZUININS1
/ICORP/ZUININS2
/ICORP/ZUININS3
/ICORP/ZUININS4
/ICORP/ZUININS5
/ICORP/ZUININS6
/ICORP/ZUININS7
/ICORP/ZUININS8
/ICORP/ZUININS9
/ICORP/ZUPDEVCT
/ICORP/ZUPINST1
/ICORP/ZUWFINST
3. At the operating system command prompt, change to the directory into which you
copied the LiveInterface files and view the contents of the INSTALL file in this
directory. A file like the following is shown (the actual transport/change request
numbers may be different in your file). This file will provide you with the file
names you need to complete the installation procedure.
#
! If your users typically log on to SAP in a language other than English, contact
IntelliCorp Technical Support for information on running the LiveInterface
Internationalization Utility after the LiveInterface installation is complete.
2
Installation and Configuration Guide 5 May, 2010
*----------------------------------------------------------------------
*
* Take the following steps to create the LiveInterface install program
*
*----------------------------------------------------------------------
*
*----------------------------------------------------------------------
*
* If step 6/6a finishes with a return code greater than 4,
* call the LiveInterface support desk.
* Once the above steps are complete, log in to SAP and run
* the LiveInterface install program (/ICORP/ZUPINST1) from transaction
* SE38.
*----------------------------------------------------------------------
*
4. Follow the directions in the INSTALL file to copy the specified files to the SAP
cofiles and data directories, add the specified file to the TP buffer, and import
the file.
3
Installation and Configuration Guide 5 May, 2010
5. Use the SAP R/3 SE01 or SE09 transaction to view the transport log for the
correction that was imported. Review this log before continuing, to make sure no
errors occurred. A Return Code of 0 or 4 indicates success, while a Return Code
of 8 or higher indicates an error. The log is displayed in an SAP workbench like
that illustrated below.
View any branch of the workbench by double-clicking it to display a log screen like that
illustrated below:
2
Installation and Configuration Guide 5 May, 2010
The installation process may take up to three hours. During this time, progress
messages will be shown in the status bar at the bottom of the screen. If you are
upgrading from a previous version of LiveInterface, you can decrease the amount of time
required to install LiveInterface by purging all unneeded data before running the
installation program. See page 9 for details.
During the installation, the ABAP installation program /ICORP/ZUPINST1 creates a log
of the events that occur during the process. A log file is written to the screen, and also
stored in the [Link] text file in the working directory specified when you run the
installation program.
• Verifies that the LiveInterface installation files are in the specified working
directory.
• Verifies that the log file can be created in the working directory.
• Verifies that SAP’s transport ‘tp’ functions are configured and working correctly.
3
Installation and Configuration Guide 5 May, 2010
After performing these checks, the installation program proceeds to install LiveInterface
by carrying out the following steps. For more details on each step, see the Installation
Details section on page 21.
Minor errors and warnings will be reported after the installation. If a major failure occurs
in any step, that step will be terminated and /ICORP/ZUPINST1 will stop without going
on to the next step. You can restart the installation process from the step that failed or
any previous step after contacting IntelliCorp Technical Support for the step password.
2
Installation and Configuration Guide 5 May, 2010
1. Make sure all LiveInterface users are logged off the system. SAP users need not
log off.
2. If you are upgrading from a previous version of LiveInterface and your users
have made any changes to the structure of the LiveInterface authorization object
(ZAUTHCUST), make sure this object is not in revised status or locked on a
change request.
3. Log on to the SAP R/3 database server under the SAP R/3 user ID identified on
page 6, or as a user with the /ICORP/LI_AUTHS role assigned, and execute
transaction SE38. Type /ICORP/ZUPINST1 in the Program field, and click the
‘Execute’ button. The first installation screen is displayed:
Windows NT system?
If you are installing LiveInterface on a Windows system, the ‘Windows NT’ system
checkbox is selected automatically.
3
Installation and Configuration Guide 5 May, 2010
Note that the directory entered here is also the directory where the installation log will be
found.
Transport Layer
If you wish to be prompted for a transport request when you apply LiveInterface patches,
select a transport layer defined on your system.
If the ‘Transport Layer’ field is left blank, no transport layer will be associated with
LiveInterface development classes. When you apply LiveInterface patches, you will be
prompted for a local request, which cannot be transported to another system.
6. Select all clients on which LiveInterface will run. The LiveInterface client control
records, background jobs, authorization objects, and profiles will be installed for
each selected client.
2
Installation and Configuration Guide 5 May, 2010
7. Click ! or press F8. Installation will take up to three hours. During this time,
the lines being written to the log file ([Link]) will be shown in the status
bar at the bottom of the screen. At the end of the installation, the log file is
displayed.
The following screen shows the last page of the [Link] log file displayed in a
text editor. The log as displayed by the installation program may look slightly different.
Scroll through the log looking for highlighted messages. At the end of the file, you
should see the message: LI installation completed successfully.
While you may ignore any warnings that appear in the log, you should call IntelliCorp
Technical Support if there are syntax errors or any other types of errors reported.
If the installation fails and there are log messages indicating that an SAP TP import
failed, use transactions SE01 or SE09 to view the transport logs and have these logs
available when you call IntelliCorp Technical Support. The change request numbers for
the imports are found in the [Link] log file.
You may also wish to use transaction SM21 to view the SAP system log and verify that
no unusual errors or warnings were reported during the LiveInterface installation.
3
Installation and Configuration Guide 5 May, 2010
The LiveInterface installation is now complete. Please see the Post Installation
Procedures section on page 24 for information on several tasks that have to be
performed after the installation. These post installation tasks include setting up
LiveInterface security and authorizations, configuring LiveInterface workbench users,
installing workflow tasks, and reviewing print specifications.
If you plan to create Outbound interfaces, please see the online Help system for
information on the installation of outbound triggers. The LiveInterface online Help is
installed separately, see page 49 for details.
Once you have obtained a step password, you may re-run the installation program by
following the steps provided on page 17. When the installation screen is shown, enter
the step number provided by IntelliCorp Technical Support in the ‘Begin at step number’
field. Enter the step password in the ‘Install step password’ field.
Click ! or press F8 to run the installation program from the step indicated. Follow any
other instructions provided by IntelliCorp Technical Support.
2
Installation and Configuration Guide 5 May, 2010
Installation Details
This section provides more detailed information on the steps performed by the
LiveInterface installation program, /ICORP/ZUPINST1.
When you are performing an upgrade of LiveInterface, this step also deletes some
programs and objects that will be recreated by the installation.
When LiveInterface creates objects, it generates a unique reference number for each of
them. The code indicating the next available reference number for construction objects
is kept in table /ICORP/ZU046. As each LiveInterface object is created, the appropriate
value in this table is incremented by 1.
This step sets the starting value for the created objects. It also creates the number
range intervals for runtime components, the LiveInterface global control record, and all
client records.
3
Installation and Configuration Guide 5 May, 2010
LiveInterface runtime components use an SAP number range rather than a LiveInterface
table to obtain reference numbers. The required number range interval will be created
by the LiveInterface during step 6. Subsequent installations will not modify the existing
number range object or interval of the previous installation.
Be careful not to modify or delete the number range (ZUPI_ZU017) or the /ICORP/
ZU046 table contents for any reason, including client refresh, client copies, or manual
editing. If the range does not exist at runtime, all LiveInterface runtime components will
fail with a short dump due to exception UPI_NUMBER_GET_NEXT_ERROR.
Event Job
xxx_ZLI_Outbound_Driver xxx_ZLI_Outbound_Driver
xxx_ZLI_core_executor xxx_ZLI_Inbound
xxx_ZLI_CPIC_Sender_EVENT xxx_ZLI_CPIC_Sender
xxx_ZLI_MQS_SENDER_EVENT xxx_ZLI_MQS_SENDER
xxx_ZLI_Outbound_Executor xxx_ZLI_Outbound_Executor
no event xxx_ZLI_Alert_Monitor
no event xxx_ZLI_Background_Watcher
xxx_ZLI_RESTORE xxx_ZLI_RESTORE
2
Installation and Configuration Guide 5 May, 2010
Some SAP 700 kernel systems may have been patched to provide a different program
(named RSEVTHIST) for the Create Event transaction (transaction SM64, Background
Processing Events tab). In this case, the following screen is displayed during Step 8 to
allow the LiveInterface events to be created manually.
Click the Create toolbar button ! 6 times to create each of the LiveInterface events.
After the 6th click, the installation continues as normal.
3
Installation and Configuration Guide 5 May, 2010
Each of these tasks is explained in detail below. For information on setting up triggered
extracts, see the online Help system.
The LiveInterface installation process provides the necessary authorization objects for
the construction of authorizations and profiles. The installation also provides a set of
sample authorizations and profiles.
Note: To get up and running quickly on a development system, you can assign the
sample profile LI_**** to all users, allowing them to perform all possible tasks.
There are three constant layers and one conditional layer to LiveInterface authorization:
Activity
The kind of LiveInterface work the user is performing. Valid activities are:
• * (ALL)
• ACTIVATE
• GENERATE
• CREATE
• CHANGE
• REPROCESS
• DISPLAY
• DELETE
• TERMINATE (used only for LiveInterface Adapter for WebSphere MQ).
The hierarchical rules are detailed in the Activity Hierarchy section below.
2
Installation and Configuration Guide 5 May, 2010
Area
The type of LiveInterface module in which the user is working. Valid areas are:
• * (ALL)
• INBOUND
• RFCINBOUND
• BAPIINBOUND (for BAPI Shell)
• OUTBOUND, MQS (for WebSphere MQ integration only)
• MQSINBOUND (for WebSphere MQ integration only)
• REALTIME
Component
The portion of LiveInterface the user is currently using. Valid components are:
• * (ALL)
• CONSTRUCT
• CONTROL
• EXECUTION
• MONITORING
• UTILITIES
• MIGRATE
• CONVERT
CONTROL Sub-components
For the component CONTROL, a further subdivision is possible. Valid sub-components
are:
• * (ALL)
• GLOBAL
• CLIENT
• PPAIR
• INTERFACE
• INB_CNTL (for inbound associations)
• ALERTS
• EXT_CNTL (for outbound interfaces)
• TRAN_CNTL (for outbound transactions)
• FILEBLDR (for Unit of Work File Builder)
• TABLES (for table migration)
• E_LDB (for use with enhanced logical databases)
• BG_WATCHER (for the background watcher)
• IDOC_PROFL (for Inbound IDOC Partner Profiles)
• MQ_SERVER (for WebSphere MQ integration only)
• CONSOLE (for WebSphere MQ integration only)
3
Installation and Configuration Guide 5 May, 2010
UTILITIES Sub-component
For the component UTILITIES, a further subdivision is possible. Valid sub-components
are:
• * (ALL)
• WB_USERS,
• TRACE
A user is assigned one or more of these values in each of the four layers, and is then
automatically authorized to perform a certain kind of work in a given component,
subcomponent and module of LiveInterface.
Activity Hierarchy
In the hierarchy of LiveInterface activities and authorizations, permission to perform an
activity in a sequence automatically permits all subordinate activities. For example:
Select ‘LiveInterface Authorization Object’ to see which authorizations are available. You
can then create new authorizations. To create a profile that is a compilation of one or
more authorizations, execute SAP transaction SU02.
2
Installation and Configuration Guide 5 May, 2010
After you log on to LiveInterface for the first time using transaction /ICORP/ZLIVE, you
may receive the following error message when trying to use one of the components of
LiveInterface:
3
Installation and Configuration Guide 5 May, 2010
1. Enter the user name in the ‘User name’ field. You can select an existing user
name by clicking on the down arrow. A chooser screen listing the existing user
names is displayed.
3. Enter the user’s name in the field to the right of ‘User name’.
4. Enter a four character name starting with the letter Z or Y for the user’s Inbound
Syntax Checking Group. This function group is deleted and recreated every time
you perform a syntax check on an inbound interface. Each user must have a
uniquely named function group.
5. You may set the user’s default colors for the LiveInterface workbench in the
‘Workbench Branch Color’, ‘Header Label Line Color’, and ‘Branch Expand
Indicator Color’ fields. You can select each field and then click on the down
arrow to display a dialog box from which you can select default colors.
6. You can change the default graph type. Select the ‘Default Graph Type’ field and
click the down arrow to display a chooser screen from which you may select a
graph type.
7. Select a Mapping preference for the user. ‘Screen Based Mapping’ produces
screen images in SAP screen format during Inbound interface construction. ‘Text
Based Mapping’ displays screen fields in the form of a list.
8. Select a Statement Build preference for the user. If you select ‘Display Select
Statement Builder’, the user will receive LiveInterface prompts for the
requirements of select statements when inserting table reads into inbound screen
flow or outbound event flow.
2
Installation and Configuration Guide 5 May, 2010
9. Select a Function Module Build preference for the user. If you select ‘Display
Function Module Builder’, the system will provide prompts for the required
parameters of function modules when inserting function module calls into
inbound screen flow or outbound event flow.
10. Click ! . The system displays the Create Function Group dialog box to confirm
the creation of the Syntax Checking group that you entered in step 4.
If you plan to use a common directory for files to be used with the inbound driver, you
may wish to make use of the Operational Defaults option. You can set the default path
to a directory on your workstation, a network directory, or a directory on the SAP server.
3
Installation and Configuration Guide 5 May, 2010
2. Enter the directory path in the ‘Common Path’ field. The sequential files used
during the execution of the Inbound Batch Driver may all reside in the same file
system directory, or may share a common directory and sub-directory path.
When they do, the name of the portion of the path that is common to all the files
can be entered in this field. If the path is on your local workstation, select
‘Common Path is Local’.
3. Enter the remaining path and file name in the ‘Inbound Interface File’ field. If the
path is longer than the first field, enter the additional information in the second
field. LiveInterface automatically concatenates the two fields.
4. If the file is on a local device, such as your workstation hard drive, select ‘Input
File is Local’. If you have specified a logical file name, select ‘Logical File Name’
and enter the file name.
5. If the path to this file is made through the Common Path, select ‘Use Common
Path’. This is not applicable when using a Logical File Name.
6. Enter the remaining path and file name in the ‘Outbound Condition Code File’
field. If the path is longer than the first field, enter the additional information in
the second field. LiveInterface automatically concatenates the two fields.
8. If the path to this file is made through the Common Path, select ‘Use Common
Path’.
2
Installation and Configuration Guide 5 May, 2010
9. If you wish to have the Condition Code File appended to the existing file, select
‘Append Condition Code File’. Otherwise the existing file will be overwritten.
10. Enter the remaining path and file name in the ‘Outbound Feedback File’ field. If
the path is longer than the first field, enter the additional information in the
second field. LiveInterface automatically concatenates the two fields.
12. If the path to this file is made through the Common Path, select ‘Use Common
Path’.
13. If you wish to have the Feedback File appended to the existing file, select
‘Append Feedback File’. Otherwise the existing file will be overwritten. Then
click ! .
3
Installation and Configuration Guide 5 May, 2010
To perform the installation, carry out the following steps on each client:
1. Make sure all LiveInterface users are logged off the system. SAP users need not
log off.
2. Log on to the SAP database server under the SAP R/3 user ID identified on page
6, or as a user with the /ICORP/LI_AUTHS role assigned, and execute
transaction SE38 and execute transaction SE38. Type /ICORP/ZUWFINST in
the ‘Program’ field, and click the ‘Execute’ button. The following screen is
displayed:
Windows NT system?
If you are installing LiveInterface on a Windows NT system, the ‘Windows NT’ system
checkbox is selected automatically.
4. Click ! or press F8. Installation will take under 15 minutes. During this time,
the lines being written to the log file are shown in the status bar at the bottom of
the screen (this installation program appends to the [Link] log file
created when LiveInterface was installed). At the end of the installation, a screen
similar to the following will be displayed:
2
Installation and Configuration Guide 5 May, 2010
Scroll through the log looking for highlighted messages. At the end of the file, you
should see the message: Install workflow tasks completed successfully.
While you may ignore any warnings that appear in the log, you should call IntelliCorp
Technical Support if there are syntax errors or any other types of errors reported.
If the installation fails and there are log messages indicating that an SAP TP import
failed, use transactions SE01 or SE09 to view the transport logs and have these logs
available when you call IntelliCorp Technical Support. The change request numbers for
the imports are found in the [Link] log file.
You may also wish to use transaction SM21 to view the SAP system log and verify that
no unusual errors or warnings were reported during the LiveInterface installation.
3
Installation and Configuration Guide 5 May, 2010
2
Installation and Configuration Guide 5 May, 2010
The affected LiveInterface background jobs and ABAP/4 programs are as follows. In the
following table, replace ‘xxx’ with the client number where the job is installed.
2. All other (user defined) background jobs that run any of the LiveInterface ABAP/4
programs listed below. These adjustments can be done via transaction SM37.
Changes made via transaction SM37 take effect the next time that the job runs.
Jobs in progress are not affected.
3
Installation and Configuration Guide 5 May, 2010
Upgrade Procedures
If you are upgrading from an earlier version of LiveInterface, you must perform the
Upgrade Procedures described below after running the installation program.
Renaming Interfaces
For SAP 4.x compliance, LiveInterface does not allow some characters in program
names. Check the names of your extracts (outbound interfaces) to make sure that they
contain only alphanumeric characters, underscores, and/or forward slashes. All other
characters are disallowed in program names.
If your extract names contain any disallowed characters, you must rename the extracts
before regenerating them, no matter which version of SAP you are using. To rename an
extract, create a new extract with the desired name and use the ‘Reference ABAP’ field
on the Create New Outbound Interface screen to select the original extract. This will
create a new extract program that is a copy of the old one. You should then delete the
old interface from your system to prevent confusion.
Regenerating Interfaces
If you are upgrading from an earlier version of LiveInterface, you must regenerate all of
your existing interfaces in order for them to run properly under LiveInterface 12. For this
purpose, LiveInterface provides a mass generation program.
You cannot regenerate interfaces that are locked on a change request by another user,
however you can regenerate interfaces which you have locked. To avoid this problem,
all LiveInterface users should release their change requests before running the mass
generation program. If a change request is not released, the user will have to manually
regenerate that interface.
You must have a LiveInterface user configuration record and an SAP developer key,
which allows you to save and generate ABAPs and function modules. See page 27 for
instructions for setting up a LiveInterface user configuration record.
2
Installation and Configuration Guide 5 May, 2010
2. Complete the screen fields as follows. Note that at least one of the following two
checkboxes must be ticked:
Choose interfaces?
Tick this checkbox to display a list of active interfaces. You may select specific
interfaces to regenerate.
3
Installation and Configuration Guide 5 May, 2010
The results of each regeneration are displayed in the status bar at the bottom of the
screen. When regeneration is completed, a report is displayed.
The report displays the regenerated interfaces, listed by name, function group (inbound
only), regeneration status (successful, syntax error, correction error, correction
canceled), time of processing, number processed, number successfully regenerated,
and the number that did not regenerate successfully.
Regeneration does not produce a job log, so the generated report should be printed,
saved to a file, or saved to an SAP office folder for later review.
2
Installation and Configuration Guide 5 May, 2010
Conversion Procedures
If you are upgrading from an earlier release of LiveInterface, you must perform the
conversion procedures described below. These procedures should be performed after
LiveInterface has been installed.
Conversion Utility
The Conversion Utility upgrades data from your previous LiveInterface release for use
with LiveInterface. Before running the Conversion Utility, you will need to check the
following:
• Make sure you have purged all obsolete runtime data using the LiveInterface
Purge Utility.
• The user ID for which the Conversion Utility is run will need to have the SAP_ALL
and SAP_NEW authorization profiles.
Note: The Conversion Utility is not installed if the LiveInterface installation program does
not detect an earlier non-namespaced version of LiveInterface. In this case no
conversion is necessary.
2. Check that the ‘Work dir for conversion’ field refers to a valid working directory.
Set the ‘Begin at step number’ field to ‘1’, and leave the ‘This step only?’
checkbox unchecked.
3. Check the ‘[Step 4 only]’ checkbox to exclude LiveInterface snapshot and history
data from the conversion.
3
Installation and Configuration Guide 5 May, 2010
LiveInterface also reports on any non-UPI jobs that are still referencing nonnamespace
LiveInterface programs (i.e. ZUIBOUND, ZUPZPURG, ZUPZHTBU, etc.).
Event Job
xxx_ZUPI_Outbound_Driver xxx_ZUPI_Outbound_Driver
xxx_ZUPI_core_executor xxx_ZUPI_Inbound
xxx_ZUPI_CPIC_Sender_EVENT xxx_ZUPI_CPIC_Sender
xxx_ZUPI_MQS_SENDER_EVENT xxx_ZUPI_MQS_SENDER
xxx_ZUPI_Outbound_Executor xxx_ZUPI_Outbound_Executor
xxx_ZUPI_RESTORE xxx_ZUPI_Alert_Monitor
no event xxx_ZUPI_Background_Watcher
no event xxx_ZUPI_RESTORE
2
Installation and Configuration Guide 5 May, 2010
Step 5 checks to see whether any of the LiveInterface workflow tasks are being used. If
they are, the user will be instructed to run a conversion program for workflows named /
ICORP/WORKFLOW_CONVERSION.
3
Installation and Configuration Guide 5 May, 2010
Note: These procedures must be executed for each SAP client for which LiveInterface
Workflow Tasks are installed.
2. Copy the agents to new Workflow Tasks for the LiveInterface namespace
release.
Workflow tasks can only be deleted if no Work Items exist, and Work Items may only be
deleted if their status is COMPLETE.
If Work Items still exist for a Workflow task, the conversion cannot continue. The
LiveInterface utility /ICORP/ZDELETE_WORKITEMS can be used to remove the Work
Items.
2
Installation and Configuration Guide 5 May, 2010
Note: The Workflow Conversion Utility is not installed if the LiveInterface installation
program does not detect an earlier non-namespaced version of LiveInterface. In this
case no conversion is necessary.
2. Check that the ‘Work dir for conversion’ field refers to a valid working directory.
The Workflow Conversion log file [Link] will be written to this directory.
Set the ‘Begin at step number’ field to ‘1’, and leave the ‘This step only?’
checkbox unchecked.
This step checks whether Work Items exist for tasks in the non-namespace release.
Tasks cannot be deleted if Work Items exist for them. The LiveInterface Utility /ICORP/
ZDELETE_WORKITEMS can be used to delete the Work Item, as described below.
3
Installation and Configuration Guide 5 May, 2010
Note: The Delete Work Items Utility is not installed if the LiveInterface installation
program does not detect an earlier non-namespaced version of LiveInterface.
4. Select ‘Choose Work Items’ and ‘Change WI status to Complete’, then press !
to display the Work Items for the selected tasks.
5. A list of Work Items will be displayed for selection. Select ‘ALL Work Items’ and
press ‘Choose’: LiveInterface will change the status of the selected Work Items to
‘Complete’.
7. Deselect ‘Change WI Status to Complete’, select ‘Delete Work Item(s), and press
! .
8. A list of Work Items will be displayed for selection. Select ALL Work Items and
press ‘Choose’. LiveInterface will delete the selected Work Items and display a
summary screen.
2
Installation and Configuration Guide 5 May, 2010
• For UNIX servers, you must log on with the root user ID to copy the files and then
set the authorization mode of both the copied files and the directory to read,
write, execute for all users (chmod 777).
• For Windows servers, you must log on as <sid> adm. The directory to which
you copy the files must be in NTFS format, and the copied files must be
writeable.
• If you copy files from the distribution directory to your SAP server using FTP, be
sure to transfer the files in binary mode.
Use the STMS transaction to import the appropriate transport. Review the transport log
files for condition codes greater than 4. If any errors are found, please contact
IntelliCorp Technical Support using the details at the beginning of this manual.
Generating the Quick Copy Interfaces
3
Installation and Configuration Guide 5 May, 2010
2
Installation and Configuration Guide 5 May, 2010
4. Make sure that the 'Syntax Check Only?' checkbox is ticked. This option
performs a preliminary syntax check of the selected interfaces without generating
them.
3
Installation and Configuration Guide 5 May, 2010
!
2
Installation and Configuration Guide 5 May, 2010
6. Select the inbound interfaces you wish to generate. The descriptions for the
Quick Copy inbound interfaces begin with 'LI Library:'. Click 'Choose' to display
the following dialog:
7. Select the outbound interfaces you wish to generate. The descriptions for the
Quick Copy inbound interfaces begin with 'LI Library:'
Note: If you have selected an inbound interface for generation, be sure to select the
corresponding outbound interface.
3
Installation and Configuration Guide 5 May, 2010
8. Click 'Choose' to perform a syntax check for the selected interfaces. When the
syntax check has completed, a screen similar to the following will be displayed:
1. If the syntax check is successful, re-run the Mass Generation Utility with the
'Syntax Check Only?' checkbox unchecked. During the generation of the
inbound interfaces, the following dialog is displayed:
10. Click ! to create a new workbench request. The following dialog is displayed:
2
Installation and Configuration Guide 5 May, 2010
11. Enter a description for the request in the 'Short description' field, then click ! .
The 'Prompt for transportable Workbench request' dialog displays the request
number:
12. Click ! to continue. If you are prompted for a development class or package when
the outbound interface is generated, enter '/ICORP/ZIB'.
13. When the interfaces have been generated, the following screen is displayed:
3
Installation and Configuration Guide 5 May, 2010
2
Installation and Configuration Guide 5 May, 2010
2. Tick the checkbox next to each of the programs whose text elements you wish to
copy, then click 'Choose'. When the text elements have been copied, a summary
screen is displayed:
3
Installation and Configuration Guide 5 May, 2010
2
Installation and Configuration Guide 5 May, 2010
1. Contact IntelliCorp Technical Support and tell them you are installing
LiveInterface on a new client. Ask for the step password associated with Step 6
of the installation (see page 21 for a description of this step). You will need this
password in order to start the installation program at the client-specific part of the
LiveInterface installation.
2. Log on to the SAP R/3 client on which you want to install LiveInterface. Be sure
to use the same SAP user id that you used during the original installation of
LiveInterface.
3. Follow the regular installation instructions provided on page 17, but when the
installation screen illustrated below is shown, enter 6 in the ‘Begin at step
number’ field and the password provided by Technical Support in the ‘Install step
password’ field.
3
Installation and Configuration Guide 5 May, 2010
When the screen illustrated below is shown, select the client on which you want to install
LiveInterface. Leave the check boxes for previously installed clients unchecked.
4. Follow the rest of the installation steps as given. When these steps are
completed, LiveInterface will be installed on your new client.
5. If you wish to use LiveInterface for workflow alerts or notify users of changes to
LiveInterface control records via workflow, you must also run the Workflow Task
installation program on the client. See the Installing Workflow Tasks section on
page 32 for details.
2
Installation and Configuration Guide 5 May, 2010
Internationalization Utility
An Internationalization Utility is provided as part of the standard LiveInterface
installation. You should run this utility if LiveInterface users at your site log into SAP in a
language other than English. The utility copies LiveInterface text items from one SAP
language code to another so that users logged on in non-English languages can see all
LiveInterface text and messages. #
Important: In order to be able to audit the text update, run the program first in ‘Test
Mode’, generating a count of the text items that will be copied. You can later compare
this count to the count of items actually copied, to make sure that all text was
successfully copied.
4. To run in Test Mode, make sure the ‘Read & Count (only)’ radio button is
selected. Then change the value of the ‘Language to Copy TO in SAP’ field to
the language code of your SAP login language.
5. Execute the program in Test Mode. The program will produce a list showing the
number of items that will be copied to the target language. Save or print this list
for later comparison. Note that the list will be very long, so you may wish to save
it as a file rather than print it.
6. Now execute the program again in ‘Update’ mode. Leave all the values on the
selection screen the same, but select the ‘Read/Copy-Update New Language’
radio button and select your target language.
7. The program will copy all LiveInterface text items to the target language,
displaying its progress on the status bar. The program typically takes less than
15 minutes to run.
8. When the program is finished, it will produce a report displaying the number of
items copied. Compare the count in this report to the count in the report you
generated in test mode. If the counts do not match, contact IntelliCorp Technical
Support.
Note: After you have run the Internationalization Utility, you should use ONLY your target
language when you log into SAP to run LiveInterface.
2
Installation and Configuration Guide 5 May, 2010
To install the Help system under Windows system, run [Link] from the
LiveInterface\Help distribution directory. The following screens are displayed:
1. The Welcome screen. Check that you have no other applications running under
Windows, and choose Next > to continue with the installation.
2. The License Agreement screen. Read the license agreement, and if you agree
to its terms, click the I Agree button to continue with the installation.
3. The Select Destination Location screen. Use the Browse… button to select
an installation directory for the Online Help, then choose Next > to continue with
the installation.
4. The Select Start Menu Folder screen. Select the start menu folder to be used
for the program's shortcuts, or enter the name of a new start menu folder. Click
Next > to continue with the installation.
5. The Ready to Install screen. Check your settings, then click Install to begin the
installation.
6. The Installing screen. This screen indicates the progress of the installation.
Click the Show details button to display a detailed installation log.
7. The Completing Setup Wizard screen. This screen confirms that the
installation is complete. Click Finish to close the Setup Wizard.
To install the online Help on a under UNIX, install the files on a Windows system as
described above. Then copy or FTP the installed files from the Windows system to your
UNIX system, being sure to maintain the directory structure of the Help system.
If you have placed the files on a web server, follow whatever procedures are in place at
your site to make the directory accessible to the web server and to notify users of the
URL. The starting page for the Help system is [Link].
Note: Because the Help system is not currently accessible through the LiveInterface
menu, you must be sure to notify LiveInterface users of the location or URL of the files
you have installed and the procedure for starting the Help system.
3
Installation and Configuration Guide 5 May, 2010
If you have installed the Help system on a web server, use a browser to access the URL
assigned to the [Link] page on the server. In order to access the Table
of Contents, Index, and Search features of the Help system, Java must be enabled in
your browser.
2
Installation and Configuration Guide 5 May, 2010
De-Installing LiveInterface
De-Installing LiveInterface involves the following steps:
Important Note: If you are upgrading to LiveInterface 12, the earlier release of
LiveInterface should not be removed until LiveInterface 12 has been installed and the
tasks in the Upgrade Procedures section on page 36 have been performed.
• For UNIX servers, you must log on with the root user ID to copy the files and then
set the authorization mode of both the copied files and the directory to read,
write, execute for all users (chmod 777).
• For Windows servers, you must log on as <sid> adm. The directory to which
you copy the files must be in NTFS format, and the copied files must be
writeable.
• If you copy files from the distribution directory to your SAP server using FTP, be
sure to transfer the files in binary mode.
Use the STMS transaction to import the appropriate transport. Review the transport log
files for condition codes greater than 4. If any errors are found, please contact
IntelliCorp Technical Support using the details at the beginning of this manual.
3
Installation and Configuration Guide 5 May, 2010
To de-install the online Help from a UNIX system or web server, delete the directory to
which the help files were copied, and if necessary, remove the IIS virtual directory which
points to the help files.