Talisman MPCS™ can run either on physical dedicated machine(s) or on virtualized machine(s).
It requires Intel® 64-bit processor or similar, and is its multithreading mechanism relies on Logical CPU Cores (LCPU or vCPU for virtual environments). It is able to run on low-performant systems with minimum 2 GB-RAM & 1 LCPU or on compute-intensive systems with up to 200 LCPUs.
Binaries are available for Linux RHEL/Debian distributions and Microsoft Windows® Server. Below are the steps to install on your favorite platform.
Depending on your distribution:
RedHat 8/...
CentOS 8/...
Fedora 26.1/27/28/...
sudo rpm --import https://download.alsego.com/p/pkgkeys/alsego.asc
sudo rpm -i https://download.alsego.com/p/tmpcs/rhel/repos/TMPCS-Repo-1.0-8.x86_64.rpm
sudo yum install epel-release
sudo yum install TMPCS.x86_64
sudo su
cd /usr/local/Talisman/MPCS/Release/xtra/
./TMPCS_InitConf.sh
exit
sudo systemctl start tmpcs
Debian Stretch/Buster/...
Ubuntu 16.04/18.04/20.04/21.04/...
curl -s https://download.alsego.com/p/pkgkeys/alsego.asc | sudo apt-key add - or alternatively wget -qO - https://download.alsego.com/p/pkgkeys/alsego.asc | sudo apt-key add -
sudo su
echo -e "deb [arch=amd64] https://download.alsego.com/p/tmpcs/debian/9 stretch main" > /etc/apt/sources.list.d/tmpcs-release.list
exit
apt-get update
apt-get install tmpcs
sudo su
cd /usr/local/Talisman/MPCS/Release/xtra/
./TMPCS_InitConf.sh
exit
sudo systemctl start tmpcs
From Server 2008 R2 (SP1).
Test if Talisman MPCS™ is running.
http://hostname:8080/
Administration Console
link.
Administration Console
full privileged user account
To speed up the learning curve, some videos are at your disposal.
Additionally, the below sample packages are made available during the installation. To activate them, you have to follow these steps from the Administration Console
:
a. Menu > Packages , then click on Import .
b. Select the dpack_aggregated_portfolio_sample package and click on Load .
c. Select All items and click on Import Selected .
a. Menu > Topology > PHYSICAL CONNECTIONS, then click on Add .
b. Open a new browser window/tab at URL http://hostname:8080/tmpcs-resf/samples/portfolio/Physical_IMStore_DDL.sql and copy the DDL dedicated to the In-Memory datastore.
c. Back to the PHYSICAL CONNECTIONS window/tab browser, enter a name for the Physical Connection, i.e.: P-IM_Portfolio_Sample.
d. Select In-Memory Store as type.
e. Paste the DDL copied in step b. as data model.
f. Click on Test Connection .
g. Click on Save .
a. Menu > Topology > LOGICAL CONNECTIONS > Associations , then click on Add .
b. Select L-IM_Portfolio_Sample as Logical Datasource Object (LDO).
c. Select (Default) as Environment.
d. Select the Physical Connection name you provided at step 2.c..
e. Click on Save .
a. Open a new browser window/tab at URL http://hostname:8080/tmpcs-resf/samples/portfolio/pf-positionsapp.
b. You should get the consolidated view which for data are aggregated from CSV file, XML file and Excel Workbook into the dedicated In-Memory datastore.
a. In the application opened at step 4.a., click on one of the portfolio quantity cells to enable edit mode.
b. Enter a new value and then press the [Enter] key. The In-Memory datastore will be updated accordingly.
a. Menu > Packages , then click on Import .
b. Select the dpack_subscriberlist_sample package and click on Load .
c. Select All items and click on Import Selected .
a. Menu > Topology > PHYSICAL CONNECTIONS, then click on Add .
b. Enter a name for the Physical Connection, i.e.: P-SQLite_Sample.
c. Enter the location samples/subscribers/Subscribers.db as DB File.
d. Click on Test Connection .
e. Click on Save .
a. Menu > Topology > LOGICAL CONNECTIONS > Associations , then click on Add .
b. Select L-SQLite_Sample as Logical Datasource Object (LDO).
c. Select (Default) as Environment.
d. Select the Physical Connection name you provided at step 2.b..
e. Click on Save .
a. Menu > Services .
b. Go to the /tmpcs-uds /samples/subscribers/list webservice definition.
c. Click on the relative icon; a new browser window/tab will open with the JSON recorset result in it.
d. To view the recordset as XML result, add &output=xml to the URL.