I get two results, the first is from the BCS and the second item is from the JDBC connector. I wonder why the teaser description is different between the two? The BCS also has a different icon due to search resolving the JDBC item target as a folder.
Thanks to profile pages, I can actually click the BCS result which takes me to the profile page for the product.
This is one area which would require a bit of extra work and development if you go with the JDBC connector approach.
Finally, we want to map some search properties. The managed properties from the previous demo are still setup, so I'll map the new BCS crawl properties to these same managed properties.
Now when you are in the FAST Query Search Service Application, don't click on the Metadata properties link in the left menu, 'these aren't the search properties you're looking for' /waveshand.
If you mess with property mappings in there you won't see your BCS properties, instead click on the FAST Search Administration link.
Then click on the Managed Properties link.
Click on Crawled property categories
You should notice the Business Data category with a larger number of properties, click the Business Data link.
There's a list of our crawl properties!
You can map crawled properties through to managed properties through here too.
After mapping all the crawled properties to managed properties, perform a full crawl.
Now retest the same search
Note the refiner counts have all incremented compared to the previous test search, so the property mappings and refiners are now setup, it's as easy as that!
Thanks for reading! I've got one more post to go for this series, I'll perform a closer comparison of the pros and cons of the the JDBC Connector and BCS Connector and why you might use either depending on your requirements and priorities.