Create New Client
Creating a New Client Information
There are multiple steps when creating a new client, first is setting up a Hyper-V server, second setting up the connections and SQL server and third is updating the web files (IE, OA, DC, Shop, RC)
Before you start you will need to make sure that .6 windows updates are complete so once the client is setup you don't need to run them again.
You will need a connection to 10.134/V$ once on the new virtual as well for the Web Files and OA build.
You will also need to find a new IP Address for the client, to do this you will want to go to SQL in OA_ProdigixInternal and open the IPAddress table. To double check the IP address is open you can Ping it using CMD or try connecting to the machine VIA remote desktop.
Additionally you can review the setup video CreateNewClient
Creating new Hyper-V server
First connect to .155, once connected open the Hyper-V manager and open a windows explorer.
In your windows explorer you will go to the G:\ drive and into the Virtual Hard Disks folder, once in the folder you will copy the NewClientCore.vhdx into the same folder and it will be named NewClientCore - Copy.xhdx.
Once the copy of the NewClientCore.vhdx is complete you will rename the vhdx file to the client name.
Once you have copied the file and changed the name you will then change to the Hyper-V manager you opened and on the right under Actions select New and then select Virtual Machine.
Continue past the Before you Begin step and give the Virtual Machine the name of your client, continue forward and select Generation 2, continue forward to select your assigned memory which will be set at 2048, continue again to the connection selection which will be in the drop down and will be named HVVirtualSwitch.
Once you have gotten to the Connect Virtual Hard Disk you will want to select the Second existing option, once you have selected this Browse to your G:\ drive and go into the Virtual Hard Disks, select the new client vhdx you created.
Before you start the server the server you will right click the new Virtual Machine and select Settings, once in the settings you will head to the bottom of the list on the left and change the Automatic Stop Action to Shut Down, you will also change the Automatic Start Action and set the start up delay, the delay can be set anywhere from 150 to 450 seconds, apply the changes to save them.
Once you have saved these settings start the machine and connect to the machine by double clicking the Virtual Machine or right clicking and selecting connect. (Do not go full screen when connecting) In the top left of the under the File select the Ctrl+Alt+Delete,this looks like 3 keyboard keys to login.
Once logged onto the Virtual Machine you will close the Shut Down Event Tracker, then in the bottom right of the screen select the Computer with a yellow warning symbol and select the Network and Sharing Center, once the pop up appears select the Ethernet 19 which will have another pop up. On this pop up select the Properties option which will have another pop-up, on this pop up there will be a list of checkboxes with names, uncheck the Internet Protocol Version 6 and then select and view properties of the Internet Protocol Version 4. Once in the new pop-up/properties section you will be able to add in the IP address, select the Use the follow IP address and enter in the follow IP addresses
- Client IP you picked before starting the process (looks like 192.168.15.X)
- Subnet will auto populate and should be 255.255.255.0
- Default Gateway will always be 192.168.15.1
- Preferred DNS will be 216.83.147.2
- Alternate DNS will be 8.8.8.8
Once you have set the IP addresses you can now select okay and close all of the pop ups.
Now you will open the Control Panel and select System, once the System window pop's up you will want to change the computer name by clicking the box named "Change" in the System Properties window. The name you set it to will be the client name. You will need to restart the computer to apply the name change.
Now that the IP address is applied the Hyper-V can be connected to using Remote Desktop, the next step would be creating the SQL Server Database and updating the Web Files and OA.
Creating SQL Server Database
Connect to the .173 SQL Server machine, once connected open the Microsoft SQL Server Management Studio, once open you will see databases on the left side of the screen.
Right click the beginning folder named Databases which is directly under the IP address, add in the client name as the Database name and select OK. You will not need to update any other field on this pop up other than the client name.
Once you have created the Database you will need to restore the Database, to do this right click the newly created database, select Tasks, Restore then Database.
This will then pop up a window, make sure the Destination Database is set to the new client, it should be set by default.
In the Source section you will need to select the Device you are restoring from, once you select the device you will use the 3 ellipticals to the right, a new pop up will display and state the Backup Media Type, make sure this is set to file and then select Add.
The add button will then pop up a window to the B:\ Drive, select the B:\SQLBackup folder and then select SQLS03. You should see B:\SQLBackup\SQLS03 at the top of the page if you are in the right spot.
Once in the SQLS03 folder you will want to open the name NewClientDBCore folder then the Full folder, the files in this folder will be dated so select the most recent dated file. This will then close the pop ups and you should be on the Restore Database page again.
You will need to change a couple additional settings before finishing the store, select the Options wrench on the left and make sure the Overwrite the Existing Data and Close Existing Connections is checked and the Take Tail-Log back up is not checked.
Once you have made sure these 2 where checked and 1 un checked you will click the OK in the bottom right to finish the restore, the restore will take a minute.
You are now finished with the SQL Server Database setup and will need to finish Updating the Web files and OA
Updating Web Files and OA
Setting ODBC
Once you have created the SQL server log onto the client machine you have just created and are working on, once logged onto the computer open up the ODBC 32-bit and ODBC 64-bit.
Once opened you will not have to make changes to the first screen so you can just select Next, on the second screen you will need to use the password for the SQL server to continue.
Once you have entered the password and select Next you will see a screen that allows you to change the Default Database, use the drop down to select the client SQL Server Database. Once selected you will continue through until you see a test connection, test the connection make sure you see a TESTS COMPLETED SUCCESFFULLY! and then you are complete.
This process is the same between the 32 bit and 64 bit ODBC.
Updating connection files for OA and Running OA build
To update the OA connection files to the new database you will open a files explorer, once opened go into C:\Program Files (x86)\Prodigix, once in this file location you will want to find the 5 files below. (Note: searching by file Type is a quick way to get them all together)
- prodigix.config
- connection.ini
- OAParms.Ini
- Prodigixsoftware.Ini
- CommissionCenter.exe.config
Once you have opened these 5 files you will want to change the "Database", "Initial Catalog" or "Catalog" in the files to the SQL Database name. You will also want to check the files for the Company or Company name and make sure this is updated to the client name. *Make sure you save the files once you have updated the database names and company names.
To run the Office Automation build you will open a connection on your computer to \\192.168.10.134\v$\Source Code\Bin, you will copy all the .exe, .dll and .ocx files to the c$\OABuild folder.
Once you have copied over the files you will go onto the client machine and on the desktop there will be a file called PDXFileReg64.bat, right click and run this .bat file as Administrator. Once complete load the Office Automation and click around to make sure the build pushed as intended.
Updating Web Files and Updating connection for web files
Once you have updated the OA connection strings you will want to update the Web based software (Shopping Cart, Report Center, Distributor Center, Signup etc.)
You will start by opening up two file explorers from the new clients server. The first folder will be to C:\inetpub\wwwroot, this will be where all the Web based software is.
The Second file explorer you will connect to 192.168.10.134\v$\sourceCodeWeb. Note: these connections will need to be completed on your machine as client machines will not connect to .134
You will complete the steps below for each Web based folder, Shopping cart, RC, DC, Signup, Graphical Tree and Prodigix API. There is an additional folder to be updated which is the Email Manager, this will be within the C:\Program Files (x86)\Prodigix folder.
Once complete you will also want to update a Connection String, two folder's will have connection strings that need to be updated that being RC and DC.
If you have the Clients Sub-Domain URL you can also update the the Corporate folder Index.ASP file and change the URL, this link is essential if any user/consumer enters in the sub-domain without a specific page IE member.tranont.com will redirect to member.tranont.com/dc due to this link.
Once connected you will want to find the web based folder you are updating and open it.
Once opened delete all the contents within the folder on the client machine NOT .134, you will then copy over all of the contents from the 134\v$\sourceCodeWeb\(X) over to the client machine. (Do not delete the folder as there are permissions tied to the folder)
The RC connection strings are updated by going to the base folder and finding the file named Web.config, in the file their will be a line stating the Initial Catalog that will be updated to the SQL database name at the top of the page, near the bottom of the page you will need to update ReportingClientCatalog to the client database name.
The DC connection strings are updated by going to the Includes folder and finding the file named config_database.asp, make sure the DataSource is set to PDXSQLDATA and the Database is set to the client SQL Database name.
Once the files have copied over you the files and updated the connection strings you will want to make sure the pages load and then you are complete.
GRAPHICAL TREE SETUP
NOTE: The Graphical tree will only work through the dc if the client has already setup their domain and SSL with us.
- Copy newest versions of 'GraphicalTree2' and 'ProdigixAPI' FROM 134
- Graphical Tree
- Modify includes/constants_settings.asp
- Set the server in the connection string variable to PDXSQLDATA
- Set the database in the connection string variable to the new clients database
- Verify API_STRING is 'Application("CompanyDomainProdigix") & "/treeapi/distributor/"'
- Prodigix API (Tree Api)
- Modify PublishedAPI/appsettings.json
- Set the server in the connection string variable to PDXSQLDATA
- Set the database in the connection string variable to the new clients database
- Database
- ClientSettings
- Update the client setting 'CompanyDomainProdigix' to be the new domain we host (must be https for graphical to work)
- Update the client setting 'Amazons3Bucket' to the clients amazon setttings so the proper pictures pull up.
- if the graphical/api still isn't working after doing the above it may be that they don't have the Dotnet core 2 hosting bundle installed on their server.