I am new to Maximo 7.6.1 installation. Have installed DB2, WAS 11.01 and Maximo 7.6.1 . All of them on the same personal laptop running Windows 10.
Installations successful (except for the final ear deployment). DB2 and WAS are successfully installed. On rebooting the laptop, I get following different logins db2admin,
maximo ,
maxdb76
My question is using which url I can access/ or get the login page of Maximo.
Try modifying this url based on your setup.
You may need to specify a port after hostname (e.g. :9080) if one is configured and specifying localhost or your IP address (found by running ipconfig from the command line) can help rule out any issues with hostname.
You said, "except for the final ear deployment" ... but it is that final EAR deployment that makes Maximo run when you start the app server you deploy it to. Once it is deployed and running, you should be able to access the Maximo login page by browsing to http://localhost:9080/maximo or https://localhost:9443/maximo.
Related
I've installed Oracle Apex on local machine, following this steps - LINK
I used Embedded PL/SQL Gateway (EPG) Configuration.
And when I try to connect on http://localhost:8080/apex I get - unable to connect firefox message. I checked firewall is inactive
Assuming you've followed all the steps and you're installing on windows, check if the OracleJobScheduler service is running (it will be postfixed with the instance name). You can do this by searching for Component Services in the windows search bar, then open the Services (Local). If the scheduler job service is not running then start it, wait a few moments, and try to re-connect.
On Linux (Gentoo) if I start GlassFish from Netbeans/Services area, the server will started, the admin site is reachable, but in Netbeans I get the following error message:
GlassFish Server 4.1 start failed.
Please check server admin user name and password properties.
Also please check the server log file for other possible causes.
and I can neither start again, nor terminate.
Any idea?
Well, I had the same situation but on Mac. After I updated to macOS Sierra. In my case was a block on the sites that use system proxy settings, where localhost, 127.0.0.1, are blocked.
Perhaps, your case es similar, but a proxy setting on you Linux (GENTO).
For mac this is the solution AppServer issues from Netbeans
Step 1: (Try to search for the same on Linux) Go to system preference >Network>Select your wifi connection>Advanced>select
proxies tab. There check 3 options 1) Auto proxy Discovery 2)Automatic
Proxy configuration 3) web proxy(http)
Step 2: Go to Netbeans>preferences>General> select use system proxy> reload> test connection You may get connection successful. If
connection gets successful, Now Clean & build your Applications in
netbeans and press run .
I hope this help you and give you an idea.
I'm learning to use the open source version of OpenShift. I have downloaded the linux image and started it on a virtual machine (named VM1) on my PC, which runs Windows 7. On another VM (named VM2) I have installed another linux OS and configured the JBoss IDE to work with OpenShift. Then I have successfully created and hosted an app on my local OpenShift PaaS cloud. Here is where the problem starts:
On VM2 (the one running linux where I developed the app) I have no problem accessing my account webpage on OpenShift, viewing what apps I have created and testing them.
From any other PC on my network I can log in to the OpenShift web console and view my apps by simply entering the IP of VM1 (in my case 192.168.1.107). There I can see the URL to launch my app: http://localtest2-mydomain.openshift.local/ . But when I click on it, I get a message saying that the web page is not available. Again, if I use this link in VM2, it works like a charm.
I tried changing the system32\drivers\etc\hosts file so that and link ending in openshift.local will be sent to the IP address of VM1, but it doesn't work. Can anyone help me?
As far as I know, you can not use wildcards in your hosts file, you would need to specify the entire url in your hosts file for it to find it correctly. Give that a try and see if it helps.
I'm trying to do msdeploy of a MVC app to a windows7 box, running on command-line. And kept getting this error:
Error Code: ERROR_DESTINATION_NOT_REACHABLE
More Information: Could not connect to the destination computer ("192.168.xxx.xxx"
). On the destination computer, make sure that Web Deploy is installed and that
the required process ("The Web Management Service") is started.
Error: The remote server returned an error: (404) Not Found.
Error count: 1.
I've verified both Wmsvc (seems this is being used) and MsDepSvc are running. And firewall are disabled. In the browser when I visit https://192.168.xxx.xxx:8172/msdeploy.axd, I got a Server Error 404, seems a bit further than where the command-line stopped.
Most of instructions on setting up IIS7 and Web deployment I could find online is for MS Servers. Both my local machine and the Windows7 machine has the same version of Msdeploy installed.
I had exactly the same issue with a VM on Azure, and the solution was to enable first the IIS Management Service and then install Web Deploy (I used Web Platform Installer). Seems that the installation order matters. You can find a blog entry I wrote about this here http://davidjrh.intelequia.com/2012/10/configurando-web-platform-installer-y.html
For non-server operating systems (i.e. Windows 7) the Web Deploy publish via Web Management Service is not supported. Instead you will have to use the Remote Agent Service, this is an admin only publishing service. You can find more info at http://technet.microsoft.com/en-us/library/dd569059(v=WS.10).aspx.
I had the same issue using MSDeploy to deploy my web application to remote IIS 7.5 web server running windows 7. I have just figured out how to fix the problem today after reading Sayed's post, so I wanna post my solution here for anyone who would run into this problem like me. Try this:
Enable IIS Management Service (in control panel >> add or remove features >> add or remove windows features)
Install Web Deploy (http://www.iis.net/downloads/microsoft/web-deploy)
Open cmd with Administrative privilege, type “net start msdepsvc” to start the “Web Deploy Agent Service”.
Check this link in your browser: http://serveraddress/MsDeployAgentService/, if it prompts for username and password, MsDeployAgentService is running on server, go to the next step.
In VS, type in http://serveraddress/MsDeployAgentService/ in Service URL while creating publish, instead of https://serveraddress:8172/MsDeploy.axd, and click test connection. It should be ok now.
After checking the Management Service and Web Deploy 3.0 were correctly installed, I found that (from VS2012 at least) the Service URL seems to matter here too, attempting to publish to any of the following did not work for me:
FQDN (localmachine.domain.local)
Domain IP Address (172.22.xxx.xxx)
Loop-back IP (127.0.0.1)
Whereas the following DID work:
localhost
NetBIOS name (localmachine)
I am using CCnet 1.6 and cctray 1.6. On the build server, the tray works properly using localhost. Remotely though, I am not able to connect the tray to the dashboard. The dashboard URL works great, but when I put that into the cctray settings, I get a 500 internal server error.
This worked up until I had to move CCnet from defaultwebsite to its own. Did I miss something when I changed it over?
Thanks,
Joe
Actually this is similar to a question I just asked but if you want to persist with remoting (but may not work so well over the Internet with firwalls and the like)
Open your dashboard.config (likely path is C:\Program Files (x86)\CruiseControl.NET\webdashboard\dashboard.config)
Find the port number your dashboard is connecting to the server on (eg: 21234)
In CC Tray, select remoting and enter hostname:portnumber (eg: mycruiseserver:21234)
Assuming that the CCNET server is part of your local network this should work:
Select .NET remoting as connection type
Specify the CCNET server's address only by its IP address (instead of using the dashboard URL)
Try switching off your firewall, it may be that you havn't opened your port.
Then, use the buildserver:port method (remotely via .NET).
I just fixed my problem (v1.8.3 for my installation).
I set the name attribute in the <server /> tag in dashboard.config to match the hostname. I'm not sure if that is required but that is the first thing I tried.
Then I inspected the bindings for the site that the dashboard is hosted under in IIS. The hostname for the binding was blank, so I changed it to the hostname for the site.
I noticed that the CCNet machine's event log had exceptions logged for unknown domain when I was trying to connect CCTray to it.
When I went to add a build server in CCTray on the remote machine, I selected via dashboard and it worked for me.