on 08-18-2010 10:45 AM
Hi all
I am newbie on ES Workplace system(s).
I changed password as said for all systems HU2(ECC),HU4(CRM),HU5(SRM),HU6 (PI),HU8(SCM)
and all work fine except HU6,
I can browse the SLD, but cant acces the integration Builder, it fails with the following errors.
======================================================================================================
com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Unable to connect to server P4://pi.esworkplace.sap.com:50004. Check server availability..........
======================================================================================================
Any idea?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Okay, I missed the part about trying to access the integration builder on the PI system. Can you access ESR & not Integration Directory? or both?
If it's ID then I think that access to the PI configuration is denied intentionally. Why do you need access to the PI config when evaluating Enterprise Services in ES Workplace?
Imagine if everyone had access to that, what a mess that would end up being
Alternatively try adding a host entry as stipulated below to see if that makes a difference:
[http://www.sdn.sap.com/irj/sdn/explore-es?rid=/webcontent/uuid/49e5ebd6-0d01-0010-86bd-e86cfe03c9a2] [original link is broken];
Regards, Trevor
Hi,
The other SDN'ers can correct me if I'm wrong but I don't think you're going to get that working using this facility.
The main reason for making these systems available in the ES Workplace is to allow the SAP ecosystem to evaluate SAP Enterprise Services. In fact, the more I think about it, it makes a lot of sense if access to the whole integration builder is restricted in this environment. This would also mean that people can't add any new Service Interfaces at will.
So you evaluate the services that SAP delivers out of the box & decide whether they can potentially work for you before you adopt them. Adopting them could possibly also mean an upgrade depending on what release the services were made available. The otehr reason for making these backend systems available is to speed up adoption of SAP Enterprise Services and SOA. So the customer doesn't need to go through a lengthy exercise of an SAP installation or upgrade before knowing whether a service could work for them.
Regards, Trevor
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.