Just as we like to organize everything in life into containers, UAG also does the same. As a user of Microsoft products, you are probably used to files or programs that are grouped together within folders and which are stored on hard drives (or hard drive partitions). With UAG, there's one little difference, the primary organizational units are called "Trunks", and in those we create (or "publish") applications, and we can also group them in folders too.
In the previous article by Erez Ben-Ari and Ran Dolev, authors of the book Microsoft Forefront UAG 2010 Administrator's Handbook, we discussed UAG's building blocks—Trunks and Applications.
In this article we will see how to prepare, create and publish an HTTPS Trunk.Read Microsoft Forefront UAG: Preparing, Creating, and Publishing an HTTPS Trunk in full
The setup and configuration of the base server components will essentially create a functioning Dynamics AX system without Business Intelligence, Workflow, or the Enterprise Portal. Once you have installed and configured the base server components you can access the Application Object Server (AOS).
This article by Marco Carvalho, author of Microsoft Dynamics AX 2009 Administration, will not just cover the basic installation of the base server components from the beginning to the end but also advanced procedures that cover just about any scenario sequentially. Specifically in this article, we will cover:
- Installing the Dynamics AX database
- Installing the Dynamics AX Application files directory
- Installing the Application Object Server (AOS)
Your chance to win 1 year's free subscription to PacktLib every Tuesday!
To enter simply identify which IBM Book the jigsaw piece has been taken from
Correct answers will then be entered into a weekly raffle to win 1 year's subscription to PacktLib worth $220
Coming up to its 100th Anniversary, IBM isn't the only one celebrating this year...
On Tuesday 22nd February Packt has published an unprecedented three new IBM books in one day
To celebrate this occassion Packt has a special offer on all IBM print books
BUY ANY IBM PRINT BOOK AND RECEIVE A 20% DISCOUNT THROUGHOUT FEBRUARY
In the previous article, Setup and Configuration of the Workflow for Microsoft Dynamics AX 2009 Administration, we have covered:
- Prerequisites for Workflow
- Installing Workflow
- Set up and Configure Workflow
This article, by Marco Carvalho, author of Microsoft Dynamics AX 2009 Administration, is a continuation of the previous article in which we will have a look at testing the workflows.Read Testing Workflows for Microsoft Dynamics AX 2009 Administration in full
The workflow system in Dynamics AX 2009 has been completely redesigned. In short, it is a web application that implements the Windows Workflow Foundation (WF) framework. Windows Workflow Foundation has been part of the Microsoft .NET Framework instance since version 3.0. If you have had experience setting up and defining custom workflow configurations in Microsoft SharePoint, then you will be familiar with the same terminology and interface.
A batch process must also be available to process Workflow events in Dynamics AX. The purpose of the batch process is to communicate the Workflow tasks generated in Dynamics AX to the Workflow web service. Additionally, the batch process also generates appropriate messages.
In this article, by Marco Carvalho, author of Microsoft Dynamics AX 2009 Administration, we will specifically cover:
- The prerequisites required for Workflow
- How to install Workflow
- How to appropriately set up and configure Workflow
- Testing Workflow
In this article by Chandru Shankar and Vincent Bellefroid, authors of Microsoft Dynamics Sure Step, we will cover Sure Step's approach to upgrading Microsoft Dynamics solutions. The following topics will be covered:
- Beginning with the Upgrade Assessment to determine the scope and components of the existing solution that need to be upgraded to the current product release
- Determining if the upgrade approach is a Technical Upgrade, or if additional functionality is to be delivered as part of a Functional Upgrade
- Delivering the upgrade using the Sure Step Upgrade Project Type
- Implementing additional functionality to an existing solution
In this article, you will get an introduction to Windows domains, domain users, and SQL Server security. This will make clear and enable you to understand how the SQL Server Security mechanism works and how tightly it is integrated with the Windows domain.
In this article, by Hemantgiri Goswami, author of Microsoft SQL Server 2008 High Availability, we will learn about most important terms of Windows Servers and SQL Server, which will help us understand clustering in Windows Server as well as SQL server. We will learn about:
- What a Windows domain is and what domain users are
- Various authentication modes in Windows Server
- Authentication modes in SQL Server
- Fixed server and fixed database roles in SQL Server
- What clustering is
- What is new in SQL Server 2008
- How clustering works
- Different types of clustering in SQL Server
- Types of Quorum
- Public and private networks
Just as we like to organize everything in life into containers, UAG also does the same. The primary organizational units in UAG are called "trunks", and in those we create (or "publish") applications, and we can also group them in folders too.
In this article by Erez Ben-Ari and Ran Dolev, authors of the book Microsoft Forefront UAG 2010 Administrator's Handbook, we will take a look at:
- Trunks and applications and their types
- URL signing and how does it work
- Designing your trunks, applications, and nesting
- DNS name resolution