Create Pub/Sub Messaging Cache
This section will demonstrate how you can create a Pub/Sub Messaging cache through the NCache Management Center and Command Line Tools.
Clustered Pub/Sub Messaging Cache
A cache cluster is a set of interconnected server nodes forming a cluster of servers that behave as a single cache unit from the outside. Here is how you can create a clustered Pub/Sub Messaging cache.
Using the NCache Management Center
Launch the NCache Management Center by browsing to http://localhost:8251 or
<server-ip>:8251
on Windows and Linux.In the left navigation bar, click on Clustered Caches. This opens up the Clustered Caches page at
<server-ip>:8251/ClusteredCaches/
.To create a new Pub/Sub Messaging cache, click on New.
- From the In-Memory Store Type dropdown menu, select Pub/Sub Messaging and specify the name of your cache. Select JSON or Binary from the Serialization dropdown menu as per your requirement. Click Next.
Warning
If a cache with the specified name already exists, you are prompted with an error message.
Note
It is recommended that you use JSON serialization if you are using ASP.NET 5.0 and above. For more details click here.
- Select the caching topology and any advanced options like Operation Timeout and Statistic Replication Interval. Click Next.
- Specify the Maximum Size of the cache, if required. You can also add cache nodes to the cluster by specifying the node IP address and clicking on the Add Node button. To add more nodes, click the Add Node button. Click Next once all the required nodes are added.
Warning
If a node is already registered on that cache, notification is prompted.
- Change the Cluster Port and Port Range if required. Click Next.
On Advanced Options page, you can configure the following settings:
You can change the Default Priority of eviction from the dropdown list.
You can also change the Eviction percentage; items will be evicted from the cache using this percentage value if eviction is enabled.
You can change the Clean interval value. The default is 15 seconds.
This cache can be started automatically upon the completion of this process if you have checked the Start this cache on Finish checkbox on this dialog box.
You can make the cache start automatically after service restart by checking the checkbox Auto start this cache on service startup.
- Click Finish. The created cache will appear on the Clustered Caches page with the server nodes and their status. A success notification will be received in the notification panel.
Using Command Line Tools
The New-Cache cmdlet enables the user to create a new cache on one or more server nodes.
This command creates a Pub/Sub Messaging cache named demoClusteredCache of Partitioned topology of size 1024MB on server nodes 20.200.20.40 and 20.200.20.39.
New-Cache demoClusteredCache -InMemoryStoreType PubSubMessaging -Server "20.200.20.40, 20.200.20.39" -Size 1024 -Topology Partitioned
Local Pub/Sub Messaging Cache
A local Pub/Sub Messaging cache can be created in the following ways
Using the NCache Management Center
Launch the NCache Management Center by browsing to http://localhost:8251 or
<server-ip>:8251
on Windows and Linux.In the left navigation bar, click on Local Caches. This opens up the Local Caches page at
<server-ip>:8251/LocalCaches/
. The page shows any existing local caches on your machine and additional details like Server and Server Platform.To create a new local cache, click on New.
- Specify the Server Node IP / Name and click Next.
- Specify the In-Memory Store Type as Pub/Sub Messaging from the dropdown menu. Afterwards, specify the Name, Isolation Level, and Serialization (Binary or JSON) of your cache. Click Next.
Warning
If a cache already exists against the Name specified, you are prompted with an error message.
Note
It is recommended that you use JSON serialization if you are using ASP.NET 5.0 and above. For more details click here.
- Change the cache size if required and click Next.
On Advanced Options page, you can configure the following settings:
You can change the Default Priority of eviction from the dropdown list.
You can also change the Eviction percentage; items will be evicted from the cache using this percentage value if eviction is enabled.
You can change the Clean interval value. The default is 15 seconds.
This cache can be started automatically upon the completion of this process if you have checked the Start this cache on Finish checkbox on this dialog box.
You can make the cache start automatically after service restart by checking the checkbox *Auto start this cache on service startup*.
- Click Finish. The created cache will appear on the Local Caches page, and a success notification will be received in the notification panel.
Using Command Line Tools
The New-Cache cmdlet enables the user to create a new cache on one or more server nodes.
This command creates a cache called myCache of Local topology with a Size
of 1024MB and InMemoryStoreType
specified as PubSubMessaging on the node 20.200.20.39.
New-Cache myCache -Topology Local -InMemoryStoreType PubSubMessaging -Server 20.200.20.39 -Size 1024