Windows Server AppFabric is an extension of the Application server role on the Microsoft Platform. Windows Server AppFabric offers in-memory, super-fast. This download is available as a part of Microsoft’s training kit for Windows Server AppFabric. The download is available at. This SharePoint tutorial explains, how to resolve the issue Window Server App Fabric: download error which comes while installing.
 
 

Windows Server AppFabric (bit) – Free download and software reviews – CNET Download

VLC Media Player. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Windows Windows. Most Popular. New Releases. Desktop Enhancements. Networking Software. Software Coupons. Windows Server AppFabric 6. Download Now. Clicking on the Download Now Visit Site button above will open a connection to a third-party site.

Just like we set up the Security Configuration for the Windows Server AppFabric Monitoring database, repeat the same steps and use built-in accounts for the persistence database.

The configuration of Windows Server AppFabric provides contextual information to run Windows Server AppFabric services that are responsible for monitoring and hosting services. Windows PowerShell is built on top of Microsoft. NET and offers a task based command-line shell and scripting language. Windows PowerShell has built in commands called Cmdlets pronounced as commandlets. Cmdlets are lightweight commands and typically return a Microsoft. NET Framework object type to the next command in the pipeline.

It should be noted that monitoring and persistence services should be run under accounts with administrative privileges so that they can read and persist events to the preconfigured monitoring and persistence databases.

Once you have finished configuring the Hosting Services as discussed in the preceding recipe, the next task is to configure the Caching Services for AppFabric. Just like in the preceding recipe, we will select a service account that should be part of the administrator group so that it has an administrative access to the caching configuration provider. Once again we will consider a workstation configuration and select a valid local system account. We will see how to setup the Caching Configuration Store Provider.

Run the AppFabric Configuration wizard. Accept the User Account Control UAC dialog, confirming that you will allow this program to make changes to your computer. Under Caching Service Account , click on Change. This will allow you to select the identity for the Caching Service Account.

If your machine is in workstation mode, then you cannot change the service account. Otherwise, you can browse and select a local account that has administrative access to the Caching Configuration store. If you select SQL provider and click on Configure , you will get the following error message:. Your screen will appear as follows:. It should be noted that the File share UNC server share selection wizard will not allow you to create a new file share.

As highlighted in the beginning of the recipe, it is required to have a UNC file share readily available. Under cluster information select New Cluster and click on Next. Configure AppFabric Cache Node by providing a unique port number value numbers must be between and for the Cache port, Cluster port, Arbitration port , and Replication port. The Cluster port enables Cache Cluster formation and Management. The Arbitration port is used to double check if the Cache Host is unavailable.

Arbitration is used when the Cache Host fails. The Replication Host is used to move data between the Cache Hosts.

Replication is used when Cache is configured for High Availability. Your screen should appear similar to the following:. If you are using any third-party non-Microsoft firewall then you will need to manually update the firewall rules. This must be done to allow Windows Server AppFabric to use the ports that were specified during its configuration.

Click on Finish to close the wizard. You have fully configured Windows Server AppFabric. Click on Finish. As the caching service runs under the identity of the provided account, the account must have administrative privileges so that it can access and modify the configuration.

The Windows Server AppFabric Caching Service needs to identify which ports to connect to in order to communicate with the other hosts in the cluster. Once the port numbers are specified, ensure that any software or hardware firewalls are not blocking these ports. As we experienced in this recipe, the Windows Server AppFabric Caching Service is highly configurable and the configuration wizard makes it extremely easy to set up or change the existing configuration.

Now that we have configured Services for AppFabric and all the services are up and running under valid service accounts along with firewall rule definitions, we can now start coding to test and start consuming the caching service. Instead, we can use Client Assemblies to connect to an instance of AppFabric. In this recipe, we will see how to set up a Client Machine that can connect to and communicate with Windows Server AppFabric.

Once we have set up the Client Assemblies, then we can use Visual Studio, for example, to write applications that can use Windows Server AppFabric Caching capabilities. Cache Client, as the name implies, refers to the applications or services that can access and modify cached items by connecting to a configured or specified cache cluster.

Setting up the Client Caching environment is a very simple task; it is just a matter of copying the binaries highlighted at the start of the recipe to a particular location. These binaries can be obtained by installing Windows Server AppFabric on a workstation. You will need the Caching feature installation to get the required Caching binaries. The default location for these assemblies is.

Copy the assemblies mentioned in step 2 to a place where they are available under a known path to your Client application.

