cancel
Showing results for 
Search instead for 
Did you mean: 

Right Way to change MBOs Connections

Former Member
0 Kudos

Hellow Experts,

I'm really enjoying the communication here, and I got a new one.

Whats the right way of change MBOs Connections to SAP for instance?

I tried 2 methods.

Method One

Title: Its just too much Work

Proceeding:

I start rebinding every MBO and  operatios to the new Connection.

Drawback:

If i have 1 MBO it may takes 30 seconds if they are 40 or 50 mbos it will take a lot of time.

there are the output tables from bapis are recreated if dont they are deleted.

so you have to reimplement all the operations one again. and it as the adicional

problem that we all can miss something and do something wrong.

Method Two


Title: Simpler way


Proceeding:

change the connection profile itself at workspace from DEV->QA or QA->PRD

Drawback:

supposing that you want independence between the apps connections  like app1 is on DEV and ap 2 is on PRD.

this will led to N connections per N applications.

DEV: (Development)

QA: (Quality)

PRD: (Production)

I would like to know if you guys have more approaches and what you think of this ones.

Cheers,

Laguerta

Accepted Solutions (1)

Accepted Solutions (1)

midhun_vp
Active Contributor
0 Kudos

The easy way to do it is keeping multiple workspaces for different servers, but keeping single connection profile with different configuration details.

ie. You will be having 3 workspaces for Dev, Q and P. With same names for SAP connection profile (ex.SAPConnection for Dev, Q and P) , but the properties of connection profiles changes,ex. Profile "SAPConnection " in Dev workspace has dev SAP details, profile "SAPConnection " in Q workspace has Q SAP server details and profile "SAPConnection " in P workspace has P SAP server details. Hence the MBOs will not through error and no need to change anything after moving the MBO project to different workspaces.

Midhun VP

Former Member
0 Kudos

Hellow Midhun!

This is the improvement I wanted to my second Method.

Thanks,

Laguerta

Answers (1)

Answers (1)

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

I will never follow method one as suggested by you.

To add for the "Method 2", i will create a separate (new) workspace for different instance like DEV, QA, PROD.

eg. Once DEV is done, i ll export the whole project, and import the same in a new workspace for QA.

    •      Create a new SUP QA and SAP connection profile
    • Change connection profile to each mbo and its operations.
    • And deploy to SUP QA Env

     

Still it is time consuming.

there is another method (should be preferable)

Deploying mbo package from SCC instead of creating workspace and connection profiles.

Regards,

JK

Former Member
0 Kudos

Hellow Jitendra Yesterday I misunderstood your answer.

changing connection for each mbo and operation is what i dont want once it is very time consuming.

I was searching for an inprovement for method two as I only would have to change the connection profile.

Interesting that Deployment article Will try that soon!