Recent pages

Edit
page

New
page

Print
page
Page last modified 23:47, 11 Dec 2008 by Amy
0
Page Notifications Off
Documentation > How To : Posting, Sharing, Deploying, and Managing your Applications

How To : Posting, Sharing, Deploying, and Managing your Applications

From $1

Back to Concepts and How TOs

  1. 1. Description
  2. 2. Prerequisites
  3. 3. Procedures
    1. 3.1. Posting a Solution or Project
    2. 3.2. Sharing a Solution or Project
    3. 3.3. Managing Your Shared Items
      1. 3.3.1. Using a Shared Post in your Solution 
      2. 3.3.2. Managing your Shared Posts 
      3. 3.3.3. Updating and Modifying Dependencies 
      4. 3.3.4. Changing to a Specific Version of a Shared Post
    4. 3.4. Deploying an Application
    5. 3.5. Managing Deployed Applications
      1. 3.5.1. Making an Application Available to Your End Users
      2. 3.5.2. Moving a Deployment
      3. 3.5.3. Activating and Deactivating a Deployment
      4. 3.5.4. Removing a Deployment
      5. 3.5.5. Changing a Deployment's Post Dependency
  4. 4. Error Handling
    1. 4.1. Posting
      1. 4.1.1. Members with Conflicts
      2. 4.1.2. Members Not Checked In
  5. 5. Examples
  6. 6. Next Steps
  7. 7. Tags

Description

This document describes how to use the Staging Manager located on the Publish tab to post and share solutions and projects, as well as how to deploy and manage applications.

Procedures

Posting a Solution or Project

Before you can post (and then deploy or share) any aspect of an application, you must first add an AppProject and  to your solution, and check in your solution.

To post your solution or project

  1. If you have not already done so, add an AppProject and a Main class to your solution.

    Note Choosing the Main Class template when you create the AppProject adds a Main class, its functions, and a blank form to your AppProject. Choosing the Empty template simply adds the AppProject without any classes. If you negelected to add the main class earlier, you can add a Main class to your AppProject, or you can make an existing class your main class.

  2. Using the getMainForm function, provide the form interface for the form you want to be the main form for your application.

    Note If you negelect to do this, the application machinery will search for a form interface called "main". If no such interface exists, your application does not launch.

  3.  Add any other initialization behavior you want using your Main class and its functions.
  4. In the Solution Explorer, ensure your AppProject is checked-in to the depot. 
  5. At the top of the Builder, select the Publish tab.
  6. In the Filter View, select the Posts filter.
  7. Just below the Posts title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the solution you want to post.
  8. The Posts Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the project you want to post.
  9. On the lower right corner of the Summary View (to the right of the Filter View), click the Add button (+).
  10. In the Create new post dialog, under Post Settings click the down arrow (labeled <= Choose Project to Post).
  11. In the dropdown box that appears, the solution you selected in the Filter View appears in expanded form, displaying each of the projects contained in the solution. Select the project you want to post.
  12. Most of the Project Settings in the Create New Post dialog auto populate.
    1. The Name text edit box auto populates with the name of the project you selected. If you want to give your post a different name, do so.
    2. Likewise, the Version text box is provided with an auto-populated versioning number using the project name, followed by a number beginning 0.1 (for the first version). Subsequent posts increment from there. You can also change this numbering system to suit your tastes. Subsequent posts will also auto-increment based on the numbering system you introduce. 

      Note If you click the Pushpin button next to the text edit box, a number based on the current GMT date/time appears in the box.

    3. The Description box remains blank. Fill in any description details you want.
  13. Click OK.
  14. Your new Post should appear in the Summary View. By selecting your post in the Summary View, you can view the Details in the Details View, and you can add a description of your post in the Description box (you must tab or click outside the box before the Save and Cancel buttons enable).

