another_martink wrote:There is a problem with
If you use https the port is normally not 80.
See in CSA how you have set it up is it with http or https ans and what is the port.
another_martink wrote:Are your services up?
another_martink wrote:To login to the application in V13 you need beacon and app.
That is if your database is not a service managed by Clarity. It it is you need db as well.
You add and deploy services in CSA.
When you system is up and running you would normally have also bg. That is after you have rescheduled the scheduled jobs.
another_martink wrote:So you tried also
What is in app-ca anad app-system logs?
another_martink wrote:Another thing to make sure is that your database is available.
vmz wrote:Now, should I try to explictly specify the URL in one of the CSA screens?
vmz wrote:The logs show nothing unordinary.
Dave wrote:vmz wrote:Now, should I try to explictly specify the URL in one of the CSA screens?The detail in the "Application" tab in the CSA, against the "Application Instance: app" settings dictate how you would access the application - so yes obviously these need to correctly configured and you need to be using them. If you have not setup details in this CSA tab then you should start there before you startup the app service.
vmz wrote:The logs show nothing unordinary. If, as you say, you are new to Clarity, how do you know what is ordinary and what is not ordinary? :wacko:
(You are being directed to look in your logs in order to detect whether your app service has even started correctly)
I added services and deployed.
another_martink wrote:Just wondering again...
If you stopped Tomcat which j2ee server are you using?
another_martink wrote:Agreed that you can have multiple version of Tomcat (or other) and the conflict occurs when the same port is used for two.
What else might you have using port 80.
another_martink wrote:I've not seen that happen. I have always to install Tomcat manually.
What can happen is that IIS is installed on the OS for one reason or another and that could use port 80 by default.
However even if you stop Tomcat Clarity will nto be using IIS.
dipur86 wrote:I also faced the same issue though I have installed Tomcat first then installed Clarity; Tomcat was not allowing Clarity to use the port number 80 and had to use a custom port number since I am not aware how to change the setting in Tomcat freeup the port. In the NSA Application Setting page, I updated the port to 8888 and was able to login to Clarity App using the same.
8090 is Tomcat port to access CSA,
And this is exactly source of a problem because TOMCAT 7 has got 8080 (not 80!) as a default port