Before you can access your WebFacing application in a browser, the application must first be started in WebSphere Application Server. For information about starting your application in the application server, see the section of this guide: Deploying WebFacing applications to WebSphere Application Server .
http://host_name:<host_port>/<context_root>/For example, if your server is MYSERVER, your port is 9080, and the context root value that you entered for the application in the administrative console is webfacing1, then you would access the application with an address like:
http://MYSERVER:9080/webfacing1/The host name for your iSeries server is case sensitive. To see what this value should be, run the command CFGTCP from an iSeries command line. On the Configure TCP/IP menu, choose option 12 Change TCP/IP domain information and make note of the Host name value. This is the value, without the quotation marks, that you must specify for your host name.
http://MYSERVER:9080/webapp/webfacing-proj1/
http://host_name:<host_port>/<context_root>/index.jspThe index.jsp file is generated by the WebFacing conversion. Most Web server configurations do not require that it is included as part of a URL. That is, in most configurations, if a user enters a URL that ends with the <context_root>, the server by default displays the index.jsp file for that context.
When you access the page, you see links that correspond to the Command labels you chose for the CL commands that you created in the WebFacing Project wizard. By clicking these links, you launch the corresponding applications on your iSeries server and the output for the application is displayed in your browser.
<a href="WFInvocation.do? inv=INV1">CALL ORDENTR</a>Launch order entry.</a>Your links will vary from this depending on the command you are using to call the application. To use the link, copy and paste the link into the source for your HTML pages.
(C) Copyright IBM Corporation 1992, 2006. All Rights Reserved.