CA Clarity Login

[vladimir zorc]

Hello all,

I am new to Clarity. Just installed Clarity v13.1. Before I continue with installation of various add-ins etc. I wanted to log-in. While I can log-in into Admin part, I am not able to get th euser screen on.
I tried Https:// localhost:80/niku/app in Chome and IE to noavail.
Read manuals (Admin, Installation, Basic User) but could not find the URL.

Could someone please let me know the exact command, and correct port number (where do you set it up?).

Thanks,

Vlad

[navzjoshi00]

Try thjis -

http://localhost:80/niku/nu#action:npt.overview


NJ

[vladimir zorc]

Thanks, but didnt work. Returned : HTTP Error 404. The requested resource is not found.

V.

[Deactivated User]

There is a problem with
Https:// localhost:80/niku/app

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.

Martti K.

[vladimir zorc]

another_martink wrote:

There is a problem with
Https:// localhost:80/niku/app

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.

Martti K.

I didn't use HTTPS actually , used HTTP - sorry about that.

Vlad

[vladimir zorc]

another_martink wrote:

There is a problem with
Https:// localhost:80/niku/app

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.

Martti K.

I didn't use HTTPS actually , used HTTP - sorry about that.

Vlad

[Deactivated User]

Are your services up?

Martti K.

[vladimir zorc]

another_martink wrote:

Are your services up?

Martti K.

[+] CA Clarity PPM Beacon [beacon] is started
[+] CA Clarity PPM System Admin Server [nsa] is started

Am I missing another service?

Vlad

[vladimir zorc]

another_martink wrote:

Are your services up?

Martti K.

[+] CA Clarity PPM Beacon [beacon] is started
[+] CA Clarity PPM System Admin Server [nsa] is started

Am I missing another service?

Vlad

[navzjoshi00]

U are missing app service :tongue:

NJ

[navzjoshi00]

& bg service

NJ

[Deactivated User]

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.

Martti K.

[vladimir zorc]

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.

Martti K.

I added services and deployed.

C:\temp\bin>service status all
[+] CA Clarity PPM Beacon [beacon] is started
[+] MSSQLSERVER is started
[+] CA Clarity PPM App Server [app] is started
[+] CA Clarity PPM System Admin Server [nsa] is started
[+] CA Clarity PPM Background Server [bg] is started

Admin page::

Service Type ID Server Status
CA Clarity Application app Clarity:9091 Started
CA Clarity Background bg Clarity:9091 Started
Database db Clarity:9091 Started

If I try link http://localhost:80/niku/nu#action:npt.overview
I get the same error: HTTP Error 404. The requested resource is not found.
I tried all other http combinations withou success.

Any new ideas?

Vlad

[vladimir zorc]

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.

Martti K.

I added services and deployed.

C:\temp\bin>service status all
[+] CA Clarity PPM Beacon [beacon] is started
[+] MSSQLSERVER is started
[+] CA Clarity PPM App Server [app] is started
[+] CA Clarity PPM System Admin Server [nsa] is started
[+] CA Clarity PPM Background Server [bg] is started

Admin page::

Service Type ID Server Status
CA Clarity Application app Clarity:9091 Started
CA Clarity Background bg Clarity:9091 Started
Database db Clarity:9091 Started

If I try link http://localhost:80/niku/nu#action:npt.overview
I get the same error: HTTP Error 404. The requested resource is not found.
I tried all other http combinations withou success.

Any new ideas?

Vlad

[Deactivated User]

So you tried also
http://localhost/niku/nu

What is in app-ca anad app-system logs?

Martti K.

[Deactivated User]

Just to make it sure:

You are on the server aren't you? Otherwise the localhost does not work.

Martti K.

[Deactivated User]

Another thing to make sure is that your database is available.

Martti K.


.

[vladimir zorc]

another_martink wrote:

Another thing to make sure is that your database is available.

Martti K.


.

Martti,

Only thing on your snaphot screen which differs to mine was the Instance field. I left it blank as if I put in niku (which would be presumably mine (not CLARITY!) db instance - app does not connect with database.
Now, should I try to explictly specify the URL in one of the CSA screens?
BTW all other prior suggestions taken and verified.

Vlad

[Anon Anon]

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)

[Deactivated User]

I added services and deployed.

