Client-Side Endpoint Protection Tasks in Microsoft SCEP 2012

In this article by Andrew Plue, author of Microsoft System Center 2012 Endpoint Protection Cookbook, we will cover:

• Locating and interrupting client-side SCEP logs
• Performing manual definition updates and checking definition version
• Manually editing local SCEP policy using the user interface
• Utilizing MpCmdRun.exe

WPF 4.5 Application and Windows

Any attempt at mastering a technology, any technology, requires a good understanding of its foundations. This understanding makes it possible to grasp the more complex aspects of that technology; Windows Presentation Foundation ( WPF) is no different. In this article, we'll take a broader look at WPF's application model, including the use of windows within an application.

In this article by Pavel Yosifovich, author of Windows Presentation Foundation 4.5 Cookbook, we will cover:

• Creating a window
• Creating a dialog box
• Using the common dialog boxes
• Creating ownership between windows
• Creating a custom shaped window
• Creating a single instance application
• Handling an unhandled exception

Management of SOA Composite Applications

Developers typically create composite applications or simply composites that are packaged into single, deployable JAR files. These applications can contain any number of service components that include BPEL or BPMN processes, Mediator services, human tasks and workflows, and business rules. Composites include logic and code that form the foundation of SOA-based integrations. Though the design and development of composites are not the ultimate responsibility of the Oracle SOA Suite 11g administrator, the deployment, monitoring, and management of them are.

In this article, the authors Ahmed Aboulnaga and Arun Pareek of the book Oracle SOA Suite 11g Administrator's Handbook will discuss the concepts that enable you to manage these composites, and cover the following areas in more detail:

• Managing composite lifecycles
• Structuring composite deployments with partitions
• Setting up ant for automated composite build management
• Promoting code, using configuration plans
• Understanding and configuring composite audit levels

Publishing the project in various formats using Adobe Captivate 6

In this article by Damien Bruyndonckx, author of Mastering Adobe Captivate 6, we will focus on making the project available to the outside world by publishing it in various formats.

Publishing the movie is the process by which we make our Captivate projects available to the outside world. Most of the time, we'll publish our movies in the Adobe Flash format or in the HTML5 format so that any student can enjoy the content of our online course across devices. However, Captivate can also publish the movie in many other formats

Publishing

So far, we have been working in a .cptx file, which is the default native file type of Captivate. The .cptx file format is great when creating and designing our projects, but it has two major disadvantages:

• It can become very large. Consequently, it is diffcult for us to upload the file on a website and for the student to download and view it.
• Opening a .cptx file requires Captivate to be installed on the computer system.

Publishing a Captivate movie is converting (the proper word is Compiling) the .cptx file to a format that can be easily downloaded and viewed by our students. The primary format to publish our projects is the .swf format . swf (pronounced swif) stands for ShockWave Flash. It is the file format used by the free Adobe Flash player plugin installed in more than 98 percent of the computers connected to the Internet. It has two advantages as compared to the .cptx file:

• A .swf file is usually much lighter than its .cptx counterpart, making it much easier to upload and download across the Internet.
• Any browser equipped with the free Adobe Flash plugin is able to open and play the .swf file. This makes it incredibly easy to deploy our Captivate courses.

That being said, the .swf format has some major disadvantages:

• It requires the Adobe Flash Player plugin to be installed. If, for whatever reason, the plugin is not available, the .swf file cannot be played back.
• There is no more Flash Player plugin available for mobile devices. Consequently, a .swf file cannot be played back on a Smartphone or on a Tablet.

That's why other publishing formats are available in Captivate. In Captivate 6, the most effective alternative to the .swf format is to publish the project in HTML5. When published to HTML5, the project can be played back in any modern browser without the need for an extra plugin. HTML5-enabled projects can also be played back on mobile devices including the iPhone, iPad, and iPod touch! HTML5 also has its caveats. At the time of this writing, (June 2012) HTML5 is still under development. Consequently, some features of Captivate are not yet supported in HTML5.

In this article, we will explore and discuss the various publishing options at our disposal in Captivate.