To install Shopping central components, double-click
ShoppingCentral.msi and follow the prompts:
license key for Windows Servicing Assistant (WSA).
If you are evaluating Shopping, leave the license key blank for a 30-day evaluation period.
WSA does not have an evaluation period. If you do not have a license key for WSA leave the field blank; you will be able to create WSA applications in the Shopping Admin console but users will not be able to launch them.
C:\Program Files (x86)\1E\Shopping\
C:\Program Files (x86)\1E\Shopping\Database\
C:\Program Files (x86)\1E\Shopping\WebSite\
C:\Program Files (x86)\1E\Shopping\Website\Shopping\
C:\Program Files (x86)\1E\Shopping\WebSite\ShoppingAPI\
C:\Program Files (x86)\1E\Shopping\CentralService\
Admin Console –
The database component will always be installed onto the selected SQL Server instance, and its destination cannot be changed during this step. To see how much disk space is required for the installation, click the Space button on the Custom Setup page.
On the Database Server screen, enter the following and click Next.
The name of the SQL Server instance to host the Shopping database. Checks are made to see if the machine is an SQL Server. You have the option to drop any existing Shopping database.
If you are upgrading and want to preserve your existing data, ensure that you do not select the Drop any existing Shopping database option.
|The SQL Server Name defaults to |
If TLS 1.0 is disabled on either server that will host the Shopping website or SQL Server, then:
enable the checkbox TLS 1.0 disabled - install using TLS 1.1 / 1.2.
install SQL Server Native Client 11.0 as described in Preparation: Installing when TLS 1.0 is disabled.
localhostif it is installed on the same server as the Shopping Central service. To set a non-standard port (if this has been configured for the ActiveEfficiency Web API), add it to the end of the server name using the following notation:
servername:portNo. If you have set a host header for the ActiveEfficiency Web API you can enter this into the field instead. When you click Next, the location will be validated for the presence of the ActiveEfficiency Web API.
localhost. Change this to refer to the AD domain controller. For details about which DC to nominate, see Preparation: Active Directory Server. Using the AD namespace is preferred in that if you specify a domain controller and that DC becomes unavailable, you won't be able to open the Shopping console.
ACME\ShoppingSrvin the User name: field. The name and password for the account will be verified when you click Next. You must also set an account or group to be used to validate communications from the Shopping Receivers.
On the Exchange or SMTP server screen – enter the fully qualified domain name for your Exchange or SMTP server. The SMTP server name defaults to
localhost for locally defined SMTP servers. You can change the SMTP server name to an external server by entering its name into the field. For example, you could set the SMTP server name to the fully qualified server name for an Exchange server such as
smtp.acme.local. The server entered will be verified when you click Next.
On the Systems Center Configuration Manager integration screen – enter the Configuration Manager server name (it defaults to local host) but you can set this to a remote server by entering the server name in the Configuration Manager Server field.
|The server is not necessarily the Configuration Manager Central site server but it must be the server at the top of the part of the Configuration Manager hierarchy you want to manage with Shopping. If you have a DNS suffix defined for the Configuration Manager server, you can only use its NetBIOS name or its fully qualified domain name. If you are intending to remotely access Configuration Manager installed on a Windows 2003 server with Service Pack 1, you will need to manually enable the Shopping Central service account to access the machine remotely. See service account permissions when Configuration Manager is remote for more details.|
The entries will be validated and warnings are raised if problems are encountered. The installer searches for email addresses for the Admin and License manager accounts using each account's AD-defined mail field. If these are not found a warning is not displayed, and they will have to be added in the Shopping Admin Console Web settings post installation.
1E recommend using AD Groups instead of individual accounts because groups can be managed outside of Shopping.
http://shopping.acme.localor if you have modified the port from its default,
You can install the Shopping Central service in unattended mode using the
msiexec.exe command-line. For example, to install all Shopping components with a Shopping service account, license it, setup the admin, reports and license manager accounts, define the Shopping security AD groups, locate the AD, SMTP, SQL and Configuration Manager server, then use an install script.
Command-line switches are described in Shopping Central installer properties.
IISHOSTHEADER property is a requirement for an unattended installation, in order to define the HTTP bindings for the Shopping Website. The bindings can also include:
IISIPADDRESS– you can provide a custom IP address for the Shopping Website, set it to * if you want it to be non-specific
IISPORT– the IIS port for the Shopping Website
Remove WSAPIDKEY if you are not using Windows Servicing Assistant.
Ensure that the parameters you provide are correct. No validation takes place for this part of the unattended installation nor are integration errors logged. If the integration fails, configure the parameters manually.
If you want to integrate Shopping with Application Migration, add the following command-lines (substitute the [
parameters>] for your environment):
APPMIGRATIONENDPOINTURL=http://[host:port] ^ APPMIGRATIONMODE=1 ^ SLAPLATFORMUSERNAME=[domain\user] ^ SLAPLATFORMPASSWORD=[password] ^
Open the Shopping.Receiver.exe.config file in C:\Program Files (x86)\1E\Shopping\Shopping.Receiver.v5.6.0 on each SCCM server and edit the ShoppingWebUrl to HTTPS from HTTP with correct port.
Restart the Shopping Receiver Service on each SCCM server.
Please contact 1E if you encounter any issues while setting up Shopping to use HTTPS.
msiexec /i ShoppingCentral.msi ^ ACTIVE_DIRECTORY_SERVER=ACME.local ^ INSTALLDIR="C:\Program Files (x86)\1E\Shopping" ^ AESERVERNAME=aeserver ^ SVCUSER=ACME\ShoppingSrv ^ SVCPASSWORD=svcpassword ^ SHOPPINGCONSOLEADMINUSERS="ACME\FullShopAdminsGroup" ^ SHOPPINGCONSOLEUSERS="ACME\PartShopAdminsGroup" ^ SHOPPINGCONSOLESMSUSERS="ACME\ShopSMSUserGroup" ^ ADMINACCOUNT="ACME\ShopAdminsGroup" ^ REPORTSACCOUNT="ACME\ShopReportsGroup" ^ LICENSEMGRACCOUNT="ACME\ShopLicenseMgrsGroup" ^ PIDKEY=abcdef-1234-5678-8765-4321 ^ WSAPIDKEY=abcdef-1234-5678-8765-4321 ^ SQLSERVER=ACME-SQLSERVER ^ SMTP_SERVER_NAME=smtp.acme.local ^ SMSPROVIDERLOCATION=SMS01 ^ IISHOSTHEADER=shopping.acme.local ^ SHOPPINGURLPREFIX=http://shopping.acme.local ^ RECEIVERACCOUNT="ACME\ShopReceiversGroup" ^ DATABASENAME=Shopping2 ^ DATABASE_COMMANDTIMEOUT=3600 ^ DATABASE_CONNECTIONTIMEOUT=30 ^ DATABASE_MODE=multiuser ^ USEGLOBALCATLOG=1 ^ ENABLETLS12=0 ^ /l*v %temp%\ShoppingCentral-install.log /qn @echo Press any key to close @pause>nul
If you use the above script to upgrade Shopping, and the command-line encounters errors, a rollback occurs which may leave your production system in an unstable state. Should that happen, you can restore the database and the files from the backup you made. If you are having trouble with the restore, contact 1E support for assistance.
Prior to running an upgrade (this is recommended and good practice):
C:\Program Files (x86)\1E\Shopping. Ensure that you copy all folders and files.
Shopping can be uninstalled from Windows Control Panel Programs and Features or by running the
ShoppingCentral.msi and choosing the Remove option. Alternative, you can run a command-line to uninstall Shopping with:
msiexec /x ShoppingCentral.msi /qb
When you uninstall Shopping central, its database (Shopping2) is left on the database server. If you subsequently reinstall Shopping, you have the option to drop the old database in the installer screen.