Académique Documents
Professionnel Documents
Culture Documents
4/28/2015
SAP Line Opener
Table of Contents
SAP Line Opener ...................................................................................................................................... 3
Installation ........................................................................................................................................... 3
Distributable .................................................................................................................................... 3
Java .................................................................................................................................................. 3
SAP Java Connector ......................................................................................................................... 3
Administration ..................................................................................................................................... 4
Registrator ....................................................................................................................................... 4
Opener ............................................................................................................................................. 5
Running as service ............................................................................................................................... 7
Command Mode .............................................................................................................................. 7
Service hooks ................................................................................................................................... 7
Windows Service ............................................................................................................................. 7
Troubleshooting .................................................................................................................................. 9
Registrator ....................................................................................................................................... 9
Opener ............................................................................................................................................. 9
Saplopsrv ......................................................................................................................................... 9
2
SAP Line Opener
Installation
In addition to its distributable, SAP Line Opener requires a Java Runtime Environment and the SAP
Java Connector to run. The latter have to be installed separately in accordance to the underlying
platform.
Distributable
The SAP Line Opener distributable just needs to be unpacked into its own directory, it doesnt require
any installation.
Java
SAP Line Opener was developed for Java Runtime Environment Version 6. It can be run with any JRE
of same or higher version.
Download
The latest Java Runtime Environment can be obtained from www.java.com.
Configuration
Launching SAP Line Opener requires some Java components to be readily available.
- Java.exe to directly launch the Registrator or Opener from within the SAP Line Opener
directory.
- Jvm.dll to launch the Opener from within the Windows service installed by saplopsrv.exe.
These files are located within the directory structure of your Java JRE installation. Do not copy them
to the SAP Line Opener directory, make them globally available instead, e.g. by adding their directory
to the PATH Environment Variable within your Windows System Properties.
Download
Installation files can be obtained from service.sap.com/connectors, section SAP Java Connector.
Installation
Installation instructions can be found at
help.sap.com/saphelp_nwpi711/helpdata/en/48/707c54872c1b5ae10000000a42189c/content.htm.
The mandatory files as stated on the installation page do not have to reside within their own
directory. To avoid version conflicts it is possible to copy them directly into the SAP Line Opener
directory.
3
SAP Line Opener
Administration
SAP Line Opener consists of two components, the Registrator and the Opener.
Registrator
The Registrator is used to configure access to SAP Service Maketplace and to request Semi Automatic
Opening registration. To run the application, launch it as Java jar file.
Input is saved within file lop.cfg and automatically loaded on any subsequent launch. This file is
also read by the Opener as part in order to process pending line opening requests. Operation results
are logged within file registrator.log.
Backend
This section controls authentication against SAP Service Marketplace.
Backend information may be updated any time as required. Both user and password must be
specified.
Connection
This section controls establishing a connection to the SAP Service Marketplace.
4
SAP Line Opener
Connection information may be updated any time as required. When connecting through a proxy a
host must be specified.
Registration
This section controls line registration within SAP Service Marketplace.
Line information is bound to successful registration, it may not be changed once registration has
completed. Both location and description are required for registration.
Opener
The Opener is used to process pending line opening requests and to list configured routers. To run
the application, launch it as Java jar file.
By default, the Opener displays the graphical user interface. It is also possible to launch it without
any frontend in non-interaction mode, processing line opening requests right away.
The Opener operates on the information stored within file lop.cfg as part of registering a line with
SAP Service Marketplace. Operation results are logged within file opener.log.
5
SAP Line Opener
This is a continuous operation that will proceed until stopped. It may get scheduled as a service.
This is a one-shot operation that stops once the list has been retrieved and displayed.
6
SAP Line Opener
Running as service
The Opener is expected to run for extended periods of time. Since it is inconvenient to keep a
frontend UI open all the time the Opener offers ways to run as a service.
Command Mode
The Opener can be launched to directly start processing line opening requests, no further interaction
required.
This starts a single process that automatically terminates whenever the Opener would enter the
stopped state, e.g. due to the backend rejecting further communication. There is no graphical user
interface involved, so it can be run on platforms like Linux without X11 support.
Service hooks
The Opener provides four public static methods within class
com.sap.support.connectivity.lop.Opener to allow direct execution control, bypassing the frontend.
Start
public static synchronized void start()
Creates the Opener as static singleton and starts processing line opening requests, similar to
selecting Process line opening requests within the dropdown list and pressing the Start button.
Stop
public static synchronized void stop()
Pause
public static synchronized void pause()
Pauses processing within the Opener, similar to pressing the Stop button.
Resume
public static synchronized void resume()
Resumes processing within the Opener, similar to pressing the Start button.
Windows Service
The SAP Line Opener distributable contains an executable to directly install and run the Opener as
Windows Service SAP Line Opener. Service controls for Start, Stop, Pause and Resume are
directly connected to the Opener service hooks. Operation results are logged within file
saplopsrv.log.
7
SAP Line Opener
The executable is available in two flavors, saplopsrv_win32.exe for 32bit environments and
saplopsrv_x64.exe for 64bit environments. It has to be launched as administrator from the same
directory as the Opener and expects a single argument to specify the desired operation.
Install
saplopsrv.exe install
Installs service SAP Line Opener with default configuration. Please note that further manual
configuration may be required, e.g. to set startup type and account information.
Uninstall
saplopsrv.exe uninstall
8
SAP Line Opener
Troubleshooting
Whatever can go wrong will go wrong. Murphys Law
Registrator
Registrator fails to launch, command java jar registrator.jar is not recognized.
Registrator unable to register, displays popup Registration failed, unable to reach backend.
Unable to access SAP Service Marketplace, please make sure that your network allows access to URL
https://websmpbsp.sap-ag.de.
Opener
Opener fails to launch, command java jar opener.jar terminates with stack trace containing
entry java.lang.UnsupportedClassVersionError: com/sap/support/connectivity/lop/Opener.
Opener fails to launch, command java jar opener.jar terminates with stack trace containing
entry java.lang.NoClassDefFoundError: com/sap/conn/jco/Ext/DestinationDataProvider.
Outdated or missing JCO installation, please download the latest JCO distribution and unpack it into
your LOP directory.
Opener attempts to request next work package, fails with entry Failed to retrieve next work
package.
Unable to access SAP Service Marketplace, please make sure that your network allows access to URL
https://websmpbsp.sap-ag.de.
Opener successfully requests next work package, fails with entry Ping failed, unable to reach
target system.
Incorrect route information, please make sure that your configured router allows SAPgui connections
to OSS.
Opener successfully requests next work package, fails with entry Ping failed, logon rejected.
Incorrect logon information, please make sure that backend user/password have been specified
correctly within the Registrator. Repeated incorrect login attempts may cause your account to get
locked temporarily, please try to access OSS to see if this might be the case.
Saplopsrv
Service fails to start, log file contains entry SaplopsrvMachineCreate: Failed to load java runtime
library: 193.
Incompatible environment, please make sure to use Java, JCO and Saplopsrv either exclusively for
32bit environments or exclusively for 64bit environments.
9
SAP Line Opener
Service fails to start, log file contains entry SaplopsrvMachineCreate: Failed to load java runtime
library: 126.
Dynamic Link Library jvm.dll not found, please make sure to include it in your path system
environment variable.
10