C:\temp\bin>service status all
[+] CA Clarity PPM Beacon [beacon] is started
[+] MSSQLSERVER is started
[+] CA Clarity PPM App Server [app] is started
[+] CA Clarity PPM System Admin Server [nsa] is started
[+] CA Clarity PPM Background Server [bg] is started

Admin page::

Service Type ID Server Status
CA Clarity Application app Clarity:9091 Started
CA Clarity Background bg Clarity:9091 Started
Database db Clarity:9091 Started

Is an indication that the services started OK.

Just wondering if the database is available or not?

Martti K.

[vladimir zorc]

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)

Your latter remark was actually very useful. I spotted in system app log a port usage conflict 80 with Apache Tomcat. Stopped it (Tomcat) and the thing works. It was actually my colleague who initially looked at the logs and spotted "nothing out of ordinary" if you are wandering.
Anyhow, we are now experimenting and I shall publish the reasons why we had a problem in the first place. JAVA vs. Tomcat clash. perhaps we installed both or ...

Thank you all
Cheers,
Vlad

[vladimir zorc]

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)

Your latter remark was actually very useful. I spotted in system app log a port usage conflict 80 with Apache Tomcat. Stopped it (Tomcat) and the thing works. It was actually my colleague who initially looked at the logs and spotted "nothing out of ordinary" if you are wandering.
Anyhow, we are now experimenting and I shall publish the reasons why we had a problem in the first place. JAVA vs. Tomcat clash. perhaps we installed both or ...

Thank you all
Cheers,
Vlad

[Deactivated User]

Just wondering again...
If you stopped Tomcat which j2ee server are you using?

Martti K.

[vladimir zorc]

another_martink wrote:

Just wondering again...
If you stopped Tomcat which j2ee server are you using?

Martti K.

J2EE ver. 1.7.0_04

We might have multiple instances of Tomcat.
But anyhow if we stop Tomcat and then set to use either Tomcat app server or J2EE app server, access to logon works in both cases.

V.
.

[Deactivated User]

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.

Martti K.

[vladimir zorc]

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.

Martti K.

We started with new server running nothing but what the installation guide told us to install. We manually installed java, tomcat 7 first.
So we assume that Clarity application installs their own Tomcat automatically so you end up with two competing for the port.

I'll let you know when we finish with more experimenting.

Regards,
Vlad

[vladimir zorc]

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.

Martti K.

We started with new server running nothing but what the installation guide told us to install. We manually installed java, tomcat 7 first.
So we assume that Clarity application installs their own Tomcat automatically so you end up with two competing for the port.

I'll let you know when we finish with more experimenting.

Regards,
Vlad

[Deactivated User]

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.

Curious.

Martti K.

[vladimir zorc]

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.

Curious.

Martti K.

Yes but it has happened to some people that the order of installation (i.e. clarity-tomcat or tomcat -clarity) was determining whether you endup with 2 instances of Tomcat, so some people say for similar installations such as Service Desk etc.
We could not encounter the confict with IIS.

Vlad

[Deactivated User]

OK thanks. I could buy that.
I always install Tomcat first because Clarity needs that and never tried to install Clarity first.

Martti K.

[Anon Anon]

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.

Dipanjan

[vladimir zorc]

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.

Dipanjan

Well I in fact did the same: first installed Tomcat and then Clarity. Port number 80 was occupied by Tomcat so I changed it to 8080, and now everything is OK. BTW Tomcat 7 service is not running and we are still avle to access the apps. What's the point of installing Tomcat? Are we running web services over something else? As you can see still unclear about it.

Regards,
Vlad

[vladimir zorc]

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.

Dipanjan

Well I in fact did the same: first installed Tomcat and then Clarity. Port number 80 was occupied by Tomcat so I changed it to 8080, and now everything is OK. BTW Tomcat 7 service is not running and we are still avle to access the apps. What's the point of installing Tomcat? Are we running web services over something else? As you can see still unclear about it.

Regards,
Vlad

[Anon Anon]

Let me know how you are checking the status of the tomcat service.

Dipanjan

[Deactivated User]

How did you install Tomcat?

Martti K.

[Anon Anon]

From Clarity installation media, I extracted Tomcat from it ZIP to a local dir.

Dipanjan

[Deactivated User]

So just copying and not a real install.
That is what I have always done and not problems related to Tomcat.