Sharing a Solution or Project

  1. Follow the steps for posting a solution or project, above. 
  2. In the Filter View, select the Shares filter.
  3. Just below the Deployments title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the solution you want to share.
  4. The Shares Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the project you want to share.
  5. On the lower right corner of the Summary View (to the right of the Filter View), click the Add button (+).
  6. In the Create new Share dialog, under Share Settings click the down arrow (labeled <= Choose a Posted Project).
  7. In the dropdown box that appears, the solution you selected in the Filter View appears in expanded form, displaying each of the version of the projects posted in the solution. Select the version you want to share.
  8. Most of the Project Settings in the Create New Post dialog auto populate. Change settings as appropriate:
    1. Post: Non-editible display of the path to the post you selected in the step above.
    2. Post Version: Non-editible display of the version number of the post you selected above.
    3. Share Name: Name of the post you selected above. Edit as desired.
    4. Share License: Click the down arrow and choose a license option for sharing your project code. Explanations of the license options are presented with the license you choose.
    5. Make this the recommended Share version: Select this option if you have already shared another version of the same posted project and you have made changes you consider to supercede the previously shared code.
    6. Post Description: Add any information about the shared item you think will be helpful to a person wondering what your code contains.
  9. When finished making changes, click OK (or click Cancel to cancel the share).
  10.  Your new share should appear in the Summary View. By selecting your post in the Summary View, you can view the Details in the Details View, and you can add a description of your post in the Post Description box (you must tab or click outside the box before the Save and Cancel buttons enable).

Managing Your Shared Items

The following procedures help you to manage your shared items:

Using a Shared Post in your Solution 

For information on how to incorporate a shared post into your solution, see Using Import and Include 

Managing your Shared Posts 

Use this procedure to remove items from the Share and to change the description of shared items. 

To manage your shares:

  1. From the Staging tab, expand My Share.
  2. Highlight the shared post you want to manage.
  3. To remove the share post, click Remove. To change the description of the shared post, click Modify and type a new description.

Updating and Modifying Dependencies 

Use this procedure to update shared posts that you have incorporated into your solution. For example, if a developer has updated a shared post that you are using, you may want to update your solution to use the latest version.

Note The Check for Updates button works by checking the shared posts you are using for the Recommended tag. If you are using a shared post and a version other than the one you are using is marked Recommended, then the shared post is marked for updating.

To update dependencies:

  1. In the Solution Explorer (Design tab), select your solution.
  2. In the tool bar above the solution, click Modify Dependencies.
  3. In the Modify Dependencies dialog, the shared posts you are using in your solution are shown on the right. Click Check for Updates to see if any dependencies have been updated.
  4. To update dependencies, either select an individual dependency and click Update, or click Update All to update all dependencies.

Changing to a Specific Version of a Shared Post

Use this procedure to select a specific version of a shared post. You may want to select a specific version of a shared post (for example, an older version) if you update the shares you are using and discover that a developer has changed the shared post and, as a result, "broke" your application. 

  1. From the Modify Dependencies dialog, select the shared post on the right. Click Change.
  2. In the Change Dependency dialog, select the version of the shared post you want to change to.
  3. Click OK.

Deploying an Application

To deploy an application

  1. Follow the steps for posting a solution or project, above. 
  2. In the Filter View, select the Deployments filter.
  3. Just below the Deployments title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the solution you want to deploy.
  4. The Deployments Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the project you want to deploy.
  5. On the lower right corner of the Summary View (to the right of the Filter View), click the Add button (+).
  6. In the Create new Deployment dialog, under Location , you can click the down arrow and select a deployment location
  7. Under Settings click the down arrow (labeled <= Choose a Posted AppProject).
  8. In the dropdown box that appears, the solution you selected in the Filter View appears in expanded form, displaying each of the version of the projects posted in the solution. Select the version you want to deploy.
  9. Most of the Project Settings in the Create New Post dialog auto populate. Change settings as appropriate:
    1. Application URL: Edit the URL as appropriate. To add a additional URLs for this application, click the plus (+). To verify the URL, click the check mark.
    2. Deployment Name: Change the deployment name as desired.
    3. SSL Settings: Select either No (default), Allowed, or Required. If you select Required, all configured URLs are modified to have an https preface.
    4. Session Timeout: Set the session timeout (in minutes). The default is 30.
    5. Session Timeout Message: Set the session timeout message. The default is Your session has timed out.
    6. Arguments: To add deployment arguments, click the Add button (+) and add Key and Value pairs. To remove arguments, select an argument, then click the Remove button (-).

      Note See Working with Deployment Arguments for details on what you need to do to use deployment args.

  10. When finished making changes, click OK (or click Cancel to cancel the deployment).
  11. Read the Deployment Notice, then click OK.
  12. In the Deployments Status column, the word Installing appears. When the deployment finishes installing, the Status should change to say Active. Once the deployment is Active, you click the link in the Primary URL column launch your application.
  13. Clicking on a deployment in the Summary View causes the Details View to populate so you can view and edit the deployment data as you wish.

