CAD Publisher WebApp Installation
Open a PowerShell window as an administrator, and enter the following command.
.\CentrowebApp.exe
Â
Â
Â
Select the language of the installation. Click
OK
Â
Click
Next.
Â
Select
I accept the terms in the license agreement and click Next.
Â
Select the type of site and click Next.
(Application Under Existing Site is the recommended configuration esp. for Distributed Deployments)Â
Â
6a. For applications under exist site,
select the parent site,Â
application name*,Â
and the source directory.
Click Next.Â
Â
*If you change the Application Name, then the address of the WebApp_JobEventHandler endpoint in the WCF client configuration of Pipeline Manager must be changed as well.
In "C:\Program Files\Actify\Centro\PipelineManagerService\Configuration\WCF" edit,
local_client.config
remote_client.config
Â
Example,
If I install Centro with the name "Centro-install", then I need to change the endpoint address to "net.pipe://localhost/Centro-install/JobEventHandler_svc/JobEventHandler.svc" in Pipeline Manager.
<endpoint address="net.pipe://localhost/Centro-install/JobEventHandler_svc/JobEventHandler.svc" binding="netNamedPipeBinding" bindingConfiguration="named_pipe_binding" contract="KitKat.ServiceContracts.ManagerContracts.IJobEventHandler" name="WebApp_JobEventHandler" />
Â
Â
Â
Â
6b.  For Stand-Alone IIS sites, indicate the site name, port and installation location. Click Next.
Â
Set the Location name for this CAD Publisher instance and the Location URI (how your user base will access the CAD Publisher instance. Note: Direct IP addresses should not be used).
Click Next.Â
Â
For applications under exist site, use the default or specify credentials for the Centro 7 directory.
Click Next.
Â
Enter email server information or choose to skip. ClickÂ
Next.
Â
Enter the IP address of the system containing the ArangoDB.
  Enter the database user name and password that the application uses to connect to the database.
It is recommend using a created database user other than the root user.
  Click Next.Â
Â
11. Select the location where uploaded catalog resource files will be stored and click Next.
Â
12. Â Click Install.
Â
13. Â Allow for the application to install
Â
14. Click Finish.
Â
15. Go to the login page. Verify the site is accessible.
This step is necessary especially for distributed deployments to attach the Location properly to the System Pipeline.
IMPORTANT NOTE:
If this step is skipped the Pipeline Manager Service WILL NOT START as this sets the parameters in the ArangoDB "Locations" Collection.
Â