Martti K.

[Anon Anon]

Yes, thats correct; earlier while doing fresh installation of 12.1.0, I did not face any issue, but for 12.1.3 fresh installation, I encountered the port number issue, and both the times I used the tomcat provided along with the installation media.

Dipanjan

[vladimir zorc]

Ok I think we came to the bottom of a problem wuth Tomcat: Earlier versions of Tomcat were listening on port 80. Latest version (at least) is listening on port 8080. The Clarity installation did not follow he change and it still offers 80 as a port. Thats why I had a problem.
I also no now that I am runnin Tomcat app server ( nsa vs niku in httm ) and that Tomcat on windows is hidden behinf java.exe processes. If you kill them that automatically stops Clarity Apps service.
Read more about Tomact on: http://www3.ntu.edu.sg/home/ehchua/programming/howto/Tomcat_HowTo.html

I am finished with this thread, and started installation of Business Objects.

Thanks for help,
Vlad

[vladimir zorc]

Ok I think we came to the bottom of a problem wuth Tomcat: Earlier versions of Tomcat were listening on port 80. Latest version (at least) is listening on port 8080. The Clarity installation did not follow he change and it still offers 80 as a port. Thats why I had a problem.
I also no now that I am runnin Tomcat app server ( nsa vs niku in httm ) and that Tomcat on windows is hidden behinf java.exe processes. If you kill them that automatically stops Clarity Apps service.
Read more about Tomact on: http://www3.ntu.edu.sg/home/ehchua/programming/howto/Tomcat_HowTo.html

I am finished with this thread, and started installation of Business Objects.

Thanks for help,
Vlad

[Anon Anon]

Thanks for the info Vlad. It is very helpful. :smile

Dipanjan

[Deactivated User]

That may very well be the Tomcat default and the following the link you posted it is also stated there.
However, the Clarity Install Guide says

Best Practice: If you are using a software firewall, provide an exception at the
executable level instead of the port level. This ensures the dynamic ports that get
allocated are open for proper multicast communication. See ephemeral ports in the
following list for more information.

80 or 443
Defines the HTTP or HTTPS port number used by the default CA Clarity Application
(app) service.
Type: Client to the CA Clarity application server

If that is not the case then something must have gone wrong with your installation or you have deliberately set Clarity to use some other port.

Martti K.

[vladimir zorc]

Martti,

"80 or 443
Defines the HTTP or HTTPS port number used by the default CA Clarity Application (app) service.
Type: Client to the CA Clarity application server"

...And this is exactly source of a problem because TOMCAT 7 has got 8080 (not 80!) as a default port for Clarity application server!
and furthermore,
if you read the instl. manual you see it stating this time correctly that 8090 is Tomcat port to access CSA, which never was a problem for me, as I hve had access to CSA all the time after installation.


Case closed.

Vlad

[vladimir zorc]

Martti,

"80 or 443
Defines the HTTP or HTTPS port number used by the default CA Clarity Application (app) service.
Type: Client to the CA Clarity application server"

...And this is exactly source of a problem because TOMCAT 7 has got 8080 (not 80!) as a default port for Clarity application server!
and furthermore,
if you read the instl. manual you see it stating this time correctly that 8090 is Tomcat port to access CSA, which never was a problem for me, as I hve had access to CSA all the time after installation.


Case closed.

Vlad

[Deactivated User]

8090 is Tomcat port to access CSA,

are you saying that you don't know the difference between CSA and APP?

And this is exactly source of a problem because TOMCAT 7 has got 8080 (not 80!) as a default port

may very well be the case because in your install something went wrong.


If your Tomcat were configured correctly you would have in the configuration written by the Clarity install

Connector port=80 protocol=HTTP1.1 connectionTimeout=60000 secure=false maxThreads=1000 minSpareThreads=1 URIEncoding=UTF-8 useBodyEncodingForURI=true maxHttpHeaderSize=65536 server=CA Clarity PPM

Martti K.

[vladimir zorc]

another_martink wrote:

So you tried also
http://localhost/niku/nu

What is in app-ca anad app-system logs?

Martti K.

The logs show nothing unordinary.

[vladimir zorc]

another_martink wrote:

So you tried also
http://localhost/niku/nu

What is in app-ca anad app-system logs?

Martti K.

The logs show nothing unordinary.