Deployment configurations for widgets

 

+

Search Tips   |   Advanced Search

 

Deployment configurations are properties you can use to build and deploy your application to a server. Deployment configurations that you create can be reused for other projects.

When you deploy your project, a local WAR file is created. A WAR file is a web application archive file for distributing a collection of models, profiles, JavaServer Pages, servlets, Java classes, XML files, tag libraries and static Web pages (HTML and related files) that together constitute a Web application. When you first create your project, you can define a deployment configuration or associate a current configuration with your project. You can specify the location in which to store the WAR file. The location that you specify is stored in the project properties.

You have the following deployment choices.

• Create a development WAR file
• Create a production WAR file

 

Create a development WAR file

The development WAR file contains utilities that help speed your development time. This file is used to deploy your application for development. After you deploy the project, the WebSphere® Portlet Factory Designer is configured to automatically update your deployed application with changes made to your project.

Steps to local deployment:

1. Create the project.

2. Choose to automatically deploy the project with the auto-deploy option or create your own deployment configuration.

3. Create a model.

4. Click Run > Run.... Then click WebSphere Portlet Factory > Active Model to test the widget.

5. Continue development. The application automatically refreshes the WAR file after each Run command.

   If the deployment succeeded, WebSphere Portlet Factory automatically synchronizes the deployed application from updated project contents.

 

Create a production WAR file

If you are ready to deploy your application to a production environment, you need to build a production WAR file. The production WAR file is optimized for size and security. This file does not contain the development and test utilities that are available with the development WAR.

Steps to production deployment:

1. Right-click on the project name. Click...

   Application Server WAR | Build WAR for production deployment

2. Deploy the WAR in either of two ways:

   • To a local or network-accessible Lotus® Mashups server.

   • To a fileshare or a network server accessible from IBM InfoSphere MashupHub to upload the WAR file and then publish it to Lotus Mashups.

See also:

1. Updating a WAR file
2. Synchronize (copy) modified files
3. WAR interactions at project creation
4. WAR interactions during development
5. WAR interactions during deployment to production
6. Excluding files from a deployed WAR
7. JAR files in a WAR
8. Creating a portlet WAR without access to a server
9. About deploying a project to a remote server

Parent topic: Overview: deployment