I'm new to Websphere and trying to create a cluster Websphere 8.5 with IBM Http Server as the webserver. My topology is different from all the examples provided by IBM :
I have 2 physical machines : machine A and machine B.
On machine A : deployment manager + app server A + HTTP Server + HTTP administration server + webserver plugin
On machine B : app server B + webserver plugin
I have a cluster who contains appsv A and appsv B, and now I want to create a webserver on machine Afor the cluster.
I've used the "Webserver Configuration Tool" to create a remote webserver : websv for machine B. But I don't know how to do with app server A...
Am I doing wrong? Should I configure the plug-in separately on the machines but giving the same name for the webserver so that I can migrate the cfg files to one then put it on machine A?
How should I do with the "configwebsv.bat"?
Thanks a lot for your responses.
Allen
There's no reason to do anything with a webserver or webserver plug-in on machine B. The dmgr is aware of any clusters you have and allows you to map them to your webserver no matter where it lives.
Related
I am trying to create a second managed server on mine OSB domain, but due to the specification that you can see below I am not being able to do it.
I have installed on Machine 2 the following package:
fmw_12.2.1.4.0_infrastructure.jar
fmw_12.2.1.4.0_osb.jar
On the domain creation I selected the nodemanager per domain.
Since my Domain is installed on a shared FS, which steps I should follow in order to create a Managed Server on Machine 1 for my OSB domain?
Best Regards.
I have 2 x AWS EC2 instances with a node.js app. Out of the box, they come with a local mongod instance that works fine. Given the criticality of the app, I decided to spin up 2 x EC2 front ends (node js) to talk to a mongo db in another availability zone using the AWS ELB.
Full IP communication/27017 connectivity exists between all 3 nodes.
When using only 1 server to the mongo server, it works just fine. When adding both front end servers into the ELB target group, I get random 504 gateway errors.
Removing a server from the group fixes the issue.
Any suggestions on what I should look for?
In terms of how the node.js server connects to mongo, there is a config.json file that simply points out the IP and DB name required.
Thanks!
AWS Load Balancer use "round robin" mechanism to route user's requests. Does your application have way to control user sessions? If not then your first request come to server 1, then second request to server 2 which doesn't have any information to the first request may result in error. That explain why it works fine when you have 1 server only
the server uses redis (the app server) and the following components:
Node.js - Server-side Javascript-framework
Express.js - Web application framework for Node.js
Nginx - Web server & reverse proxy
MongoDB - NoSQL database
redis - Session Manager & data structure server
Socket.IO - Bi-directional communication between web clients and servers
I have built a working IBM api connect service (loopback) that provides local mySQL data to/from an angular website. I now want to move this service to an Ubuntu web server (appache) so that I can open up the website to external traffic. I have moved installed api connect onto the server and moved the project files across.
But I don't understand how to run the project so that it is available externally. When I run API connect the api is available on a local port address: Web server listening at: http://127.0.0.1:9000.
But in my webpage (angularjs) I can't call this as it tries to connect on the client machine, not server.
Has anyone done this before and if so, can you offer any advice?
You should configure your Apache as a reverse proxy, so that it forwards requests from your public ip address at port 80 (or 443 if you want SSL) to localhost:9000. See https://httpd.apache.org/docs/2.4/howto/reverse_proxy.html or https://www.nginx.com/resources/admin-guide/reverse-proxy/ if you'd like to try out Nginx.
i want to install multiple instance of jboss fuse and then integrate each jboss instance with different environment .
eg suppose we have 6 SIT env then we need 6 different jboss fuse to be connected.
and suppose we have 10 different unix user on one server and jboss fuse is install on this server now how we can install fuse on each unix user.
can we create jboss domain same as web-logic domain?
Currently we have downloaded zip file of jboss fuse from red-hat site and unzip this file and do configuration changes per environment that is we unzip file in 6 different users and integrated to SIT env.
what is standard way of doing this?
The solution for this is
Fabric
with the help Fabric we can support multiple environment without any issue.
.
You can run multiple instances
for that you would require to change in etc\system.properties
Change port for below attribute
org.osgi.service.http.port=<Port> #Every Instance should have different port
If you accessing it via putty. It is better to change sshPort as well to prevent the conflict. in etc\org.apache.karaf.shell.cfg
sshPort=8107
Last thing you would require to change is RMI Server Port in etc\org.apache.karaf.management.cfg for each instance.
rmiServerPort = 44444
We have several enterprise application to deploy on Weblogic server. As you know for each domain we could define specific port, deploy an application on that and clients could access to server application by that port. My question is about the port number standard.
Is there any standard to assign server ports number to different application, if No what is your suggestion ? Is counting method (for example) god ?!! or ...
Thanks for your replies
You can deploy your applications in different managed servers. What you have to do is create a managed server per application under your weblogic domain. During the configuration of the managed server you will be asked to give a port number. After setting the managed server your applications can be deployed on them, using the ports you have specified earlier. More information about the weblogic managed servers can be found in weblogic administration guide.