Search
Contribute
Navigation
- 8.5+
- actions
- advanced features
- advantages of composite applications
- API
- app dev
- basic NSF application
- basics
- benefits
- Best practices
- Best practices
- BIRT
- browser
- built-in actions
- built-in properties
- business value
- CAE
- CAI
- catalog
- changing page properties
- compatibility
- component
- component library
- component properties
- components
- Composite Application basics
- Composite Application basics
- composite application demonstration
- composite applications
- container
- container components
- context
- creating a sidebar
- creating wiring properties
- customer interests
- data model
- debugging
- demo
- demonstration
- deploying
- deploying applications
- deploying NSF components
- deployment
- drag and drop
- easy
- ECL settings
- Eclipse
- Eclipse API
- Eclipse basics
- Eclipse components
- Eclipse samples
- Eclipse tips
- editing properties
- education
- embedded browser
- enablement
- errors
- Expeditor
- Expeditor samples
- Expeditor toolkit
- extensions
- FAQ
- feature rules
- first application
- fundamentals of Eclipse
- general debugging tips
- generic container
- getting started
- glossary
- Greenhouse
- hod
- host on demand
- how to
- Java components
- lead manager
- live text
- local
- Lotus Expeditor
- Lotus Notes component advanced development
- Lotus Notes component development in Composite Applications
- Lotus Notes components
- Lotus Notes components
- Lotusphere
- LS09
- match rules
- my first wire
- navigation
- navigators
- new applications
- new user
- new users
- Notes
- Notes 8
- Notes components
- Notes View
- Notes @formulas
- Notes8_5
- NSF-based composite applications
- NSF components
- NSFs
- opening pages
- out-of-the-box components
- overview
- page navigation
- page properties
- pages
- passing context
- PIM components
- plugins
- Portal
- product information
- product wikis
- productivity tools
- properties
- property
- property broker
- property broker editor
- Property Broker Monitor tool
- property to property
- provisioning
- questions
- resources
- roadmap
- running in context
- sample composite application
- samples
- service oriented architecture
- setting component properties
- setting up
- sidebar
- skills
- SOA
- Symphony
- Symphony view component
- toolkit
- tools
- topology peek tool
- troubleshooting
- tutorial
- Tutorials
- uninstalling composite applications
- update site
- updates
- user interface planning
- video
- view
- web container
- web services
- widgets
- wires
- wiring
- wiring properties
- wiring tutorial
- WSDL
- .ca
- @formulas
Go elsewhere
Property Value Editor
![]() |
Advanced users
, Composite Application Editor
, Deploying
, Lotus Notes components
advanced features , CAE , Notes , NSF components , deploying |
Mark Gargan 11/27/2008 |
Mark Gargan 01/22/2009 |
The Property Value Editor is a powerful tool that allows an application developer to make changes to multiple property values at once. A typical use of the the Property Value Editor would be to update URLs when moving an application from a development/test environment to a deployment environment. For example a composite application may be developed using components on a test domino server or from a development updatesite, when the application is moved to a deployment phase all the component URLs would need to updated. Without the Property Value editor each component would need to be updated individually.
This feature uses regular expressions when replacing values. To read more about regular-expression constructs see http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html.
CAUTION: While the Property Value Editor is intend to provide a power tool for updating component properties, replacing property values can break an application so use this feature with care.
Using the Property Value Editor
1. Select Edit > Property Value Editor.
2. In the Filter area, narrow your search scope by choosing either Preference Name contains or Preference Value contains and entering a filter string. Leaving a field blank or entering the wildcard character (*) returns all. The selection area displays the parts of your application you want to search, listed in a hierarchy of application, page, component, property. The property values display on the right. You can only update property values. For example, to update URLs, enter URL in the Property field. Any component that contains a URL preference displays.
Note: If no results are found that match the filter only the root page is displayed.
3. All result that match the filter are selected automatically. Leave as is if you want to replace all selected values. Otherwise, check only those values you want to replace.
4. Enter a regular expression (or literal string) of what you wish to replace and the replacement string, and click Apply. It is prudent to review what is selected in the tree before applying changes. The changes will display in the selection area. If you have searched by Preference Value Contains: and apply changes, the new value may no longer match the filter criteria and if so will no longer be displayed.
5. When you are done making changes, click OK to save your changes or Cancel to roll back all changes since you opened the editor.
Examples for using Property Value Editor
Example 1.
Changing the Initial URL of managed browser components.
In this example there are several Managed browser components on a application. By default they are set to about:blank we will change them to http://www.ibm.com
1. Filter by Preference Name Contains: with initialURL
2. The tree area should now show the any components that a preference that contains initialURL
3. In the Replace Property Value area leav e the Replace field as .+ this is replace anything and everything
the the with field enter http://www.ibm.com
4. Clicking on Apply with apply the changes.
5. Clicking OK will save the changes while clicking cancel will abandon any changes made since the dialog was open.
Example 2. Replacing the change the server of a notes URL
In this scenario we have a new composite application that we wish to move from development to deployment. The composite application contains several new notes components that are located on a test server (testserver) and several other components that have already been deployed (dominoserver1). The components have been deployed to dominoserver2 and the components URL need to be update to reflect this
1. Filter by Preference Value Contains: with Notes://testserver/85257336004CE5D3/CompanyByName?OpenView
2. The tree area should now show all thecomponents that have a preference whos value contains Notes://testserver/
e.g. Notes://testserver/85257336004CE5D3/CompanyByName?OpenView
3. In the Replace Property Value area enter Notes://testserver/ into the Replace field in the with field enter Notes://dominoserver2/
4. Click on Apply to apply the changes and OK to save them.
Some examples of some regular expressions.
| Regular Expression | Description | Example |
| .+ | one or more of any character | |
| http://[\w-._]+/ | A string that starts with http:// followed by one or more alphanumeric charater, '-', '.' and/or '_' followed by '/' | http://www.ibm.com/ but not http://www.ibm.com |
| [A-F0-9]{16} | Any series of numeric characters and/or A,B,C,D,E,F exactly 16 characters long | F2A477C624781375 41745C3C35E6675F477C624 |
| [w]{3}.[\w-_.]+[.com] | Any dot com domain with a www. prefix | www.ibm.com/ie/ http://www.ibm.com |


