Hello,
The scenario we want to build is:
- Have one portal
- Have one J2EE Engine
- Have one backend with TWO clients (e.g. 100 and 200)
- Have ESS/MSS running and connect to both clients (multiclient szenario)
What has been done so far:
1) Copied folder for ESS or MSS with iViews, Pages, Roles etc. to connect those to client 200
2) Create new backend client and added to system landscape
3) Create new JCo connection (New JCo Connection for new client). We have done that with extension CL2 and adding to iView application paramter sap-wd-arfc-wd-usesys for redirecting the JCo connection of WebDynpro - that works)
4) Change PCD location of one Service (e.g. Who is Who for testing) on backend <b>client 200</b> with Transaction SPRO - changed key EMPLOYEE_WHOISWHO_SERVICE05 - to the PCD location of copied iView from step 1.
5) System aliases are defined for client 200 at time
Status:
- We have a set of copied iViews where JCo is redirected to client 200. Redirection of JCo Connections works
- The original set of ESS iviews is not modified, JCo Connections established to connect to client 100
Problem faced: On ESS overview page iView (for example) we cannot divide the iViews to be called.
- On copied Client 200 Overview iView if we click "Who is Who" for example, the copied "client 200" 'Who is Who' iView starts.
- On original Client 100 Overview also client 200 Who is Who is started (!!!)
-> As System Aliases all point to 200 we assume both getting information from Client 200 (?) over System Alias (?)
What we assume:
- We need to create a second set of System Aliases - keep the original to point to 100, make a new set to point to 200
- Problem: we can't have two System Aliases with the same name
So how can we get the second copied set of ESS/MSS to work with different System aliases? Or do we miss out here something else?
Frank