I have installed the trail MMC. depolyed 2 application there. 1 using mule console and second using Cloudhub(target- configured mmc server there).
what would be the url for both.
tomcat is running on port :8585
serverName: himserver-onpromice
applicationName deployed using mmc console: findName
applicationName deployed using clouhub console: getMyName
I checked with below but not working,..
http://himserver-onpromice:8585/getMyName/
MMC is on-premise deployment and hence it will use the ports configured inside your mule application. If we assume you are using HTTP listener connector as input source then you should use the configured port for it. The default port is 8081 (on cloud default port is 80). Hence, in this case URL should be: http://himserver-onpromice:8081/findName/getMyName/
Related
When I try to deploy a sample application 1 which runs on port 1001 using a Global Configurations properties file, the application deploys to both the servers.
I can test the application on 1001 port and 8086 port.
Subsequently, when I try to deploy Application 2 on 1002 port. I can see that the application gets partially deployed to Server 1 and can be tested successfully on port 1002.
Can anyone explain this behavior of the Mule Standalone instances.
I am a newbie and trying out different concepts on Mule 4
Server 1 Port: Default port
Server 2 Port: 8086
Group: QAGroup
POC with proprties file port 1001: 8086/1001- Running on Both nodes
Typeof: 8081 - Only running on Node 1
Logger: 8082 - Only Running on Node 1
Logger with proprties file port 1002: 1002- Only running on Node 1
Only one app can listen to one particular port. It looks that your servers have apps what ara already listening to this port. You, maybe, had tried somthing and then forgot about it. It is not actual flow or http listener. It is http listeneer configuartion in any flow of any project.
First of all I would check all log files for errors.
Or I would got to both serveres to the folder apps inside runtime folder and search for port numbers. For sure you will fimd duplicates.
To allow multiple apps listen to the same port like 80 or 443 you need Domain project with this http listenet as shared resource.
I am trying to set up a client-server EJB using two different machines on my network. while installing WAS server it prompted me to add admin credentials, so LTPA is enabled (hope it enabled SSL). Now on client EJB deployed WAS server I have to configure the outbound IIOP SSL certificate(Correct me if I am wrong on this). But unfortunately in the server WAS admin console I can see SSL Signer certificates cn(Host/domain) parameter as localhost. the same "localhost" is arriving when I try to "retrieve from port" in client EJB WAS server.
I have attached the "Retrieve from port" screenshot
Client WAS retrieve from port action
Even I have tried changing the hostname in the server WAS under the Server-> Communications -> Port to IP address instead of localhost.
I expect it should bring domainname.ipaddress
"Retrieve from port" action always brings "localhost" from the remote server
As per the comment by #Gas, I am following this below link
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/tsec_sslreplacecell.html
will update in short
I have setup a test VM and I am trying to get FTP via FileZilla working and connect an IIS website to an external WCF service. Neither are working, I have tried disabling the windows firewall to rule that out as well.
I have setup endpoints as below.
Incoming
Outgoing
i have just set up the FileZilla server on Azure VM.
That is what i did:
1) Install FileZilla with default settings
2) Set up the passive ports range. In my case it is 60000-60000.
3) Created outbound/inbound exceptions in firewall to allow "FileZilla Server.exe"
4) Using Powershell (i think that can be a problem, because there are some nuances when you create it on Azure portal):
Add-AzureAcccount
Get-AzureVM -Servicename "myvmcs"-Name VM1 | Add-AzureEndpoint -Name FTP- Dynamic-60000 -Protocol TCP -LocalPort 60000 -PublicPort 60000 | Update-AzureVM
5) In FileZilla server settings, i have added user, shared folder and in Passive mode settings i set "Use the following IP" into the domain name of the VM.
Tried to connect it using a few different clients, and it works.
I currently have a WildFly 9 cluster up and running with access to my application over port 8080, I would like to set up SSL and have access only on port 8443, but I cannot seem to find any documentation for where the security realm and https listener are placed in Domain mode.
I have the keystore and certificate all set up and was able to get https working in a demo using standalone mode, but I need to be able to do it in domain mode.
Can anyone help me out and share how they've accomplished this?
Solved it! It turns out for some reason JBoss was not registering my Security Realm and HTTPS listener. To do this you need to use bin/jbosscli and the commands:
RUN THE "CONNECT" COMMAND FIRST
/host=master/core-service=management/security-realm=SSLRealm/:add()
---where SSLRealm is the name of the realm
/host=master/core-service=management/security-realm=SSLRealm/server-identity=ssl/:add(keystore-path=Keystore.jks, keystore-relative-to=jboss.domain.config.dir, keystore-password=password)
---this assumes the keystore lives in the domain/configuration directory
Restart the server.
I then ran into issues figuring out the command to register the HTTPS listener, but I found the WildFly web console at serverURL:9990 has a way to do it too:
Once logged in to the webconsole
Configuration->Profiles->for each profile which is used->Undertow->HTTP->View
From there
HTTP Server->default-server->view
Finally
HTTPS Listener->ADD enter a name like: default-https, Security Realm: the name chosen for the security realm (for this example SSLRealm), Socket Binding: https and click save
Restart again
You should now have access at your serversURL:8443
To set it up on slave servers you should only need to copy the keystore to each slave servers domain/configuration and then add the security realm replacing /host=master/ with /host=slave/ in the command. And then restart the server.
Double check the Domain.xml file on the slave has the https listener you created originally in the webconsole (it should automatically be put into all of the clusters domain.xml files)
I am using Mule to expose a web service and deployed it on AWS . It's working fine locally. I can use SoapUI to test http://localhost:8087/hello. But if we call from outside using the host of AWS: http://xxx.xxx.com:8087/hello, it will show connection error. We've opened the port 8087, what else do we need? Thanks!
If you have defined "localhost" in you mule configuration file mule will only listen on the localhost interface. Change the host in your inbound endpoint to 0.0.0.0 to bind to all available interfaces or explicitly specify the IP you want to listen on for incoming requests.
If this doesn't fix it please verify firewall settings again and then post more information such as relevant parts of you mule configuration file.