Problem while creating SAP Web Dynpro iView

Question

Hi,
I am creating SAP Web Dynpro iView from iView Template.
The SAP Web Dynpro System Object is being created. The System Alias is also being created.
The Test Connection is successful with Portal Server.
Now, while creating SAP Web Dynpro iView from Template in Step 4:
I am not getting my System while an old system which is being deleted is being displayed.
Name of my System Object is: WD_System and System alias is: WD_Alias.
The Step name is:
Step 4:  Application Parameter
Enter the paramater(s) of the application for which you want to create the iView 
Regards
Kaushik Banerjee

Answer 1

Hi Bala,
I am not getting the System Alias under:
User Administration-> User Mapping-> Logon Data(Select a Principal) (System Alias).
The System is successfully built under System Amininstration->System Configuration->System Landscape->Portal Content->kaushikb named WD_System and System Alias is named as: WebDynpro_alias.
The Test Connection is successful.
I am displaying the result below:
SAP Web AS Connection
  Test Details:
The test performs the following:
1. Checks the validity of the system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Checks if a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (kolapon:50000)
5. The host name kolapon was resolved successfully.
6. The server kolapon was pinged successfully.
7. The WAS ping service http://kolapon:50000/sap/bc/ping was not pinged successfully. If the ping service is not activated on the WAS, you can try to call the ping service manually.
8. An HTTP/S connection to http://kolapon:50000 was obtained successfully.
Regards
Kaushik Banerjee