Skip to Content

JavaServer Faces on Web AS

h3. Introduction   Since v6.30 SAP Web AS provides a J2EE 1.3 compliant Java Stack. Hence you’re now able to use SAP Web AS as your sole platform for both either ABAP or JAVA coded applications.  In this blog I will provide a short step-by-step guide about how to migrate an existing, simple JavaServer Faces application (that might probably run on a non-SAP server so far) to the SAP NW Developer Studio (NWDS) and how to run this application on the SAP J2EE engine afterwards.    After describing the necessary steps in detail, I will also provide a short summary of the procedure at the end of this blog.  If you’re planning to make use of JavaServer Faces in NWDS, I hope the information contained in this blog can help you to do so.   h3. JSF requirements   JavaServer Faces (JSF) is a comparatively new framework for developing web applications using JAVA. It is intended to run in a Servlet 2.3, JSP 1.2 web container. Furthermore you’ll need the JSF API and two special JSP tag-libraries to make use of this technology.    Both, the Servlet 2.3 and the JSP 1.2 API, are integral parts of the J2EE 1.3 standard. In this respect, SAP Web AS meets these demands of JSF since version 6.30.     You can download the JSF API and the JSP tag-libraries directly from Sun (look for the JavaServer Faces Reference Implementation at   (    During my work on this blog I tried with a small JSF application using the Servlet 1.2 API and the JavaServer Faces 1.1.01 reference implementation (you can download both from sun), which contained just some plain HTML pages, JavaServer pages and managed beans.   h3. JSF on Web AS: Step by Step guide   * step:  You’ll first need a new Web Module Project in SAP NWDS in which you will “transfer” your JSF application. So start with creating this Web Module Project in NW Developer Studio.    0.1.   0.2. Therefore you have to be in the J2EE Development Perspective (Window->Open Perspective). 0.3.   0.4. Then create a new Web Module Project (File->New->Web Module Project). 0.5.       image ~Fig. 1: Create new Web Module Project~    The structure of this new Web Module Project should look like shown in Fig.2: image
You must be Logged on to comment or reply to a post.
  • Michael,

    JSF is a SAP WebAS external library by nature. So I guess it is better to wrap it first this way and expose only API parts to consumers (jsf-api + jstl AFAIK).


    • Hi Valery,

      I just looked for a way, that wasn't to complicated but works (all I wanted :).

      I'm sure the're many ways to improve that method, but I didn't try by myself (so can't say much about if and how they work) -I'm sorry.

      Feel free to upvalue this blog with your own proposals.


  • Hi,
      Can we directly use the Migration plugin?
    If that is possible then we can have the migration done in no time at-all and at the same time do it the SAP way..


    • Hi,

      when I worked on the documents I now used to write this weblog, the migration kit was still in development and did only support BEA WebLogic. At that time, I couldn't get some test material to try the migration kit together with JSF.

      Nevertheless, here's my opinion (please keep in mind, that I haven't tried yet):
      To make use of JSF, actually you just have to make sure, that some jars are included in your web project in the right way.
      The Migration Kit is used to migrate whole J2EE applications to WAS. I don't think there's something special about JSF and the usage of the migration plugin (->it might not be necessary, when migrating a simple JSF application like I did).

      The only problem I can currently think of, is that the migration plugin only works for certain web-servers (these are Jboss, BEA and IBM).
      So you won't get the chance do make use of this tool if your application runs on a different server.