Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • IBM Composite Applications wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 6.2
  • 6.2.1
  • 8.0.1
  • 8.5
  • 8.5+
  • 8.5.1
  • advanced features
  • advantages
  • API
  • app dev
  • assembling
  • basics
  • benefits
  • Browser
  • CAE
  • catalog
  • changing page properties
  • changing value to another type of value
  • code snippet
  • component library
  • component properties
  • components
  • Composite Application Editor
  • Composite Applications
  • container components
  • containers
  • custom actions
  • debugging
  • demos
  • deploying
  • designing
  • developing
  • Eclipse
  • Eclipse components
  • editing properties
  • Editor
  • education
  • enablement
  • Expeditor
  • extending
  • extensions
  • FAQ
  • feature rules
  • framework
  • getting started
  • Help
  • HOD
  • host on demand
  • how to
  • Java
  • lead manager
  • linking
  • live text
  • match rules
  • new users
  • Notes
  • Notes components
  • nsf
  • NSF components
  • overview
  • page navigation
  • page properties
  • Palette
  • PBE
  • PIM
  • plugins
  • Portal
  • preference
  • product documentation
  • programming
  • properties
  • property broker
  • property broker editor
  • Property Broker Monitor tool
  • provisioning
  • resources
  • roadmap
  • samples
  • setting component properties
  • Sidebar
  • sideshelf
  • Symphony
  • Symphony view component
  • technote
  • testing
  • toolkit
  • TopologyHandler
  • troubleshooting
  • tutorial
  • update site
  • updating
  • upgrading
  • video
  • view
  • Web
  • web services
  • white lists
  • widgets
  • Wiring
  • WSDL
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > Deploying NSF > Setting Deployment Component Properties
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

Setting Deployment Component Properties 

expanded Abstract
collapsed Abstract
No abstract provided.

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

expanded Article information
collapsed Article information
Category:
Deploying NSF
Tags:
basics, deploying, drag and drop, Eclipse components, NSF components, designing, Notes, linking

This Version: Version 9 October 14, 2009 4:12:49 PM by Michael Cooper  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (4)
collapsed Versions (4)
Version Comparison     
Version Date Changed by               Summary of changes
This version (9) Oct 14, 2009 4:12:49 PM Michael Cooper  
8 Oct 14, 2009 4:12:07 PM Michael Cooper  
7 Oct 11, 2009 7:35:01 PM Deanna Drschiwiski  
5 Dec 5, 2008 9:40:00 AM Robert F Harwood  
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 ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use