3. Copy the category file otx.sap.rm.SystemArchiveLink.v to a different location within the Enterprise Workspace. If required, you can change the category name.
Caution
Do not delete the original category file under Open the Enterprise Library Types Volumes.
4. Repeat the above procedure with the category file otx.sap.rm.SystemPrintList.v in the otx.sap.rm.SystemPrintList folder.
Note: Note the location of the copied system category files
otx.sap.rm.SystemArchiveLink.v and otx.sap.rm.SystemPrintList.v. You will need this information to configure new declarations with the SPRO transaction in SAP.
5.9 Installing Open Text Advanced Item Management (optional)
If you require MIME-type-specific metadata during creation, and if disposition export to the format specified by the US DoD, then you have to download (from the Knowledge Center) and install the Open Text Advanced Item Management
component.
5.10 Installing RMLink RFC Service on RCS Server (SAP R/3 Enterprise 4.70 only)
SAP R/3 Enterprise 4.70 does not support web services. Therefore, the RMLink RFC Service enables RMLink on SAP R/3 Enterprise 4.70 to communicate with the Enterprise Library Services via RFC. The RMLink RFC Service has to be installed on the Enterprise Library Services installation.
5.10.1 Installing SAP Java Connector module
Prior to installing the RMLink RFC Service, you must install the SAP Java Connector (JCo) version 2.1.8 on the RCS server.
JCo is a toolkit that allows the RMLink RFC Service to communicate with any SAP system.
To install the Java Connector module on Windows:
1. Make sure that the DLL files librfc32.dll and sapjcorfc.dll can be found by Windows (for example by copying them into the <Windows
installation>\System32 folder).
2. Copy the sapjco.jar file to the <Tomcat installation>\common\lib folder (or a similar path for NetWeaver).
During startup, the application server loads all libraries in this path and makes them available to its applications, including the RCS server. Therefore, the RMLink RFC Service, running under the RCS Server, will be able to access JCo and use it to establish a communication with SAP servers.
3. Restart the application server.
To install the Java Connector Module on UNIX:
1. Make sure that the library files librfccm.so and libsapjcorfc.so can be found by the operating system.
2. Make sure that the library files librfccm.so and libsapjcorfc.so can be found by the application server (for example by copying them to the
$LD_LIBRARY_PATH path for the Tomcat application server).
3. Copy the sapjco.jar file to the <Tomcat installation>/common/lib directory (or a similar path for NetWeaver).
4. Restart the application server.
5.10.2 Installing RMLink RFC Service
To install the RMLink RFC Service, execute the setup file (RMLink RFC Service-9.-7.1.msi for Windows, setup.sh for UNIX ) provided on your installation CD on the RCS server. The RCS server must to be running during the installation; once the installation is finished, restart the RCS server server.
After the installation, verify the RMLink RFC Service is installed. In the Open Text
5.10 Installing RMLink RFC Service on RCS Server (SAP R/3 Enterprise 4.70 only)
Note: Make sure that your RCS server has a sufficient initial memory pool.
Refer to the Section 3.1.1.3 "Configuring Tomcat pool size" in Open Text Runtime and Core Services - Installation Guide (ELCS-IGD) for memory pool size recommendations (available in the Knowledge Center under:
https://knowledge.opentext.com/knowledge/llisapi.dll/open/13609768).
5.10.3 Configuring RMLink RFC Service
The RMLink RFC Service is configured in the Open Text Administration.
Note: The initial configuration supports a single SAP server (parameter rmlink.maxservers = 1). If you plan to use the RMLink RFC Service with multiple SAP servers, you must set the value of rmlink.maxservers to the number of SAP servers and copy the complete server-specific set of parameters (rmlink.server1.<xxx>) so that each additional SAP server gets its own set of parameters (rmlink.server2…, rmlink.server3…, etc.).
To configure the RMLink RFC Service
1. In the Open Text Administration, navigate toRuntime and Core Service | Configuration | RMLink RFC Service.
You see a list of all possible configuration parameters. Some parameters already
The following table explains each configuration parameter.
Name Type Description Default
Value rmlink.maxservers Numeric Number of SAP servers that
com-municate with the RFC Service
1
rmlink.sapusername.
convert2lowercase
Enumera-tion Upon function calls, the RFC Service will either lowercase or uppercase the user in the SAP token for subse-quent authentication of this user with the CAP service. The value (true or false) depends on whether the Livelink users are defined in lower or upper cases.
false
rmlink.server1.applic
ationname String SAP server system ID (example:
DP1)
rmlink.server1.client String SAP server client number 800 rmlink.server1.hostn
ame String SAP server host name
rmlink.server1.poolsi ze
Numeric Thread pool size for this SAP server 5
rmlink.server1.progr amid
String Name of the registered RFC Server Program ID within SAP RFC Desti-nation configuration (SM59 transac-tion)
RMLinkR FCSer-vice
rmlink.server1.rfctrac
e Boolean Enable or disable the RFC trace (*.trc files log the entire RFC data communication)
false
rmlink.server1.sapgw host
String SAP gateway host name for this server
rmlink.server1.sapgw
service String SAP gateway service for this server (example: sapgw01)
rmlink.server1.sapus
ername String SAP user name to register the RFC Service in the gateway; the user must
5.10 Installing RMLink RFC Service on RCS Server (SAP R/3 Enterprise 4.70 only)
Name Type Description Default
Value rmlink.server1.snclib
rary String Path to the SNC library rmlink.server1.syste
mnumber String SAP server system number (example:
00) rmlink.server1.unico
de
Boolean SAP server Unicode support true
5.10.4 Troubleshooting RMLink RFC Service
The RMLink RFC Service features three log levels: ERROR, DEBUG, and TRACE with ERROR being the default. The RMLink RFC Service writes its logs in the rcs.log file located in the logging directory of your application server (e.g. <Tomcat installation>\logs).
To change the default log level:
1. In the Open Text Administration, navigate toRuntime and Core Service | Configuration | Logging.
2. Double-click the logger.RMLinkRFCService.loglevel entry or select it and click Properties in the right Actions pane. Select the required log level.
An additional source of troubleshooting information is the RFC trace. To enable the RFC trace, set the rmlink.server1.rfctrace configuration parameter to true and restart the RFC Service. As a result, SAP JCo will begin to log the complete RFC data
Chapter 6
Performing post-installation tasks in SAP
Before using the RMLink functions, the following post-installation and customizing tasks in SAP are required:
• Defining SAP roles
• Using the IMG function
• Setting up SAP authentication
• Creating HTTP connection and logical port for Enterprise Library Services
• Creating HTTP connection and logical port for CAP services
• Creating logical port for Web service proxy class
• Maintaining Enterprise Library server settings
• Scheduling job removing deleted records
• Activating GOS enhancements
The following additional post-installation and customizing tasks in SAP are optional:
• Maintaining receiver module /OTX/RM_UPD_RECORD_VIA_EVENT for changed events and receiver module /OTX/RM_CRT_RECORD_PRINTLIST for created events
• Creating additional Livelink categories
• Implementing business property provider