cancel
Showing results for 
Search instead for 
Did you mean: 

Seperating modules

Former Member
0 Kudos

Hi all,

The idea is still vague here but we are considering moving SD and WM to a seperate server. Currently we have all modules of r3 on one server, that includes the app and DB. And we are seeing performance problems at some point of the day where there are too many jobs coming from too many modules.

What would be the best to so.?

Thanks in advance.

Samer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Samer,

I recommend that you should think about this issue by load balancing method not at the module level. You should create two different logon groups for each module under SMLG and assign newly created groups to your module users. For example, for WM module, you can create a "LB_WM" logon group then assign 1 application server to them and 1 for "LB_SD" logon group. At the end of the process, assign load balancing groups to your users. By doing so you will be able to split-up module users into two different server.

Best regards,

Former Member
0 Kudos

Hi Orkun,

Great way to approach the idea and this might be the way to try to solve our problem. But let me try to get more explanation.

I'm not too familiar with SMLG but I've just done some reading, is this what you're getting to: http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a64c1505211d189550000e829fbbd/frameset.htm

You mentioned at the end that after we create the "login groups"we will "split-up module users into two different servers". So you mean After creating the two groups, "LB_WM and "LB_SD", we will still giving each one of them to an individual physical application server or do you mean create another instance and create the groups accordingly? We currently have one instance for all..

Input will be appreciated,

Samer

Edited by: Samer Kamal on Apr 18, 2008 2:33 AM

Former Member
0 Kudos

Hi,

if you have only single application instance ( i.e central instance ) you can not achieve logon load balance

you need to install one more application server ( i.e dialog instance )

and configure the logon group according to following sap note

Note 26317 - Set up for LOGON group for autom. load balancing

regards,

kaushal

Former Member
0 Kudos

Hi Samer,

I though that you've two or more instances in your SAP system. My suggestion is that if you have high load on your existing server, you should buy a new application server and attach it into your existing system. By doing so you will be able to distribute module users into different machines. Of course that requires IT investment. I hope that it is clear and fullfil with your expectations.

Best regards,

Former Member
0 Kudos

Hi kaushal/Orkun,

So do you guys think installing a new dialog instance and perform load balance on both won't help with performance? It has to be a new physical application server..?

Former Member
0 Kudos

Hi,

if you face performance problem then i suggest to install new application server and perform the load balancing according to sap note which i suggested

so user are distributed among the application server.

regards,

kaushal

Former Member
0 Kudos

sometimes i get confused between an "instanc"e and an "application server" and to be precise, do you mean installing a new physical application server? And then install the dialog instance on it, attach it to the first physical application server and the central instance? And then distribute the module users like the note is suggesting?

Former Member
0 Kudos

Hi,


sometimes i get confused between an "instanc"e and an "application server" and to be precise, do you mean installing a new physical application server? And then install the dialog instance on it

you have central system installation means Central instance and Database instance are running on single windows server.

install the dialog instance ( which is also called application server) on one new windows server for your existing SAP system.

Central instance have message server , Disp + work , and Enqueue process ( all WP i.e work process)

while Dialog instance have only DISP + WORK ( all WP except ENQ)

when you finish the installation of Dialog instance for you SAP System user can logon from both instance i.e

Central instance and Dialog instance

you need to perform the load balancing using sap note which i suggested.

in short you need to install a dialog instance on new windows physical server for your existing SAP system.

regards,

kaushal

Former Member
0 Kudos

thanks for the great explanation..

So from this I get it that there's no need to move any of the modules that have high loading time.. Correct?

To try to overcome buying new hardware, do you think we can put a production dialog instance on a virtual now..?

Former Member
0 Kudos

Hi,

sorry i didn't get you


do you think we can put a production dialog instance on a virtual now

what do you mean by putting a production dialog instance on a virtual .. ?

regards,

kaushal

Former Member
0 Kudos

Sorry not to make it clear..

I mean can I install the dialog instance on a virtual windows O/S (VMWARE since it's certified for production from SAP now) instead of new physical hard drive..?

Former Member
0 Kudos

Hi,

Dialog instance does not take more HDD space. ( 4 GB HDD is enough)

you want to install dialog instance on virtual windows which is separate server or you want to install virtual windows server on same production server host

if yes then don't do that. you can still facing performance issue.

use separate windows server host for dialog instance

regards,

kaushal

Former Member
0 Kudos

I'll be installing virtual windows on another physical server so we won't face the performance issue

Back to my previous question. There's no need to move any of the modules that have high loading time.. Correct?

markus_doehr2
Active Contributor
0 Kudos

There is no need - and no possibility to do so easily.

SAP is an integrated system and can't be separated easily. It's technically possible to do that, but this would imply

- buying an SLO service (http://service.sap.com/slo)

- configuring an IDOC/ALE scenario so you can keep both systems in sync

- installing a new ERP system and configure appropriately

Markus

Former Member
0 Kudos

gotcha.. That's what i thought.

Okay thank you all very the helpful answers. I'll post more if i have any more question as we go forward and determine our plan..

Answers (0)