How to deploy SAP Print Server Highly Available Architecture on Azure

Posted on by — No Comments ↓

This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .

Overview

SAPSprint serves as one of the vital print output transfer programs designed for Microsoft Windows operating systems. Acting as a successor to SAPlpd, SAPSprint functions as an implementation of a print server, specifically essential for remote printing within Microsoft Windows environments. Seamlessly integrating with ECC, SAPSprint facilitates this integration by incorporating host printer details, configuring them as corresponding SAPSprint servers within the respective printer configurations.

 

For organizations prioritizing reliability, achieving High Availability (HA) in SAP print servers is paramount. One of the ways it can be accomplished by installing the SAPSprint service on another node within the primary site, operating in an active-active mode.

This blog intends to serves as a valuable reference for deploying an HA environment for SAP Print Servers on Microsoft Azure, ensuring uninterrupted printing operations and improving overall system resilience.

 

Software Requirements 

The following Software versions are being used for this blog,

Operating System: Windows Server 2016

SAP PDF print: version 730 SP 04

SAP Print Service: SP760 SP 06

 

Architectural Design

Figure 1 -  High Level Design-Architecture of SAP print server application.Figure 1 -  High Level Design-Architecture of SAP print server application.

 

HA Strategy of SAP Print Server Application

  • High Availability has been ensured for the Print server within the primary zone, effectively removing any single points of failure.

  • Node2 of the Print server has been deployed with an identical configuration to Node1.

  • An Azure standard load balancer has been established over both Print Server Node1 and Node2 to evenly distribute the workload, maintaining an active-active state for both nodes.

 

Azure Load balancer Configuration

Added Newly Build Node in azure LB backend pool to avoid the single point failure in zonal level.

jitendrasingh_0-1710099044428.png

 

SAP Sprint Installation Steps

SAPPDFPrint Installation:

  • Navigate to software location in corresponding windows application server:

jitendrasingh_0-1710099147232.png

  • Right click on the executable file and run as administrator.

jitendrasingh_1-1710099182689.png

  • Make sure all SAP application in the respective server are closed before proceeding with the installation:

jitendrasingh_2-1710099213659.png

 

  • Validate the disk space usage

jitendrasingh_3-1710099247049.png

 

  • Validate the installation path:

jitendrasingh_4-1710099266636.png

  • Installation completed successfully:

jitendrasingh_0-1710099346905.png

  • Verify whether the SAP PDF print software is now available under list of installed programs:

jitendrasingh_1-1710099368427.png

 

SAPSprint installation:

  • Navigate to software location in corresponding windows application server:

jitendrasingh_3-1710099468369.png

  • Right click on the executable file and run as administrator.

jitendrasingh_4-1710099489216.png

  • Make sure all SAP application in the respective server are closed before proceeding with the installation:

jitendrasingh_5-1710099516220.png

  • Verify whether the memory to be allocated is available in the server:

jitendrasingh_6-1710099541218.png

  • Validate the installation directory: 

jitendrasingh_7-1710099572272.png

  • Specify the SAP Print Service port as- 515:

  jitendrasingh_8-1710099593065.png

  • Installation completed successfully:

 jitendrasingh_9-1710099614903.png

  • Verify whether the SAP Print Service software is now available under list of installed programs:

jitendrasingh_10-1710099640442.png

jitendrasingh_11-1710099666550.png

 

Post Installation Configuration Steps

Step 1: Login to existing print server node

Go to windows, select SAPSprint and click on “Print Options Editor.” A new window for print option editor will open in read only mode.

jitendrasingh_12-1710099691498.png

 Step 2: Take the screenshot of each tab to compare the settings with newly added server:

Trace Options:

jitendrasingh_13-1710099726886.png

Restart Options:

jitendrasingh_14-1710099746251.png

SAPSprint Processing:

jitendrasingh_15-1710099764983.png

SAPWIN Processing:

jitendrasingh_16-1710099780116.png

PDF Options:

jitendrasingh_17-1710099800015.png

Ni Options:

jitendrasingh_18-1710099815717.png

SNC Options:

jitendrasingh_19-1710099833997.png

Others:

jitendrasingh_20-1710099850681.png

Printer Tray Selection:

jitendrasingh_21-1710099868080.png

Administration:

jitendrasingh_22-1710099877373.png

Step 3: Login to new VM(node 2), go to windows, select SAPSprint and right click on “Print Options Editor” to select “Run as Y

administrator.” Print Options Editor should get open in edit mode.

Step 4: Compare the settings of each tab in “Print Options Editor” with node 1 settings to keep it in sync.

Step 5: Once changes are done, click on “Apply” & post that click on “OK”. Close the editor.

Step 6: Login to new VM (node 2), go to windows, select SAPSprint and click on “Print Options Editor” & validate if all changes are saved.

 

Integration with ECC

 

Step 1: Navigate to spad in corresponding ECC system

Step 2: Select the output device for which print server details need to be updated.

Step 3: Click on “Access method” & in “Destination Host” tab , mention the print server ILB name instead of individual physical host

jitendrasingh_0-1710099932083.png

 

Testing Validation

 

#

Test Case

Expected Outcome

1

Configure the 1st print server and test

Test print from print server 1 should be running

2

Configure the 2nd print server and test

Test print from print server 2 should be running

3

Enable the Load balancer and test

Test print should work from both print servers

4

Stop Print Service in Node 1 

Test print should continue running

5

Stop Print Service in Node 2 

Test print should continue running

6

Stop Print Server VM in node 1 

Test print should continue running

7

Stop Print Server VM in node 2 

Test print should continue running

8

Trigger a print and in the print server, pause corresponding print queue in node 1

Test print will go to error first and when same spool request is retriggered, it will be successful through node 2

9

Trigger a print and in the print server, pause corresponding print queue in node 2

Test print will go to error first and when same spool request is retriggered, it will be successful through node 1

 

Observations & Troubleshooting

After introducing the New Node in HA configuration, we identified the issues reported by customers.

1)  Print requests are not reaching printers.

Resolution:

Whitelisted New server I address in Client firewall to allow the traffic from print server to Printers

 

2) Print requests are processed in print queues whereas physical prints are not received at printer.

Resolution:

We have highlighted the above observation to SAP and SAP has recommended to select the “Display SAP user as job owner” option under “SAPPrint Processing” tab of Print option editor.

jitendrasingh_1-1710099975592.png

 

 

 

Summary

The blog describes the high availability (HA) architecture of SAP Print Server on Azure environment, using SAPSprint service and Azure load balancer. The blog also provides the software requirements considered for test, the installation and configuration steps, the testing and validation scenarios, and the issues and troubleshooting tips for the SAP Print Server HA.

 

 Reference

What is Azure Load Balancer? - Azure Load Balancer | Microsoft Learn

About Azure Site Recovery - Azure Site Recovery | Microsoft Learn

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.