Managing Deployed Applications

The procedures that follow allow you to manage applications you deploy:

Making an Application Available to Your End Users

There are two ways you can make your application available to end users: as a stand-alone Web page or embedded into an HTML Web page.

To make an application available to your end users

  • To make the application available as a stand-alone application, simply post the URL specified during the deployment phase to your end users.
  • To embed the application into an HTML page, add an IFrame into the page that points to the URL specified during the deployment step.

Moving a Deployment

You can only move a deployment if you have more than one deployment location available to you (such as a registered image of the Bungee Application server). Only active deployments can be moved.

To move a deployment:

  1. In the Filter View, select the Deployments filter.
  2. Just below the Deployments title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the proper solution.
  3. The Deployments Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the deployment you want to move.
  4. In the Summary View select the deployment.
  5. Click Move Deployment.
  6. In the dialog box that's displayed, select the new location. When you select a new location, the Primary Application URL is updated to reflect the new location's URL.

    Note The URL is updated only if the application URL uses the same DNS hostname as the original location. If you are using a custom DNS address, then the URL is not updated. In this case, a warning message is displayed. Be sure to update the URL or the deployment will break.

  7. Click OK.

Activating and Deactivating a Deployment

To activate or deactivate a deployment:

  1. In the Filter View, select the Deployments filter.
  2. Just below the Deployments title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the proper solution.
  3. The Deployments Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the deployment you want to activate or deactivate.
  4. In the summary view, select the deployment.
  5. Below the summary view, click Activate Deployment to activate a deployment, or click Deactivate Deployment to deactivate a deployment. The status for the deployment changes to to show the change in state.

Removing a Deployment

To remove a deployment: 

  1. In the Filter View, select the Deployments filter.
  2. Just below the Deployments title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the proper solution.
  3. The Deployments Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the deployment you want to remove.
  4. In the Summary View, select the deployment.
  5. Below the summary view, and to the left, click the minus (-). A confirmation prompt is displayed.
  6. Click OK.

Changing a Deployment's Post Dependency

To change a deployments post dependency:

  1. In the Filter View, select the Deployments filter.
  2. Just below the Deployments title, click the down arrow, then, within the drop down box, expand into the DesignGroup groupings and select the DesignGroup containing the proper solution.
  3. The Deployments Filter View should populate with all the solutions in that DesignGroup. From that list of solutions, select the one containing the deployment whose dependency you want to change.
  4. In the Summary View, select the deployment.
  5. In the Detail View, in Application Post, click the down arrow.
  6. Select the post you want to use.
  7. Click Save.

Error Handling

Posting

Members with Conflicts

If you have a conflict when posting, the following error message is returned:

Members Not Checked In

A very similar message dialog is displayed if you have not (for instance) checked your AppProject into the depot prior to attempting to post your application.

Examples

See the Hello World portion of the Learn tab.

Next Steps

 

Tags

 

Tags:
Deploy, HOW_TO, Posting
Attach file or image
Files (0)
 
Images (0)
 
Comments (0)
You must login to post a comment.

 
Powered by MindTouch Core v.9.02.2