We have combined our Digital Experience Products Support Blogs with our Application Integration Middleware Support Blog. You will find new content for the DX suite of products at Application Integration Middleware Support Blog. Existing blog entries for DX will remain on this blog since there is a wealth of great information here, but be sure to follow us at our new location so you will be up-to-date on new content. Update your bookmarks and rss feeds and check us out at our new space! You can also find information on that blog about many of the other products in our middleware portfolio.
IBM Web Experience Factory Blog
Anthony Whelan (IBM) 31000066QG 2.626 Visualizações
Using Web Experience Factory as a data service provider for Script Portlet and WEF single page applications
gsager 060000WU3G 3.480 Visualizações
We've now posted an updated version of the Script Application builder samples as open source, using the OpenNTF repository. It's available here
gsager 060000WU3G Marcações:  wizard jquery openntf single_page_app builders 4.457 Visualizações
But what is WEF great at? Taking a pattern and automating the repetition of that pattern. So we created a wizard. Which has been added to our OpenNTF offering. This wizard allows to create a new portlet based on an existing application or a blank application for your creation. The wizard asks if you want the model to be a portlet, if you want to include WEF services that are available from an existing service provider and if you want to create a new application or reference an existing one as is. If you choose a new one it asks which libraries you plan to use what application template you want to use and it creates a new model that is available for your use. If you say you want to reference an existing HTML file, you are then asked if it is one that is currently in the project or you have a zip file that contains the application. If it is an existing file then you select the file and the model is created for you. If you choose the zip file you are asked to choose the zip file. The chooser is limited to files that are already in the project by default, but there is a button that allows you to add a file to the project. You can use this to reference zip files that you have downloaded or received from other places. There is also an option to delete the referenced zip file after the wizard has extracted the files into your project. There is also a convert any templating check box that is included to help you convert your applications that need this as they are imported. The most common issue we have run into so far is the default ERB templating that underscore.js supports. So the defaults for the conversion fields are set to convert the
ruthspeaks 2700006S3X Marcações:  david-wilkerson portlets ldap wcm puma wef davalen was rad portal 3.799 Visualizações
IBM Web Content Manager (WCM) and portlet developers can benefit from a sandbox where the Lightweight Directory Access Protocol (LDAP) configuration matches that of their production environment. This is especially true when the LDAP schema of a production system has been extended. This article explains why and how to implement an enhanced LDAP configuration on a sandbox portal environment.
Read full article at: http://www.dzone.com/links/r/improve_users_digital_experience_by_extending_the.html
Over the last couple of years developer Adam Kewley has had the need to create a Dojo Form Dialog in IBM Web Experience Factory (WEF) that interacts with the end user. The dialog is expected to update itself without refreshing the entire page. By utilizing custom refresh features within WEF you can construct a dialog that will behave more like a popup window.
Read the blog article and download the sample here.
Jonathan Booth 060000XRMC 3.774 Visualizações
Going forward we expect to use this open source OpenNTF approach for publishing sample builders or other reusable extensions for WEF, instead of posting them on the WEF wiki as we did in the past. For posting "how to" examples of techniques we will continue to use the WEF wiki, since there is already a large body of samples there (around 150 at my count!).
Across the wider Portal / Digital Experience team, we will also be using the OpenNTF repository to publish samples of many different types. For example, there is a new set of Script Portlet samples posted there, and going forward we expect to post Portal theme samples, WCM samples and plugins, and other samples and extensions. We are also working on creating a "mini-site" on developerWorks for accessing these samples and extensions.
For any of these OpenNTF posts, you can download the package from the OpenNTF project page and you can click the "Source Control" link to access the source code on Github. And we'd love for you to get involved. You can post feature requests, report defects, and take part in discussions. If you are interested in posting your own samples or extensions as open source (possible based on something we've posted), for WEF or for any part of Portal, this OpenNTF page has information about how you can contribute: http://openntf.org/main.nsf/page.xsp?name=Get_Involved
New samples, articles, and builder for using jQuery and other script libraries with Web Experience Factory
JQuery and other JS-based libraries are getting used more and more for application development across the industry, and there are now a huge number of open source and other script libraries available that support a wide range of features. We increasingly see Web Experience Factory (WEF) customers using these libraries in their WEF applications. To support this trend, we've just posted a series of articles and samples on using jQuery and other JS libraries, along with a "Script Application" builder that you can download.
By combining WEF with jQuery or other scripting libraries you can:
The new articles and samples show a few different scenarios for using WEF with script libraries. They show how you can do this using standard WEF builders, and then they show how the Script Application builder can make things simpler. The Script Application builder automates a common pattern for building script-based applications:
Using WEF and the Script Application builder, you supply the application JS/HTML, specify the libraries you want to use, and then the portlet or web application is generated for you. For access to data and services, you can reference a WEF Service Provider model and have all of its operations automatically available to your JS code via REST/JSON.
We expect to continue posting additional samples and downloadable tools related to building script-based applications and using script libraries with WEF. There are a lot of different potential scenarios for using WEF's model-based code generation with client script-based applications. If there are specific scenarios that you are interested in, we'd love to hear about them, by adding comments here, posting in the WEF forum, or email.
Here's a list of the recently posted articles and downloadable code, all available on the WEF wiki:
One of the things about WEF, as a development tool, is its friendliness to plugging in custom Java code. And so you know the basic mechanics but people don’t talk a lot about the strategy of how to organize the LJOs that you do create. As you might imagine, there is value in putting a little thought into this, and the following ideas have evolved into a pretty useful strategy.
by Kevin Wilmeth
One of the things we love about IBM Web Experience Factory (WEF), as a development tool, is its friendliness to plugging in custom Java code. And by this we mean optionally plugging in code, only where it is truly needed, not being covered natively by the buider set. You can do this in…a lot of places, including places people wouldn’t necessarily even think to look. (Ironically, the full extent of this capability often eludes the highly experienced Java programmer, who may be mentally wired in to a different way of organizing code, and not intuitively “see” how WEF presents itself for such extension.)
And so we have the humble “Ell Jay Oh” as part of the toolkit—we teach its basic mechanics within the first five days of training—but we don’t talk a lot about the strategy of how to organize the LJOs that you do create. As you might imagine, there is value in putting a little thought into this, and the following ideas have evolved into a pretty useful strategy that I like more the more I use it.
LJO layers that work together
The big inspiration for my strategy came some years ago now, when the Domino builder set first became available and I worked on a number of projects that needed it. As a longtime Domino developer before I discovered the Factory, I understood that really getting value out of Domino meant going beyond (way beyond) the limited capacity of the builder set. And so lots of core Domino functions wound up as Java methods in LJOs. Enough so, that I had to do something to organize them!
At some point, it dawned on me to look at my LJOs in layers, much like you’d think of SOA layers. It turns out that there are two very clear separation points that you can lean on to do this: IXml, and WebAppAccess. This implies three layers of LJOs in your project architecture.
Continue reading: http://dzone.com/Zf6w
ruthspeaks 2700006S3X Marcações:  development wef portal davalen technical code java adam-kewley 4.742 Visualizações
Adam Kewley walks us through how to implement your own portlet page tracker which will not only be able to tell when page changed, but also track whether or not a portlet has registered this page change.
by Adam Kewley
Once in a while during product development we run into scenarios where we need to extend the functionality of IBM Web Experience Factory (WEF) & IBM WebSphere Portal above and beyond what’s supported out of the box. The product goes a long way to make things easier to develop with but it’s impossible (and impractical) to expect it to cover every scenario. Fortunately we can usually rely on custom API and sample workarounds to get us through. This article will discuss one such scenario: Tracking Portal Page states with WEF.
In general a portlet isn’t supposed to know (or care) which page it is placed on. It also shouldn’t worry which page the user was on previously. Due to this construct, it’s not always easy to tell when a portlet is being reloaded or when it’s processing a request from a form action.
In some instances however, a project may require a portlet to refresh itself when a user navigates back to that page. A client may wish that an input form resets itself despite what the JSR specification may state. IBM provides a few API classes that expose the page structure. We’ve used them in the past to get the unique page name as well as generate a portal navigation menu inside of a portlet. In this segment we will discuss how to implement your own portlet page tracker which will not only be able to tell when page changed, but also track whether or not a portlet has registered this page change.
The WebSphere Portal API provides the ModelUtil and NavigationNode classes to gain access to the page models within the portal. Using the following sample code, we can obtain the unique name of the current portal page:
NiharT 120000Q88P 3.167 Visualizações
The recent conference (workshop) on Social interaction patterns, exceptional digital experiences has been good source of information. Take a look at this link for further information - https://www.ibmdw.net/social/2013/11/14/webinar-replay-technology-deliver-exceptional-social-digital-experiences
This Webinar also covered integrating web experience factory, Social Business toolkit and multi-channel feature pack for developing social integration using high level wrappers.
AdamG 110000672C 2.868 Visualizações
tom_be 270006P2EP 4.197 Visualizações
How to Integrate Bootstrap with Web Experience Factory for an Exceptional UI Experience
This is a short blog that describes a project I created on Github that contains a WEF Theme showing how to integrate WEF with Bootstrap. This includes the theme file, data definition, html template, DSUI base pages, and a sample model. The theme gives you basic DSUI functionality for list, details, and edits pages. Currently the Bootstrap css and jQuery are pulled in from a CDN.
This is just the initial version, and there is plenty of work to be done such as adding Bootstrap specific builders to fully leverage its features.
Download the attached wef_bootstrap.zip or fork the project and build it from source. To build from source you will need to run 'ant' from the project folder.
Once you have the wef_bootstrap.zip file use the Import > Web Experience Factory Archive to add to an existing project. Then run the provided sample DSUI consumer model (models/bootstrap/OrdersBootstrapSample.model)
If you would like to contribute you can clone this repo, and then submit a pull request for bug fixes or features.
Orders Sample Pages
This follow are the list,details, and edit page from the provided sample.
Exceptional Shopping Experience - Using Web Experience Factory to integrate WebSphere Commerce and WebSphere Portal
Check this cool article out by Joseph George - Exceptional Digital Shopping Experience (xDSx) - Enabling Omni-Channel shopping Experience with WebSphere Commerce and WebSphere Portal - click herePresentation on this @ ASEAN Tech Talk http://www.slideshare.net/josephgeorgek/ibm-x-dx-omnichannel-commerce-experience
AdamG 110000672C Marcações:  websphere-portal digital portlet experience web factory mobile wef mobile-development web-experience-factory mobilefirst 5.005 Visualizações
Here's a quick presentation and demo (video) of what's new with the Multi-Channel Feature Pack 2 for Web Experience Factory 8.0
Jonathan Booth 060000XRMC 7.541 Visualizações
I'm very happy to announce the availability of the Multi-Channel Feature Pack 2 for Web Experience Factory 8.0. This is our second Feature Pack release of 2013, and it continues our focus on the key themes of developer productivity and support for mobile and multi-channel applications. We're using these Feature Pack catalog releases to get new tools that support these themes into the hands of developers quickly.
Here are the key features in this release:
This picture shows a few screenshots of some sample banking applications built with this Feature Pack.
This Feature Pack requires the latest Web Experience Factory Fixpack 126.96.36.199, and some of the enhancements listed above are part of that Fixpack.
Here are some key links for this Feature Pack. We hope you download the Fixpack and Feature Pack and try this all out!