Configuring relay server in Sybase Control Center Applies to: SUP 2.1.x SUP 2.2.x SUP 2.3.x Summary Relay servers can be used to connect to SUP server through internet and this would be one of the best and the suggested methods to connect to SUP. In order to do this, we will have to configure the relay server details in the SUP server and I shall tell you how to achieve that in the course of this document. Author: SHARVARI Company: SAP LABS INDIA PVT LTD Created on: 9 November 2013 Author Bio Sharvari sharvari@sap.com Quality Associate, Engineering Services, SUP-ODP SAP Labs India PVT Ltd 2013 SAP AG 1
Pre-requisites: Note: 1. You should know the relay server host name 2. Relay server URL template 3. You should have configured a farm id which will be associated with the relay server 4. Node id against which the farm is available 5. Token value which is associated with the farm generated. In the document, I shall take the example of relay server with host: relaymp.sap-ag.de Configuring SCC: 1. Click on localhost@localhost (running) tab on the left pane. 2. Following this we can see a tab called Relay Servers This is where we will add the relay server details 2013 SAP AG 2
1. Click on new 2. Add the relayserver host 3. Port values have to be keyed in- you should know the http and https port of the relay server 4. Add the relayserver URL suffix 5. Click Next 2013 SAP AG 3
Now that the relay server host and port details are provided, we will have to connect a farm id to this Relay server. 1. Next to the label Farm ID, add the farm details that you already have 2. Under the drop down Type select Messaging 3. Click on add 4. This adds the values in the table. Select the entry by clicking on it 5. Now, you can add Server Node ID and token details in the respective text fields 6. Click on add 7. Displays the corresponding values in the table below it 8. Click on next 9. Verify values and say finish 2013 SAP AG 4
We shall move to the next level of configuration: 1. Expand localhost@localhost(running) 2. Expand Servers 3. Click on the running server node. 4. On the right pane, you can see outbound enabler 5. Click on it to and say new 6. This will provide you with a screen as in the screen shot below 7. By default replication type would be selected. 1. On changing the type to messaging, you can see the details get automatically updated With the relay server details that we had previously entered. 2. If you want to have the connectivity between the device and the SUP server to be HTTP channel, select the http port. If not, select the Https port in the radio button provided against relay server port 3. Click on next 4. Say Finish 2013 SAP AG 5
1. This will add the relay server as below 2. But, it would be in the stopped state 3. Select the checkbox against the relayserver 4. Click on start button provided just above the list displayed 5. Status of the relay server should show Running Now, the relay server is ready to be used! 2013 SAP AG 6
Note: In case the relay server moves to an error state, you can select the relay server checkbox and then Click on Retrieve Log. Set a higher verbosity level of 5 and save the logs. This would help us in knowing why the configured relay server failed to start. 2013 SAP AG 7
Copyright Copyright 2013 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Oracle Corporation. JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2013 SAP AG 8