on 04-25-2007 8:17 PM
The EP and the J2EE are running on the same WebAS 7 (EP7). An URL iView is used for integration. I found two drawbacks:
- The path of the URL can not be server relative, so just starting with /myapp/test.jsf
- Neither can the iView by pre-customized by a system setting, e.g. I configure the server's setting (e.g. the URL) and the iView is just adding its part of the URL.
<b>Problem: </b>When I do transport my iViews I have to manually adjust all the URLs, unlike with ABAP WebAS iViews I can not just set the alias to a different system. If I was able to use relative links I could also just deploy at EP2 and my J2EE application on that server would be used.
Any idea how to overcome the problem?
Hi Frank,
You should use the Generic application integrator, which has all the features of URL iviews, and more (for instance user exits, for providing extra url parameters).
Check out the Howto document here:
http://help.sap.com/bp_epv260/EP_JA/documentation/How-to_Guides/25_HowToUseAppIntegrator_en.pdf
If you want to refer to the portal/j2ee system itself, you might want to try the builtin system with alias SAP_LocalSystem. In this case you don't have to define systems throughout your portal landscape
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Frank,
URL iView might not be the right choice, look for Application Integration (sorry, no specifics at this time, haven't got a portal here), it has much more settings to play with.
Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.