The IBM Composite Applications wiki has been launched.
This is a one-stop-shop for information about Composite Applications.
The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
Bring information and collaboration into the context of your daily business processes using composite applications
Matching: o'gorman X
nheidloff 060001WH71 Tags:  expeditor612 conventions o'gorman expeditor611 notes80 tutorials faq samples notes801 5,980 Views
Another new feature coming along in CAE for 8.0.1 is the ability to Undo changes you've made to your applicaton.
For 8.0.1, this feature is only available for NSF based applications. We hope to extend this to Portal based applications in the future.
There are two aspects to this new feature:
1. When you close CAE, you are asked if you want to keep your changes. Selecting "No" will revert the application back to it's original state... when you opened CAE.
2. Edit->Undo. This will undo the last operation performed. Operations are things like: add component, add page, remove component, remove page, modify wiring, modify component properties, etc.
Do you have trouble finding out what wires are in your application?
There is a new feature coming in CAE in Notes 8.0.1 to help you with this.... View All Wires.
It will be launched from a button in the Wiring UI:
When you click the button, it will bring up a new window that contains a tabular view of all wires in the application.......
By hovering over a row in the table, you can get more information about the wire....
Or you can choose to include extra information in the table itself...
Some other features:
If you would like to include the embedded browser in your application, and wire your components to it, you need to define properties that use the same types as the embedded browser component. However, you do not need to define these types from scratch, you can import the types from an existing WSDL file and then define your properties to use those types.
Note: In the Beta version of Notes8, when you choose to "Add locally installed components" from the palette in CAE you are presented with a number of "Browser" components. You should choose the one titled: Managed Browser. This is the browser component that supports wiring. (In the Notes 8.0 release, you will not be see the multiple browser components, just the Managed Browser one.)
You can download the WSDL for the Embedded Browser here: eb.wsdl.
(Please ignore the .jpg extension. Save file locally as eb.wsdl)
To import the types:
You can now select these types from the drop-down list when creating a new property.
Noticed any missing features / components while launching Notes from your Eclipse IDE?
Or noticed that the debug tools are not available even though you've installed them?
This entry explains about how the RCP features & plugins in Notes 8 are broken into locations, and about the extra location where additional features are provisioned.
If you look at the framework directory within your Notes installation directory, you will notice 3 Eclipse locations: eclipse, rcp, and shared.
The eclipse site contains the features & plugins from then Eclipse RCP.
The rcp site contains the features & plugins from the Expeditor platform.
The shared site contains the features & plugins from Notes.
There is a fourth location that is in your workspace: <notes_data>/workspace/Applications
It is into this fourth location that components in Composite Applications generally get provisioned. Features installed using the Application Management UI are also installed to this location.
When you launch Notes 8, it will load the feature & plugins from all four locations, however when you are launching from the Eclipse IDE, if only picks up the three locations in the framework directory by default. This means that anything installed into the Applications location is not available to you.
Eclipse uses link files to link the different sites. These files are located in the framework/eclipse/links directory. You will notice that there are three link files here for the three locations in the framework directory. The launcher for Notes dynamically include the Applications location, but when you launch from your IDE this does not happen.
There are two method to remedy this.
1. Use an Eclipse Target and include the Applications location as an Additional Location in your target.
2. Create an additional link file in framework/eclipse/links directory to point to the Applications location.
My preference is option 2, so I will expand on that one.
- Create a new file in <notes_install>/framework/eclipse/links, called apps.link containing: path=C\:/ibm/notes8/data/workspace/applications
(Update the path to match your Notes install location.)
- In Eclipse, navigate to Windows->Preferences->Target Platform, and click Reload.
If you select "Group plug-ins by location", and then collapse the locations, you should now see the four locations.
When you next launch Notes from your IDE you should now have any components / features that are installed to the Applications location.
(If your Launch Configuration selectively chooses plug-ins to enable while launching, you might need to verify that the new plugins are selected).
Do you have (or want) a component that performs different functions in different circumstances?
There are some features in CAE and Comp Apps to help you with this.
1) Copy components in CAE palette
Right-click on a component the palette, and choose "Copy"
Right-click somewhere else in the palette (or in a different palette) and choose "Paste".
This will create an identical copy of the component on the palette, along with any advanced settings (e.g. preferences) you've applied to the component.
2) Rename your component
Right-click on the component and choose "Rename" to give the component a new name.
At runtime this name is available via the com.ibm.rcp.title preference, so you can set the title of your component appropriately.
3) Apply different settings to the components
Use the Advanced Settings dialog to apply some new preferences to the component to differentiate it from the original.
These settings can then be read by the component at runtime. See this previous entry for more details.