NW 7.3 + iView from remote source wizard + R3 Web Dynpro ABAP, not working

Question

Hi,
I think this forum is my last resort.
I'm running NetWeaver 7.3 Enterprise Portal and also have an existing ECC6 on backend.
Our ABAP Programmer has built some WD4A application on ECC, I'd like to made them available
on EP as ABAP WebDynpro iView.
From the document, I know the way to create ABAP WD iView is different since 7.3. I have to use "iView from remote source" to do it.
On EP side, I have made an system alias (test ok) for ECC, assigned permission, provide mapping id/pwd, and test. 
On ABAP side, all webdynpro app are activated (T-code sicf, /sap/bc/webdynpro, /sap/public/bc/webdynpro...). I can even test WAS by bringing up browser and access some sample ABAP webdynpro .
However, I cannot success on "iView from remote source" wizard and it always show me "Nothing found. Check your search Criteria.".   Eventhough I use "*" as search criteria.
Anyone has the similar situation ? I even doubt that it is a placeholder of a feature , not working for now. Anyone made it work on NW 7.3 ?
More detail:
My System Alias for ECC:   
      Application Host: myr3.mydomain.com
      SAP Client: 600
      SAP System ID:   DEV
      SAP System Number: 00
      Server Port:  <leave it blank>
      System Type: SAP_R3
      Logon Method:  UIDPW
      User Mapping Type: admin,user
      ICM Host: myr3.mydomain.com:8000
      ICM Protocol: http
      ICM URL prefix: <leave it blank>
      SAP Netweaver AS Description: <leave it blank>
All other fileds are leave it as default value
I also assign a group to have "read" and "user" permission to this system
Also assign Alias to the system.
I also create a user belong to the group, assign his system mapping an ECC user ID & PWD to it.
I tested the System alias, it is working (both WEB AS  test, and R3 test)
Then I try to create an iView on EP, under a PCD folder , new->iview->iview from remote source. A wizard show up. Then I can select the ECC alias just created, and provide * as application search criteria, and then select "WEB DYNPRO ABAP" as the application type. Then "GO"
as I mentioned, it always show "Nothing Found. Check your search crieteria"
But I'm sure the web dynpro applications are activated on R3.
OK, that's it, please help this one. Thanks
IF YOU DID MAKE IT WORK ON YOUR NW 7.3, PLEASE DROP A LINE HERE SO I KNOW IT IS MY OWN PROBLEM !!!
Edited by: Wilson KU on Nov 14, 2011 10:42 AM
Edited by: Wilson KU on Nov 14, 2011 10:46 AM

Answer 1

Thanks for the reply,
[About Backend]
I feel confident about the backend R3 system because I can use the WAS URL to access the sample WD4A application, for example, I can bring up the wd4a application ui in my browser. It is purely browser and R3 stuff, no EP involved.
http://soeprdev.mydomain.com:8000/sap/bc/webdynpro/bobf/demo_sales_order?sap-client=600&sap-language=ZF
I also already activate all nodes and sub-nodes (in SICF Services) under /sap/bc/webdynpro as well as /sap/public/bc/webdynpro. (and some other nodes to make icon and include work)
[About the system object in EP]
I have done all kind of test on the system object (alias):
1. In EP System Administration -> Landscape Configuration, I select the system object, click "Test Connection", It shows me a Check mark, and the detail message is SOE_DEV_600 connection
2. Edit the System object, then click on "Connection Tests" page, I see two lines there, check both and click test, here is the result:
SAP Web AS Connection:
: Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if the system object has a valid system alias
4. Check if an SAP system is defined in the system object
5. Validate the following parameters: Web AS protocol; Web AS hostname
6. Checks if the host name of the server can be resolved.
7. Pings the Web AS Ping service (works only if the service is activated on the Web AS, and only on ABAP Web AS)
8. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. System retrieved successfully
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ICM Protocol (http) ICM Host Name (soeprdev.mydomain.com:8000)
6. The host name (soeprdev.mydomain.com) was resolved successfully
7. The Web AS ping service http://soeprdev.mydomain.com:8000/sap/bc/ping was pinged successfully
8. An HTTP/S connection to http://soeprdev.mydomain.com:8000 was obtained successfully.
Connection Test for Connectors:
: Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the back-end application using the connector defined in this system object
Results
Default alias retrieved successfully
Connection successful