In this article by Munwar Shariff, we will learn how to use Alfresco as a smart document repository. This will include providing automatic version tracking and control, and accessing documents in the Alfresco repository from your web browser, a network drive, FTP, or WebDAV.Read Implementing Document Management in Alfresco 3- part2 in full
The primary focus of implementing workflow is automation of a business process. In this article by Munawar Shariff & Amita Bhandari, we will see the basic, out-of-the-box workflow capabilities of Alfresco and the ways to extend it as per your business requirements.
By the end of this article, you will have learned how to:
- Enable simple workflow for documents
- Create email templates and set email notifications
- Extend workflow to include multiple approval steps
- Implement a complex workflow scenario for document lifecycle management
Read Implementing Workflow in Alfresco 3 in full
In this article by Aaron Winborn, we'll go through the FileField module. This is a useful module if you want to have an easily configured solution, in many situations, there are some benefits from using the FileField module instead. It's light-weight, it's flexible, and it's easy to customize. It may also be easier to add support for players other than the 1PixelOut and XSPF players distributed with Audio.
Additionally, as of this writing, the Drupal 6 version of the Audio module wasn't quite ready for production. But I am confident it will be soon, if not already.
Finally, there may be specific reasons for wanting to choose a FileField solution over the Audio module. Similar to the quandary of whether to use the Image module or Image Field, the most common reason would probably be to allow multiple audio files to be attached to a node, or to allow audio fields to be associated with other types of nodes. (Note that the Audio module is also bundled with the Audio Attach module, which might be a solution for that as well.)Read Audio Fields in Drupal in full
In this article by Hector R. Madrid, we will discuss about the Oracle Wallet Manager. The Oracle Wallet Manager (OWM) is the tool used by Oracle to manage the authentication processes. It is a key tool for managing most of the authentication and security related tasks in an Oracle environment, this includes; authenticating users, providing SSL communication, and configuring the Transparent Data Encryption (TDE) feature, among others. There are two modes to work with the Oracle Wallet, the first one is by using the Java Oracle Wallet Manager console and the second one is by means of the mkwallet command line version, this method is suitable for batch processing. The Wallet is a very sensitive element; there are several ways to store it, not only in its file at the file system level, but also in the registry (for Windows platforms only). It can also be stored in an LDAP compliant directory.Read Oracle Wallet Manager in full
Learning how to figure out why things are going wrong is one of the key aspects of developing software. We call it debugging. While dealing with REST services and clients, things can go wrong and it would help a great deal to know how to find out what is causing the problems.
In this article by Samisa Abeysinghe, we will look into the techniques such as message capturing and analyzing to get to know if things are going fine, and if not, what sort of problems are causing trouble.Read Debugging REST Web Services in full