SAP NetWeaver Portal enables the creation of iViews based on remotely
located systems. In case of connection failure, an exception will be
raised. This blog was written in order to assist with troubleshooting
the root cause of the connection failure.
In addition the following documentation page provides full description about this feature:
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/f5/b36fcd92a5472bbad125a9c6a0fcf8/content.htm
and recently new traces have been added (see note number 1940155).
There are 4 different types of iViews from remote source available:
The values filled in the wizard fields must be valid according to the type of remote iView being generated.
The table below provides information about the relevant fields and values that should be used for each iView type
1. SAP Portal Component iView
2. Transaction
3. Web Dynpro ABAP
4. Web Dynpro Java
5. Appendix Screenshot How to verify that "user mapping for system access" is defined for your user?
Check under: User Administration -> identity management -> User mapping for system access:
In addition the following documentation page provides full description about this feature:
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/f5/b36fcd92a5472bbad125a9c6a0fcf8/content.htm
and recently new traces have been added (see note number 1940155).
Background
While creating new content using the "content admin" role, you can choose to create "iView From Remote Source"There are 4 different types of iViews from remote source available:
- SAP Portal Component iView - iView is based on a remote portal component
- Transaction - iView is based on a transaction from SAP back end system
- Web Dynpro ABAP - iView is based on content from SAP Web Dynpro ABAP from remote system
- Web Dynpro Java - iView is based on content from SAP Web Dynpro JAVA from remote system
Prerequisites
Before using the iView from remote source feature the following Prerequisite must be filled:- The relevant system must be defined under portal system landscape. Click here for more information about 'system landscapes'.
- Make sure to create alias to the relevant system. Click here for more information about 'Managing System Aliases'.
- Use the test connection feature while creating the system: Check the "Run connection test after clicking next". (make sure you type valid user and password)
The connection test should pass successfully
Procedure
As previously mentioned, it is highly important to fill the values in the iView generation wizard according to the type of remote iView chosen.The table below provides information about the relevant fields and values that should be used for each iView type
Web Dynpro Java
|
Web Dynpro ABAP
|
Transaction
|
SAP Portal Component iView
|
Filling the wizard fields
|
select the alias of the SAP system from which you want to take the iView
|
select the alias of the SAP portal system from which you want to take the iView
|
'Search In' Field
| ||
type a string for filtering the transactions you are interest in, you can type '*' for no filter at all
|
type a string for filtering the available iViews, you can type '*' for no filter at all
|
'Search For' field
| ||
choose "Web Dynpro Java"
|
choose "Web Dynpro ABAP"
|
choose "Transaction"
|
choose "SAP Portal Component iView"
|
'Application Type' field
|
n/a
|
[optional] you can limit your search to a specific role
|
'Search in Role'
| ||
choose According to the described in this link
|
n/a
|
'Implementation' field
| ||
Web Dynpro Java | Web Dynpro ABAP | Transaction | SAP Portal Component |
:Screenshots
|
Troubleshooting
In case of connection failure the following message will appear in the portal: "Connection to SAP component system failed; check the system settings"
The table below provides tips for troubleshooting according to the relevant iView type:
Web Dynpro Java
|
Web Dynpro ABAP
|
Transaction
|
SAP Portal Component iView
|
Step#
|
Recheck the values you entered into the wizard fields, make sure they are valid
|
1
| |||
|
2
| |||
Make sure the user you are connected with has access to the remote portal you are trying to connect
|
n/a
|
n/a
|
Make sure the user you are connected with has access to the remote portal you are trying to connect
|
3
|
n/a
|
Verify that "user mapping for system access" is defined for your user (under identity management – see
Appendix Screenshot |
n/a
|
4
| |
Check the recent trace file for more information
|
5
|
Screenshots
The screenshots below shows the process for the different iView types:
The result should be a list of all the available iViews:
In case the operation fails, the following message appears on the screen:
The result should be a list of all the relevant transactions:
In case the operation fails, the following message appears on the screen:
The result should be a list of all the relevant content:
In case the operation fails, the following message appears on the screen:
The result should be a list of all the relevant content:
In case the operation fails, the following message appears on the screen:
Check under: User Administration -> identity management -> User mapping for system access:
No comments:
Post a Comment