Background:

We upgraded our Portal from 7.0 to 7.31 which was a huge leap forward and there was so much things we need to consider while doing this upgrade. In 7.0 all Portal components used were all PAR files and now there are no PARS. You will have to migrate all these files. One of the challenges we had was modifying the standard Portal logon page. We had to go through numerous documents on how to modify the logon pages, how to modify the war files in NWDS using NWDI and how to package the war file into an ear and deploy to the server. All the pains gone through to make that a success is the reflection of this document.

Solution Implementation:

1. Open your NWDS and logon to NWDI. Navigate to the Development Configuration in which you would like to create this new development component.

2. Create a Web Module Development Component.

WebModule DC.png

3. Give the Web Module DC Details. Click finish. This will automatically create an activity in NWDS and attach all the files and folders to it respectively.

WebMod DC Details.png

4. It’s time to now import the standard logon file from the server that was downloaded. Right Click on the DC and import WAR File.

Import WAR.png

5. Select the War File Location and a new local Web project name where the contents will be uploaded.

Import.png

6. In the above step the default jar files will be added to the lib folder in the local web project. Additional jar files that are required to be added to eliminate the errors in jsp’s can also be added.

7. Copy the Web Content Folder of local project and replace the web contents folder inside the NWDI DC.

8. Modify the JSP Files as required to customize your logon screen. Build the DC.

9. This DC is not directly deployable. You will need to package this into another DC of type Enterprise Application.

Ent App.png

10. Give the DC Details.

DC Details.png

11. Select the Web Module Project in the Next Screen so the WAR file is added to the deployment descriptor of the the new DC created for deployment.

Select Web Module Project.png

12. Modify the application-j2ee-engine.xml file in the DC as below. Provider name for the application is usually your client name. The provider name defines your namespace where your applications reside on the AS Java.

/wp-content/uploads/2013/08/application_j2ee_engine_261747.png

13. Now, Right click on your DC and Java EE Tools > Generate Deployment Descriptor Stub. This will generate application.xml file.

14.The application.xml file will look like the below. By default the Context-Root will be referring to the Web Module DC you created but you can modify the Context-Root Name to a different one which will be used in the NWA Configuration for the logon page.

/wp-content/uploads/2013/08/application_261748.png

15. Build your DC and Deploy it to the server.

Hurray !!! Next Step is your nwa configuration where you need to give the context-root name that we used above and restart the server.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply