javascipt

Featured Post

Interesting Features in ECMAScript 6

By: Brent Wodicka

bondiBondi Digital Publishing has relied on AIS for several years to build and enhance it’s Cloud Hosted digital magazine archive platform. Vogue, Rolling Stone, and many other magazines now have a compelling avenue for delivering content to their readers. Both back issues and new and upcoming issues of magazines are provided online in a beautiful HTML5 viewer.

The Bondi Digital Archive has grown, and with that growth new challenges have arisen. Some publishers have come to Bondi with a need to make hundreds or thousands of back issues available online as quickly as possible. However, once the back issues were all scanned, the images and metadata had to be processed before the final digital product was ready. This processing was taking an immense amount of time – sometimes up to several weeks. The publications wanted their back issues available online much more quickly than that. Read More…

javasciptAre you writing a lot of JavaScript as part of your web application? Spending a lot of time debugging that JavaScript? I want to discuss a debugging technique today using that old standby, console.log and overcoming one of its deficiencies.

Using console.log can be useful for printing out application state without interrupting your workflow. Contrast that with using a JavaScript breakpoint where you are forced to break your workflow to check the application state and then resume the execution of your application.

So, now that I’ve refreshed your memory on the upside of console.log over a breakpoint, let’s talk about the downside compared to breakpoints. To add a console.log statement, you have to edit the source code of your application. And editing the source code of your application is an even bigger break in your debugging workflow. You have to go back to the editor, add the log statement, refresh the page, and then go back to where you were. And don’t forget to remove that log statement before you commit your source code.

Well what if you could avoid those limitations? Read More…

Part 4: Load testing the messaging integration style

In this four part series we have been looking at how different application integration styles handle spikes in load. In Part 1 we created and deployed a distributed system that used an RPC-based integration style. Our inventory application communicated with our purchasing application via a web service. In Part 2 we simulated a spike in load and caused the system fail. In Part 3 we updated the architecture from an RPC-based integration style to a messaging-based integration style. In this post, we are going to simulate the same spike in load and see how the messaging-based architecture copes.

Where are we now? We have updated our distributed system to use messaging as the communication mechanism between the applications. We have created an integration test that causes the inventory application to request stock replenishment from the purchasing application and we have created a load test that executes the integration test a thousand times and records the results. We have already tested our previous, RPC-based architecture and seen that it doesn’t hold up when there is more load than the hardware can handle. Read More…

sharepoint 2013 logoI came across an interesting bug while trying to add a user the Administrators of a Search Service Application in SharePoint 2013. When I tried adding the user, and clicking OK, and error is returned: “User does not have permission to perform this action” along with a correlation ID. Further investigation in the ULS logs revealed that the problem was SQL permission related: “The EXECUTE permission was denied on the object ‘proc_MSS_GetConfigurationProperty’, database ‘SPSearch’, schema ‘dbo’.” Additionally performing a search fails and logs the error: “There was an exception in the Database. Please retry your operation and if the problem presists, contact an administrator.” (The error message has a typo too).  Read More…

Microsoft Azure

Please join AIS as presenter Kevin Aenmey discusses the Azure Service Bus as a messaging platform hosted in the cloud.  

Thursday, March 26, 2015 – 12:00 PM EST: REGISTER NOW

Azure Service Bus is a messaging platform hosted in the cloud. It provides different messaging capabilities that allow applications to communicate with each other whether those application are running in Azure or on-premises. The asynchronous messaging patterns enabled by Service Bus allows for convenient load leveling, load balancing and temporal decoupling. This talk will provide an introduction to asynchronous messaging with Azure Service Bus.  We will focus on what it is, why you would want to use it and a brief demonstration on a number of asynchronous messaging patterns implemented with Service Bus.

Register Today! 
Read More…

sharepoint 2013 logoIf you’ve ever had the need to add document management capabilities for your entities in CRM, you already know that CRM 2013 and CRM online rely on SharePoint for this functionality. This out of the box integration point is well documented and available for configuration in the CRM administrative interface. When set up, users can create, upload, view and delete documents in SharePoint locations that correspond to entity instances in CRM.

This post will discuss a different integration point – using search in SharePoint 2013 to expose CRM entity data. When setup properly, SharePoint 2013 can provide a robust, enterprise level search capability that can be tailored to your needs. Also, it seems to fill a current functionality gap in CRM that often requires a third party tool. Granted, you will need SharePoint 2013 Enterprise to realize this setup, but if this is available to you there should be no need to look anywhere else for search. Read More…

A Primer on Pattern Libraries

chimp(1)For many, developing and delivering the front-end of a website or application is often centered on the development of pages within the project. But with that approach, it doesn’t take very long for your CSS file(s) to become overgrown and difficult to maintain. Before you know it rules are duplicated, important tags are cluttering declarations and regression issues are flooding the bug list. It can go from bad to frustrating pretty quickly.

So what’s a Front-End Dev to do? Instead of focusing on the development of elements for each page, shift your focus and consider the entire project, building components that can easily be reused throughout the site or application. And that’s where Pattern Libraries step in: They provide a structured visual reference that presents and organizes the components of the project, streamlines development and helps deliver a cohesive, maintainable product.

Read More…

MicrosoftAzure

Join Microsoft and AIS to learn how Azure Government Cloud can help Justice & Public Safety officials quickly respond to events at scale as needed.
 


The cloud platform designed to meet U.S. government demands Azure Government delivers cloud speed, scale, and economics while addressing the security and compliance needs of U.S. federal agencies including the Department of Defense, plus state and local governments and their solution providers. Azure Government offers physical and network isolation from non-U.S. government deployments and requires specialized personnel screening. Azure Government will address government regulatory and compliance requirements such as FedRAMP, CJIS, and HIPAA.

When local, state or federal authorities respond to criminal acts, they seek to quickly collect vast amount of inputs from the public.  This input can be in the form of tips, photos, videos or any untold observations.  Agencies need the capability to surge their IT tools and applications to collect the data, store it, and run big data analysis tools against the collected content to harvest information.

Register now for an exclusive Microsoft & AIS webinar to learn how you can:

  • Through a few clicks publish internet or extranet facing web or SharePoint site to organize with first responders to an incident or catastrophe
  • Provide a cost effective approach to development on larger scale environments
  • Extend the On-Prem footprint without exposing critical data
  • Reduce the burden of implementing back-up and disaster recovery for your applications.

RSVP TODAY!

sharepoint 2013 logoRecently, I encountered an issue with SharePoint 2013 search crawls where .pdf files smaller than 1 MB reported a warning: “The item has been truncated in the index because it exceeds the maximum size”. The default MaxDownLoadSize for documents in SharePoint is 64MB, which was more than enough the handle these relatively small .pdf files.

After I reached out to some co-workers; one suggested that the error might be a false-positive and the entire document had been crawled. I tested this by first searching for words at the end of the document and no matches were found; this would be expected if it were truncated. Next, I tried searching for text in the middle of the document, no matches were found either. I thought it must have truncated a lot of text and tried searching for text contained at the very beginning of the document. No results were found! So when the warning said it truncated the item, it had truncated the whole document. Read More…