Skip to Content
author's profile photo Former Member
Former Member

Clarification regdng instances & clients for SolMan w.r.to Service Desk Msg

Hello Gurus,

Pls help me.

As we face issues while deleting service desk (test) messages and also to test various other new features of SolMan we are planning to have Sandbox & Production instances for SolMan.

Now the query is

ℹ️ Do we need two seperate instances for Sandbox & Production?

(or)

(ii) Can we use two different clients of the same instance as Sandbox & Production clients?

(iii) If we can use different clients of the same instance what will happen to the service desk messages which we create in the Sandbox client? Will they in any way affect the Production client?

(iv) Also what will happen to the IMG configurations we make in the Sandbox client? Will they affect the Production client? Or everything can be redone for the Production Client or can be transproted?

Pls clarify. All useful answers will be suitably rewarded.

Thanks & best regds,

Alagammai.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 09, 2007 at 03:22 PM

    Hey Arunachalam,

    Let me address your issues pointwise:

    ℹ️ Do we need two seperate instances for Sandbox & Production?

    (or)

    (ii) Can we use two different clients of the same instance as Sandbox & Production clients?

    Answer:

    You can chose any options. Both the options are safe. you wont have any problems..

    (iii) If we can use different clients of the same instance what will happen to the service desk messages which we create in the Sandbox client? Will they in any way affect the Production client?

    Answer:

    Nothing will happen to those sandbox msges untill and unless you archive them.

    If you prefer to use the same instance with PRD as difrrent client on the same instance, this additional (Test msegs ) that you created in sandbox <b>client will NOT</b> interfere with the Production client.

    So chill and dont worry.

    The reason being so is that the messages you create is client specfic, so messages you create in Sandbox client <b>will not be visible on PRD client</b>.

    (iv) Also what will happen to the IMG configurations we make in the Sandbox client? Will they affect the Production client? Or everything can be redone for the Production Client or can be transproted?

    Answer:

    The customizing settings that you had done for service desk implementation in sandbox client <b>will not be available</b> in PRD client since this settings are client specific.

    So you are left with two options:

    A) if you have set of transport request for Service desk implementation in sandbox client, then those TR can be imported in PRD client.

    B) If you dont have Proper TR in Sandbox client, then are are better off doing the configurations again..

    Plz note: No matter what strategy you follow( A OR B ), you have to again establish RFC connections from you PRD client to the satellite ssytem.

    If you decide to have seprate instance for PRD, even then you can move those TR's in your sandbox client into new PRD instance and again establish RFC connections from SOLMAN to Satelllite systems.

    Hope i answered all your queries.

    PLz reward for usefull answers.

    Regards,

    Anand.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.