To cache-enable an application server, you will need to install the Windows Server AppFabric Caching Assemblies on it. As long as your application installation copies the AppFabric Cache Assemblies and has a valid configuration in place, your application server is Cache enabled. By copying these assemblies on the client machine, we ensure that the client does not need to do a complete installation of Windows Server AppFabric.

Once the Client Assemblies are available, we can write applications that can use AppFabric’s Caching capabilities and connect to the AppFabric Caching cluster. Once Windows Server AppFabric is configured, it is still possible to change its configuration. There could be a number of reasons for changing the configuration of an existing deployment. The following are some of the most common scenarios that would require such changes:.

You can use the Windows Server AppFabric configuration wizard and make the required changes as they are required. In this recipe, we will see how to re-configure Windows Server AppFabric after installation.

You will need an existing instance of AppFabric that has been installed and configured to get started with this recipe. In this recipe, we will learn how to change Windows Server AppFabric configuration after it has been installed on the host OS. To begin, launch the AppFabric Configuration wizard to go through the configuration options on an existing installation of AppFabric to easily select the options that we want to change.

Click on Next at the bottom of the screen to get started with the configuration. Give the wizard a few seconds while it loads the existing configuration. The screen should look as follows:. Once the configuration is loaded, you will notice that the green tick under the monitoring and persistence configurations states that the default monitoring store is registered. We can now go ahead and change the monitoring configuration by selecting Set monitoring configuration and clicking on Change.

By selecting Register AppFabric monitoring store in root web. Config file and is made available to all subsequent websites. The Initialize monitoring store option will create a new database if it does not already exist and it will also initialize the schema and the structure of the database based on the Microsoft SQL Server provider for the AppFabric monitoring site. It should also be noted that if you skip the Register AppFabric monitoring store in root web. We can repeat steps 4, 5, and 6 by selecting Set persistence configuration.

Change the Caching Service account by selecting Change and opting for a relevant account. Change the File share UNC server share by browsing and selecting the appropriate share that we want to store the XML configuration file.

Join an existing cluster as opposed to creating a new one by selecting the Join cluster option, as shown in the following screenshot:. If the configuration already exists, then this caching service instance will become part of an existing cluster.

If you are joining an existing cluster, you will not be able to change the cluster size. It should be noted that the cluster size does not dictate the possible number of machines in the cluster; however, it does optimize the whole cluster based on the size selected. So for example, you can add seven machines to a cluster that is defined as “Small” machines. However, Windows Server AppFabric will optimize the caching configuration based on cluster configuration of machines.

To change port numbers for caching, click on Next and change the values as required. In case of changing port numbers you must ensure that firewall level exceptions have already been defined for the newly selected port numbers. Configuration can be changed in a variety of ways. For example, in this recipe our changes were driven by the Windows Server AppFabric configuration wizard; however, we could have achieved similar results using AppFabric PowerShell commandlets.

We will learn more about PowerShell commandlets in the following chapters. Another possible way to change configuration is to modify the configuration manually. For example, when using the XML provider, we can always go to the file share and modify the ClusterConfig.

Windows Server AppFabric uses providers to abstract the implementation details of its Cache configuration as well as persistence and monitoring stores. In this recipe we used out of the box providers, but configuration storage and management can be further extended to implement a custom provider.

At runtime, Windows Server AppFabric looks up the registered configuration provider. Based on the provider it then accesses a specific configuration store. The configuration store is then used to fetch relevant information for that provider. For example, with the Caching configuration provider, the configuration store will store information such as port numbers, service accounts, and so on.

Similarly, for the persistence and monitoring configuration providers, the configuration store will maintain information relevant to monitoring and persistence stores such as connection strings, for example. There are hundreds of cmdlets and functions available that allow administrators and developers alike to perform day-to-day management tasks on AppFabric. As Caching is one of the biggest features in Windows Server AppFabric, it is no surprise that AppFabric Caching has a dedicated set of PowerShell cmdlets that allow developers and administrators to interact with the distributed Cache environments in an interactive and streamlined manner.

In this recipe, we will look at how to use PowerShell cmdlets to interact with the AppFabric Caching service. Using PowerShell to manage AppFabric Caching introduces a number of useful possibilities, including but not limited to automating build and deployment scenarios, and enabling command line monitoring and troubleshooting. On Windows 7 and Windows Server , you must run Caching Administration Windows PowerShell with administrative privileges, otherwise some commands will not work.

To set the context of the Windows PowerShell session, we will execute the use-CacheCluster command first. Considering that this is being executed on the host computer, we do not need to provide the configuration, as the parameters are extracted from the local computer. Once the context has been set, we will execute the start-CacheCluster command.

