Since writing An Introduction to WapSnap the ALT-Invest team has made good progress in the current prototype. Once a few more areas get solidified and the application is installable it will be moving to the Alpha phase and made available to developers interested in providing thoughts and feature requests.
For this installment I wanted to highlight two sections of the product. The first being the snapshot options and the second being the built in SugarCRM tools area.
The image below is a row from the Instances section of the product that shows what application instances have been added to WapSnap. The first three columns from left to right are Instance Name, Instance File Path, and Instance Database. These column show the data that is used by WapSnap in order to know where to pull data from when executing a snapshot.
The 5 images are where the functionality of WapSnap starts. In the application you can hover above any button and get a bubble with a description. The buttons from left to right are Snapshot files and database, Snapshot Database, Snapshot Files, List Instances, and Delete. By browsing to list instances you can select the instances and start the comparison.
Snapshoting the filesystem will make a full backup of the files and hash them for later comparison. Taking a snapshot of the database provides a table by table backup of the database along with table hashes for comparison. The table by table breakdown will allow WapSnap to quickly detect changes in and compare single tables including there structure and or the data within.
One new section that was very recently added was the tools section. Most developers that work with specific software packages often end up writing tools and scripts that are used daily to speed up development, troubleshooting, or other tasks. In the future we would like to give them the ability to add in their own tools but for now the WapSnap team will be providing them. The first tool is the SugarCRM SOAP Browser.
With the WSDL browser you can quickly connect to a SugarCRM instance and get the modules available for integration via SOAP. Once you click Get WSDL you will be provided the list of modules. When a module is clicked you are provided the available fields for that module. We have found that the WSDL browser makes it easier to identify available sections in SugarCRM to integrate with and we hope that you discover the same.
We plan on adding more tools as we find things that are helpful to other developers. So please comment and let us know what features or tools can help streamline your efforts.
- No public Twitter messages.