Archive for February, 2006

Auto vCard is public

Share

The Auto vCard functionality I created a while back is now public on the App Exchange. I encourage feedback on it and how it could be improved. Click the image below to visit the page on the App Exchange.

app_exchange_button_detail.gif

Comments (2) comments feed

Gmail / Salesforce.com Integration

Thumbware.com has another integration between a popular web tool and Salesforce.com. First was del.icio.us and now gmail. Check it out at http://gmail.thumbware.com/

Comments (2) comments feed

Relational Junction for Salesforce

Company: Sesame Software (website)
Product: Relational Junction for Salesforce
On App Exchange
5star.png

I was recently introduced to the Relational Junction for Salesforce product by Sesame Software. Per their site’s product page,

Relational Junction for Salesforce simplifies legacy data migration, integration and reporting by creating and synchronizing a local data warehouse that is a perfect mirror of your Salesforce.com site. This Oracle, SQL Server, MySQL, DB2, or Sybase database includes all custom objects and fields, including long text and attachments. No programming is required, and the database schema is always in sync with your Salesforce site.

thumb-rj4salesforce.jpg

I was given a temporary license to play around with the product and I have to say I am quite impressed. I am running Windows XP and used a local MySQL database for my replica database. I was able to get a replica created locally in about 10 – 15 minutes. I spent another 30 minutes learning about its intricacies and was able get my replica tweaked just the way I wanted.

The biggest thing that sets this product apart is its ability to easily send data back to Salesforce.com. It lets companies have their developers focus on interacting with the DBMS of choice (Oracle, MySQL, SQL Server, etc.). Inserts/Updates made in the replica database are sent back to Salesforce.com in the next SetUpdated command. This works for standard and custom objects. The Relational Junction for Salesforce scripts do the work of interacting with the Sforce API, leaving developers to focus on the replica database. Another nice thing is that DELETES made in Salesforce.com are not deleted in the replica. Rather, they are marked as having been deleted.

The process of setting it up was simple (a PDF they provide explains what you need to do):

  1. Unzip the files into a new directory. “c:\rj4salesforce” is the recommended location in order which minimizes the amount of editing required in the config files. There is no install program.
  2. Edit the connection properties file with info on connecting to Salesforce.com and to your local database. There is also a command for encrypting the password in the file.
  3. Edit the upload.config and download.config files to document the objects that should be included in the download from Salesforce.com to the local database and the objects included in the upload of changes back to Salesforce.com.
  4. Run a GetAllGlobal command to get your Salesforce.com database replicated locally. Alternatively, you can run GetSchemaGlobal to just get the schema.
  5. From there, you can run all kinds of commands like GetUpdated on specific objects to get changes from Salesforce, GetUpdatedGlobal to get all changes for all objects in your download.config file, SetUpdated on specific objects to send changes back to Salesforce, etc.

Relational Junction for Salesforce definitely practices the Keep It Simple philosophy. There is no user interface for it. All commands are run via command line. The programs are written in Java, so it is cross-platform, and they provide BAT files for Windows execution and files for Unix execution.

The documentation includes sample scripts, best practices and an example approach to use the product for converting legacy data to Salesforce.

If you are looking to integrate your Salesforce.com database with multiple datasources and are hesitant to train a large group of developers on the Sforce API, Relational Junction for Salesforce is a good option for handling the work with Sforce, letting your team focus on interacting with the databases they are used to.

Sesame Software also makes an ETL Manager product to manage the loads between non-Salesforce.com databases. I did not look at that product, but you learn about it here.

Comments (0) comments feed

Salesforce.com / del.icio.us integration at Thumbware.com

Thumbware.com has created a cool little integration between Salesforce.com and del.icio.us. Using a “bookmarklet” in your browser, you can easily associate external links to your Salesforce.com data. This allows your users to later view related links to your Contacts, for example. The demo shows it being related to Contacts, but it appears that you can use this functionality against any object.

Check it out at http://bookmark.thumbware.com/.

Using del.icio.us and the bookmarklet maintains a user’s productivity by allowing them to save the information without having to leave the page they are on to visit del.icio.us and/or Salesforce.com. Great job to Ian at Thumbware.com!

Comments (0) comments feed

System Status Page

thumb-SFDC_Status_Page.png

As you might have read about by now, Salesforce.com has made their system status page public. It is located here. I think it is great that they are doing this and it is very interesting to see this information.

Across the top, you see the current status. Each server (AP, EMEA, NA1 and SSL (used for PE edition only, i think)) is listed and a red/yellow/green status indicator is there telling you the system status. I would expect, should the status be yellow or red, that there would be an explanation of the problem. It will be interesting to see how they handle this during actual outages. Will the explanation be there in real-time or will those be delivered after the fact? Ideally, there will not only be explanation on the problem, but information on which parts of the application are down (API vs. GUI) and the expected time to come back online.

Then they show historical status. As you can see in the picture, clicking on the red status from 02/09 on NA1, they give a detailed explanation of the problem that occurred. Also interesting in the historical section are the number of transactions and avg. speed. It gives some appreciation as to the size of the application and what they are dealing with over there. Kind of makes you wish that NA2, NA3, NA4, etc. all existed for failover purposes.

Comments (0) comments feed

« Previous entries