This should result in a status that shows that the Caching Service is up and running:. The Start-CacheCluster commandlet starts the caching service on all the servers that are part of the cluster with the lead hosts starting before non-lead hosts.

Once the Caching Service is up and running, we can query it for the caches that are available in this cluster by using the Get-Cache command. This shows that the cluster is up and running and there is a default cache instance running on the cluster. When starting PowerShell sessions and running on a non-host computer, you must provide the -Provider xml or System. Note that Cache services do not automatically start after a system reboot, so the Start-CacheCluster command must be invoked.

We can also use the Start-CacheHost command with HostName and Port parameters to start a particular host in the cluster. We will see much more on each of these PowerShell commands in the following chapters of this book. As long as we know where something wrong, most installation related errors are fairly trivial to fix. Once error s are found, we can look up in MSDN for the error details as well as their corresponding resolutions.

These errors can either be viewed by clicking on the link in the last page of the installation wizard by or by browsing to the file and then opening it with Notepad or your favorite text editor. Search for errors in the text file. Configuration errors are AppFabric specific but descriptive enough to point you in the right direction; providing information that let’s you know the issue is related to network resource, firewalls, and so on.

It is also worth noting that you can see all PowerShell commands that are executed by the wizard logged in this file as well. Troubleshooting configuration errors revolves around going to a relevant log file and finding the error entries and then looking up each error on the corresponding MSDN help page as highlighted in the How to do it When a cache host is rebooted, Windows Server AppFabric does not start the caching services by default.

Windows server appfabric free download

The Windows Server AppFabric Caching Service needs to identify which ports to connect to in order to communicate with the other hosts in the cluster. Once the port numbers are specified, ensure that any software or hardware firewalls are not blocking these ports.

As we experienced in this recipe, the Windows Server AppFabric Caching Service is highly configurable and the configuration wizard makes it extremely easy to set up or change the existing configuration.

Now that we have configured Services for AppFabric and all the services are up and running under valid service accounts along with firewall rule definitions, we can now start coding to test and start consuming the caching service.

Instead, we can use Client Assemblies to connect to an instance of AppFabric. In this recipe, we will see how to set up a Client Machine that can connect to and communicate with Windows Server AppFabric. Once we have set up the Client Assemblies, then we can use Visual Studio, for example, to write applications that can use Windows Server AppFabric Caching capabilities.

Cache Client, as the name implies, refers to the applications or services that can access and modify cached items by connecting to a configured or specified cache cluster. Setting up the Client Caching environment is a very simple task; it is just a matter of copying the binaries highlighted at the start of the recipe to a particular location.

These binaries can be obtained by installing Windows Server AppFabric on a workstation. You will need the Caching feature installation to get the required Caching binaries.

The default location for these assemblies is. Copy the assemblies mentioned in step 2 to a place where they are available under a known path to your Client application.

To cache-enable an application server, you will need to install the Windows Server AppFabric Caching Assemblies on it. As long as your application installation copies the AppFabric Cache Assemblies and has a valid configuration in place, your application server is Cache enabled.

By copying these assemblies on the client machine, we ensure that the client does not need to do a complete installation of Windows Server AppFabric. Once the Client Assemblies are available, we can write applications that can use AppFabric’s Caching capabilities and connect to the AppFabric Caching cluster. Once Windows Server AppFabric is configured, it is still possible to change its configuration.

There could be a number of reasons for changing the configuration of an existing deployment. The following are some of the most common scenarios that would require such changes:. You can use the Windows Server AppFabric configuration wizard and make the required changes as they are required. In this recipe, we will see how to re-configure Windows Server AppFabric after installation.

You will need an existing instance of AppFabric that has been installed and configured to get started with this recipe. In this recipe, we will learn how to change Windows Server AppFabric configuration after it has been installed on the host OS.

To begin, launch the AppFabric Configuration wizard to go through the configuration options on an existing installation of AppFabric to easily select the options that we want to change. Click on Next at the bottom of the screen to get started with the configuration. Give the wizard a few seconds while it loads the existing configuration. The screen should look as follows:.

Once the configuration is loaded, you will notice that the green tick under the monitoring and persistence configurations states that the default monitoring store is registered. We can now go ahead and change the monitoring configuration by selecting Set monitoring configuration and clicking on Change. By selecting Register AppFabric monitoring store in root web. Config file and is made available to all subsequent websites. The Initialize monitoring store option will create a new database if it does not already exist and it will also initialize the schema and the structure of the database based on the Microsoft SQL Server provider for the AppFabric monitoring site.

