Skip to main content link. Accesskey S
  • Log In
  • Help
  • IBM Logo
  • IBM Composite Applications wiki
  • All Wikis
  • All Forums
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
Community Articles Product Documentation Learning Center IBM Redbooks This category Custom Search Scope...
Search
Community Articles > Deploying Applications > Deploying NSF > Setting Deployment Component Properties
  • New Article
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Robert F Harwood
Contribution Summary:
  • Articles authored: 59
  • Articles edited: 54
  • Comments Posted: 8

Recent articles by this author

Lotus Domino Designer help updates for 8.5.2

How to find the documentation for Lotus Domino release 8.5.2

Product-specific links for the IBM Support Portal

The IBM Support Portal simplifies the customer online support experience.

Creating custom actions in java

During this tutorial you will extend the Browser Application Container with a custom container action created in Java. Our use case is to allow a user to highlight any text in a note and quickly see the translation in another window on the same page. We will create a composite application page ...

Expeditor Toolkit 6.2 and Lotus Expeditor wiki now available

The Lotus Expeditor 6.2 Toolkit is now available for download. In case you are not familiar with the toolkit, it can be used to build plug-ins for Notes, Sametime, Symphony, and Expeditor. The 6.2 version of the toolkit can be used with beta releases of Notes 8.5. Additional information about the ...

Step-by-Step deployment scenario 1: Application "move" example

This article describes a deployment scenario that "moves" an NSFbased composite application from a development environment (local only or test Domino server) to a singleserver production environment . Note: This information is provided for example purposes ONLY. It is published to provide ...

Learning Center articleSetting Deployment Component Properties

Added by Robert F Harwood | Edited by IBM contributor Michael Cooper on October 14, 2009 | Version 9
  • Edit
  • More Actions Show Menu▼
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: basics, deploying, drag and drop, Eclipse components, NSF components, designing, Notes, linking

Table of Contents
| Next | Previous

This article contains the following sections:
  • Using static links with Eclipse components
  • Using dynamic links with Eclipse components

You can refer to Eclipse components in various ways. As part of the Eclipse component development process, developers typically refer to the Eclipse components via view extension names. You can launch Notes directly from the Eclipse/Expeditor IDE with your Eclipse components and then refer to the Eclipse components via the Composite Application Editor component provider "Locally installed components." Refer to the Composite Application Editor and Lotus Expeditor online help for more information.

Using static links with Eclipse components

Eclipse components can also be referred to using static links. Refer to the following for more information: http://www-10.lotus.com/ldd/compappwiki.nsf/dx/advanced-component-properties and http://www-128.ibm.com/developerworks/blogs/page/CompApps?entry=managing_components_with_multiple_dependant.

The following provides an example. The URL property contains the server name when using static paths.

com.ibm.rcp.viewId - com.ibm.cademo.util.comp.constants.ConstantsView
id.feature - com.ibm.complib2.comp.basic.feature
version.feature - 8.1.20080530
match.feature - compatible
url.feature - http://w3.myserver.com:8080/ajax.nsf/site.xml


Notes can also access Eclipse features from different update sites such as:
  • Classic Eclipse update sites via HTTP
  • NSF based update site (updatesite.ntf) via NRPC
  • NSF based update site (updatesite.ntf) via HTTP

There are advantages to putting Eclipse components in NSFs. One would be better manageability. Refer to the "Managing client plug-in deployment" section of the Domino Administrator help for more information.

You can access NSF based update sites either via NRPC or HTTP. HTTP, for example, is used when standalone Sametime accesses Eclipse components from Domino.

For Notes, it is recommended that you use NRPC, however, because it is more efficient. The following provides information on the correct NRPC syntax:

Sample server:

Domino server name: jdoe-1/JDoe
Domino ip address: 127.0.0.1
Domino DNS address: jdoe-1.us.ibm.com

Syntax for sample NSF based update site on a server:

server: jdoe-1
path: a_dir/myUpSite.nsf
rep id: 852574AA00371F34
nrpc://jdoe-1/852574AA00371F34/site.xml
nrpc://jdoe-1/852574AA00371F34/site.xml
nrpc://jdoe-1/852574AA00371F34
nrpc://127.0.0.1/
852574AA00371F34/site.xml
nrpc://127.0.0.1/852574AA00371F34/site.xml
nrpc://127.0.0.1/852574AA00371F34
nrpc://jdoe-1.us.ibm.com/__852574AA00371F34/site.xml
nrpc://jdoe-1.us.ibm.com/852574AA00371F34/site.xml
nrpc://jdoe-1.us.ibm.com/852574AA00371F34

Syntax for local sample NSF based update site:

local db
path: a_dir/myUpSite.nsf
rep id: 852574AA00371F34
nrpc:__852574AA00371F34/site.xml
nrpc:
/852574AA00371F34/site.xml
nrpc:852574AA00371F34

Static links to Eclipse components create the same problems that static links to NSF components do. They may also break when applications are moved from a development environment to a production environment.

Using dynamic links with Eclipse components

To help avoid link breakage, it is recommended that you use dynamic links. Dynamic links for Eclipse components are created by leaving the "url.feature" component property empty. That way, Eclipse components can be "pushed" to Notes clients or "pulled" from the Notes client.

Eclipse components can be "pushed" to Notes clients via the Widget catalog. For more information, refer to the "Deploying client plug-ins with widgets and the widget catalog" section of the Domino Administrator help.

Eclipse components can be "pulled" from Notes when that is required. In this case, the "url.feature" component property should also not be set. You should use the Notes Administrator whitelist feature to accomplish this. Using the whitelist feature, the client will try to contact any update site the Notes client knows about in a certain order and try to locate the necessary Eclipse component. For more information, refer to the "Controlling feature install and update with update site" section of the Domino Administrator help.


Table of Contents
| Next | Previous

  • Edit
  • More Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (4)
collapsed Versions (4)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (9)Oct 14, 2009 4:12:49 PMMichael Cooper  IBM contributor
8Oct 14, 2009 4:12:07 PMMichael Cooper  IBM contributor
7Oct 11, 2009 7:35:01 PMDeanna Drschiwiski  IBM contributor
5Dec 5, 2008 9:40:00 AMRobert F Harwood  IBM contributor
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkIBM Collaboration Solutions
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use