GATEWAY WORK PROCESS

Gateway Process is Monitored in SMGW. It listens on Port 3300.Secured gateway listens on port 4800. Gateway Connection details are used while defining RFC Connections in SM59. Gateway host(Name of the Application Server) Gateway Service(sapgw00). Note: Generally No issues occur with SAP Gateway Service Except max Connections reached(SM21/ST22). Gateway parameters:
gw/max_conn=500(Maximum Number of active Connection which increased up to 4092)
gw/keepalive=300(Timer for check unused connections and disconnect)
gw/timeout=10000ms(Timeout for connecting to other gateways)
Gateway Proces is monitored in SMGW–>Menu–>Go to–>logged on Clients
it displays the currently connected clients.
By Default, a Gateway Connection for Application Server and IGS(Internet Graphics Server) are established. IGS Server is installed by default to provide the Graphics Services. Installation of Additional Gateway Servers:
Use SAP Installation Master Software/SWPM
Select Gateway Installation
Provide SID, Master Password, Instance Number
Provide the kernel Software
Review the Inputs and Install the Gateway.
Standalone Gateway is monitored in SMGW. login gateway as administrator, as standard interface GUI is not available use gateway Monitor at OS level.
#su – gwsadm
$cdpro to navigate to the profiles directory.
$gwmon pf=<instance Profile>GWS_G03_HostName NetWeaver Gateway:
It is not the gateway that is discussed in Application Server Context.
In Simple Words, Netweaver Gateway is a set of ABAP add-ons(applied through Tcode SAINT) to your existing SAP ERP system that provides easy access to your business information which provides a simple way to connect devices, environments, and platforms to SAP software based on market standards. The framework enables development of innovative people-centric solutions bringing the power of SAP business software into new experiences such as social and collaboration environments, mobile and tablet devices and rich internet applications.
Currently Fiori(UX User Experience) based Applications uses the Netweaver Gateway.

Comments

Post a Comment

Popular posts from this blog

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more