It should also be noted that if you skip the Register AppFabric monitoring store in root web. We can repeat steps 4, 5, and 6 by selecting Set persistence configuration. Change the Caching Service account by selecting Change and opting for a relevant account. Change the File share UNC server share by browsing and selecting the appropriate share that we want to store the XML configuration file.

Join an existing cluster as opposed to creating a new one by selecting the Join cluster option, as shown in the following screenshot:. If the configuration already exists, then this caching service instance will become part of an existing cluster. If you are joining an existing cluster, you will not be able to change the cluster size. It should be noted that the cluster size does not dictate the possible number of machines in the cluster; however, it does optimize the whole cluster based on the size selected.

So for example, you can add seven machines to a cluster that is defined as “Small” machines. However, Windows Server AppFabric will optimize the caching configuration based on cluster configuration of machines.

To change port numbers for caching, click on Next and change the values as required. In case of changing port numbers you must ensure that firewall level exceptions have already been defined for the newly selected port numbers. Configuration can be changed in a variety of ways. For example, in this recipe our changes were driven by the Windows Server AppFabric configuration wizard; however, we could have achieved similar results using AppFabric PowerShell commandlets.

We will learn more about PowerShell commandlets in the following chapters. Another possible way to change configuration is to modify the configuration manually.

For example, when using the XML provider, we can always go to the file share and modify the ClusterConfig.

Windows Server AppFabric uses providers to abstract the implementation details of its Cache configuration as well as persistence and monitoring stores. In this recipe we used out of the box providers, but configuration storage and management can be further extended to implement a custom provider. At runtime, Windows Server AppFabric looks up the registered configuration provider. Based on the provider it then accesses a specific configuration store. The configuration store is then used to fetch relevant information for that provider.

For example, with the Caching configuration provider, the configuration store will store information such as port numbers, service accounts, and so on. Similarly, for the persistence and monitoring configuration providers, the configuration store will maintain information relevant to monitoring and persistence stores such as connection strings, for example. There are hundreds of cmdlets and functions available that allow administrators and developers alike to perform day-to-day management tasks on AppFabric.

As Caching is one of the biggest features in Windows Server AppFabric, it is no surprise that AppFabric Caching has a dedicated set of PowerShell cmdlets that allow developers and administrators to interact with the distributed Cache environments in an interactive and streamlined manner. In this recipe, we will look at how to use PowerShell cmdlets to interact with the AppFabric Caching service.

Using PowerShell to manage AppFabric Caching introduces a number of useful possibilities, including but not limited to automating build and deployment scenarios, and enabling command line monitoring and troubleshooting.

On Windows 7 and Windows Server , you must run Caching Administration Windows PowerShell with administrative privileges, otherwise some commands will not work.

To set the context of the Windows PowerShell session, we will execute the use-CacheCluster command first. Considering that this is being executed on the host computer, we do not need to provide the configuration, as the parameters are extracted from the local computer.

Once the context has been set, we will execute the start-CacheCluster command. This should result in a status that shows that the Caching Service is up and running:. The Start-CacheCluster commandlet starts the caching service on all the servers that are part of the cluster with the lead hosts starting before non-lead hosts.

Once the Caching Service is up and running, we can query it for the caches that are available in this cluster by using the Get-Cache command.

This shows that the cluster is up and running and there is a default cache instance running on the cluster. When starting PowerShell sessions and running on a non-host computer, you must provide the -Provider xml or System. Note that Cache services do not automatically start after a system reboot, so the Start-CacheCluster command must be invoked. We can also use the Start-CacheHost command with HostName and Port parameters to start a particular host in the cluster.

We will see much more on each of these PowerShell commands in the following chapters of this book. As long as we know where something wrong, most installation related errors are fairly trivial to fix. Once error s are found, we can look up in MSDN for the error details as well as their corresponding resolutions.

These errors can either be viewed by clicking on the link in the last page of the installation wizard by or by browsing to the file and then opening it with Notepad or your favorite text editor. Search for errors in the text file. Configuration errors are AppFabric specific but descriptive enough to point you in the right direction; providing information that let’s you know the issue is related to network resource, firewalls, and so on.

WinRAR bit. VLC Media Player. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat. Clash of Clans. Subway Surfers. TubeMate 3. Google Play. Windows Server AppFabric for Windows 7 x86 32bits OS, it is a set of integrated technologies that make it easier to build, scale and manage Web and composite applications that run on IIS. It provides out-of-the-box capabilities for you to easily build and manage composite applications, including: 1.

Enhanced design and development tools in Visual Studio to build rich composite applications 2. Distributed in-memory application cache to improve application performance. Windows Server AppFabric allows developers to build their next-generation composite applications, and for administrators to host and manage them.