This is especially important for a Prism installation that relies on integrations, plugins, or ancillary products that leverage a connection directly to Retail Pro 9 or RIL. Where data is being brought into Prism via custom profile that data must be put in a format which is recognized as valid for processing by Prism. Data can only be communicated using Connection Manager profiles established between two Prism installations or a Prism installation and a "custom" profile connection. ![]() The Connection Manager in Prism 2.x does not support native connections between Retail Pro 9 and Retail Pro RIL. Prism 2.x does not natively communicate with legacy Retail Pro apps This includes managing inventory cost, price, and quantity, all document types, customer details, and preferences, and any other data which is required for operation within Prism. Refer to the appropriate document for your EFT processor: Prism and Adyen, Prism and BS Payone, or Prism and Global Payments).Īll data required to run Prism is maintained and managed within the core functionality of Prism 2.x. Upgrading to Prism 2.x from legacy versions of Retail ProĪ separate document is available for each EFT processor that Prism supports.Silent install via command line (e.g., via scheduled task).Post-Upgrade/Install information about configuring preferences, security, and day-to-day replication of data between servers. ![]() Installing a blank Oracle DB and new Prism 2.x.Installing Prism "over-the-top" of 1.14.x.Prism 2.x notes and installation best practices. ![]() This topic is divided into the following sections: If you need information about installing Prism 1.14.7 or earlier versions, download the PDF file linked above. This Getting Started Guide has instructions for upgrading to/installing Prism 2.x and changing basic configuration settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |