I'm having problems accessing the website of the WSO2 Enterprise Mobility Manager server. I have opened port 9443, but when I type localhost:9443/emm I get page not found.
What configuration do I need to change in the apache server to point it to the correct place. I am unsure what the root directory of the website is.
Ollie
Details:
Debian Jessie 32bit
WSO2-EMM Version 1.1.0
Apache 2.4.10
If you have downloaded the binary version 1.1.0 of WSO2 EMM, localhost:9443/emm should work after you execute {EMM_HOME}/bin/wso2server.sh.
If it is not working, please check the log file which is located at {EMM_HOME}/repository/logs/wso2carbon.log for the reason of failing.
There is no such specific changes to be done to Apache server when you install & run the WSO2 EMM. Can you log into carbon console?
https://localhost:9443/carbon/
Related
I am inside a corporate firewall that does not allow me to access the free deployed instance at https://console.gridgain.com/. I downloaded the source and tried to build but again the firewall does not allow me to go outside the network to retrieve the dependencies specified in the pom.xml file.
What are my options
You can download binary build of Ignite Web Console from Apache Ignite, deploy it on premise.
You can also deploy paid version of GridGain, deploy it on premise.
You can download WebConsole from the GridGain website by the following link: https://www.gridgain.com/resources/download
You can install it in your environment and use without needing to access external resources.
Recently I have installed Apache Http server 2.4 but I need disp_apache2.4.dll. I have gone through number of forums but no luck. Please suggest me some links or forums to get that dll file.
Note : I am using Adobe CQ (AEM)
Only "Dispatcher for Apache HTTP Server 2.2" is available for IIS on Windows. Dispatcher for Apache HTTP Server 2.4 is not supported and therefore the version you are looking for is not available on this platform.
I can run Spark on necessary port on localhost, but I can't find info how to run my site on my own domain name (not localhost).
Should I also run and configure any webserver, such as Apache Httpd?
OS: Windows Server 2008 R2, JRE 8.
You'll have to follow the instructions from your host provider. For example, I have an app hosted at OpenShift. Openshift recomends the use of CNAME records, I just followed their instructions, and my app is on air.
I installed solr 5.0.0 in my windows 8 system and apache-tomcat-8.0.0-RC5.exe ,my tomcat is listening to 8080 port.
I have copied all the 5 jars and log4j.properties from C:\Users\xyz\Desktop\solr\solr-5.0.0\solr-5.0.0\solr-5.0.0\server\lib\ext to tomcats lib folder .
jcl-over-slf4j-1.7.7.jar
jul-to-slf4j-1.7.7.jar
log4j-1.2.17.jar
slf4j-api-1.7.7.jar
slf4j-log4j12-1.7.7.jar
Added -Dsolr.solr.home=C:\Users\xyz\Desktop\solr\solr-5.0.0\solr-5.0.0\solr-5.0.0\ to tomcat service java options.
My tomcat server is up but solr http://localhost:8080/solr/ throws below an error
HTTP Status 503 - Server is shutting down or failed to initialize
type Status report
message Server is shutting down or failed to initialize
description The requested service is not currently available.
Apache Tomcat/8.0.0-RC5.
I tried various options like changing the tomcat port from 8080 to 8983. modifying solr.xml file . None of the solutions worked, may be because I am using solr 5.0.0 . could any one help me out ?
According Solr Doc: "Beginning with Solr 5.0, Solr is no longer distributed as a "war" (Web Application Archive) suitable for deployment in any Servlet Container. Solr is now distributed as a stand alone java server application, including start and stop scripts for use on Unix and MS-Windows platforms, as well as an installation script for setting up a "production" installation of Solr on *nix platforms managed via /etc/init.d.... ... Internally, Solr is still implemented via Servlet APIs and is powered by Jetty -- but this is simply an implementation detail. Deployment as a "webapp" to other Servlet Containers (or other instances of Jetty) is not supported, and may not work in future 5.x versions of Solr when additional changes are likely to be made to Solr internally to leverage custom networking stack features." I don't know if it means you can't deploy slr 5.0 to other container, like Tomcat. See full description here
I have this requirement to write a customized module in http server. Newer version of the application uses the APACHE http server and the older version is deployed on IHS (IBM Http Server). I tried googling it but I couldn't find anywhere if I can write a module and packaged it in IHS .Is that possible ? If yes , how ? Do I have to get the code and build it with my module or I can write some extension and plugin into IHS. anything will help , thanks.
Yes, you extend IHS the same way you extend a vanilla Apache HTTP Server module -- with the Apache HTTP Server API.
You can either use binary modules compiled against vanilla Apache, or compile directly against IHS with the inclued bin/apxs script.
For pointers, look at any existing module in the core distribution of Apache, or Nick Kew's Apache Modules book.