This article provides guidance on how to deploy Seeker in Microsoft's fully managed PaaS platform called Azure App Service. It enables development teams to quickly build powerful web, mobile, and API apps using .NET, .NET Core, Java, Ruby, Node.js, PHP, Python and Docker. Integrate Azure App Service into your existing frameworks, and get unparalleled developer productivity with cutting-edge capabilities such as continuous integration, live-site debugging, and the industry-leading Microsoft Visual Studio IDE.
Step-by-step guide
Here are the instructions:
- Login to Azure portal, and navigate to the App Service that you are instrumenting with Seeker.
- Create the folder D:\home\SiteExtensions, if it doesn't exist.
- Create a subfolder D:\home\SiteExtensions\Seeker.
- Upload the contents of <SEEKER_INSTALL_DIR>\agents\dotnet\seeker-agent-azure.zip to the \SiteExtensions\Seeker folder in Azure.
- Get the FTP settings of the Azure App Service.
- Download a FTP tool to transfer Seeker Agent to Azure. The tool used in the sample screenshots is WinSCP.
- To connect, enter the FTP credentials for Azure.
- Transfer seeker-agent-azure.zip to SiteExtensions/Seeker.
- Get the FTP settings of the Azure App Service.
- Extract all contents, and verify that Synopsys.Seeker.Agent.dll is present.
- Create the following folder D:\home\LogFiles\Seeker.
- Edit the Application Settings of the Azure App Service.
- Add SEEKER_SERVER_URL
- Add SEEKER_PROJECT_KEY
- Add COR_PROFILER_PATH to the x86/x64 profiler based on the application.
- Save the changes.
- Restart the Azure App Service.
- Browse to the application to ensure that the Application is started.
- Check the logs to ensure that Seeker Agent is able to connect to the Seeker Server.
Go to Seeker Console to verify that Seeker Agent has connected.
At the time of writing, Seeker 2019.2 only supported .Net, Java and Node.js development in Azure PaaS.