I'm trying to generate a plugin-cfg.xml file for IBM HTTP Server (IHS) to point to a WebSphere Application Server (WAS) environment. I've tried using several commands and tools to generate the file, but they don't seem to be working for my specific environment. Can anyone recommend a reliable way to generate the plugin-cfg.xml file for IHS on my system? I'm running WAS version 9.5. Any suggestions or guidance would be greatly appreciated. Thank you!
We tried several commands and options to generate a plugin-cfg.xml file for IBM HTTP Server (IHS) to point to a WebSphere Application Server (WAS) environment from the command line. However, these commands did not work as expected or were not applicable for your specific environment.
You didnt write what did you try and how it is not working.
Brief solutions are described here: 3 ways to generate the plugin-cfg.xml.
If you want to do it via cmd line this should work for you:
app_server_root/bin/GenPluginCfg.sh
You have detailed description here - https://www.ibm.com/docs/en/was-zos/8.5.5?topic=SS7K4U_8.5.5/com.ibm.websphere.base.doc/ae/rxml_genplugincfg1.htm
Related
I need to get response on this URL:
https://[host IP]:8088/api/admin
I tried so many different configs so you might see extra stuff commented out.
I can easily access the web page, the only issue is, I cannot call admin api from application. No response in this regard.
Here are logs and config
https://pastebin.com/42pSg9yN
This is an AWS instance with Ubunutu 16.04
I have tried following this stackoverflow Answer too and also followed the official DOC too.
How to call ejabberd Administrator API
https://docs.ejabberd.im/developer/ejabberd-api/simple-configuration/
If there is anything you need to get a better understanding, Let me know.
I think that your configuration file have some conflicts.
Plus the REST endpoints for admin is "/api" not "/api/admin".
If you have just installed ejaberred, I'll suggest you to do a clean installation using the official linux installer (not apt-get).
The installer is interactive and will generate most of the configurations for you.
Thanks
I'm trying to do some clustering testing and I am setting up multiple RabbitMQ services on a single Windows machine. I am able to set the environment variables RABBITMQ_NODENAME, RABBITMQ_SERVICENAME, and RABBITMQ_NODE_PORT then run RabbitMQ-Service Install to have a new RabbitMQ service installed under a different name.
My question is regarding the configuration file. Based on what I read on the RabbitMQ site, the configuration file defaults to the %AppData%\RabbitMQ directory.
I'm just having trouble trying to understand how it should be setup so I can have 3 instances of the service running with their own configuration.
Do I run the installation under a different local or domain account so it gets placed under a different %AppData%\RabbitMQ directory or can I add a directive to the service to look in a particular directory for the configuration file for that particular service?
Also, how does RABBITMQ_BASE come into play? Is that only for data and log files or does that also apply to the configuration file? I'm not sure if once I have the service setup with BASE defined as a specific path I can place a new rabbitmq.config under the root of that path.
Please confirm and provide any additional assistance. Thank you in advance!
For now I'm testing on Windows but I plan on converting to linux once I have this all working correctly and understood. Unfortunately, I've inherited the current environment and it's already installed and running using Windows servers. They just wanted me to setup clustering for it so I'm trying to simulate the cluster on my workstation.
Nevermind, I found out what I needed. The environment variable RABBITMQ_CONFIG_FILE can be used to override the location of the default config file.
http://www.rabbitmq.com/relocate.html
You can run multiple RabbitMQ instances on 1 machine without clustering. You just need to change the ports and the node name in rabbitmq-defaults, rabbitmq-env and config files. If you want them as a service you can just create them from the already configured instances.
HERE is a detailed guide on how to do that. It's pretty easy and straightforward.
I have ColdFusion Builder 2.0.0 installed and I am trying to look at the much vaunted step debugging. However, I cannot seem to get it to work as I don't have my site / JRun install setup in the naive way the examples show.
I am using version 9,0,1,274733 of ColdFusion and my configuration is as follows:-
Installed as multi-server version with Jrun here:- c:\Apps\JRun4
application files are here:- d:\websites\my.website.com
web root is here d:\websites\my.website.com\www
core library of CFCs is here d:\websites\frameworks\core which is mapped in CF as core
I have read this watched this http://help.adobe.com/en_US/ColdFusionBuilder/Using/WS0ef8c004658c1089-31c11ef1121cdfd6aa0-7fff.html and this http://forta.com/blog/index.cfm/2007/5/30/CF8-Debugger-Getting-Started and watched this https://experts.adobeconnect.com/_a204547676/p33029638/?launcher=false&fcsContent=true&pbMode=normal but I get stuck at the point after you have configured RDS and you are setting up the server for your project.
Now I am pretty sure the above is correct, when I move to the next page in the wizard I get the following:-
Now I as I understand it my Server Home should be c:\Apps\JRun4 and my Document root should be d:\websites\my.website.com
This all looks like it is going to be fine until you actually try and debug when I get
followed by
I can confirm that the server is running and RDS is enabled as in the RDS Dataview I can see all my databases.
Any help would be gratefully received as this is very frustrating and the documentation is very lacking.
There is a video tutorial as well that you may want to check and see if that helps. http://blogs.adobe.com/anand/2011/01/learn-how-to-debug-coldfusion-applications-using-coldfusion-builder-2.html
You need to specify the RDS username/password and the "application server name". If you are using the base instance that was installed when you setup the multiserver install of CF that is "cfusion", otherwise its the name of the instance you are using.
The RDS username is most likely "admin" unless you setup custom users for RDS. The password is the RDS password you specified when you installed CF.
I have a need to be alerted via email of error messages in our JBoss logs. JBoss is running on a Windows 2008 server. I'm familiar with logwatch utilities on Linux, but I haven't found a well supported solutions for Windows. Does anyone have any recommendations?
Also I'd like to steer away from something like rsync'ing logs to a Linux log server which would run Linux log analysis scripts. We'd like to keep the number of servers in our environment as low as possible. Thank you!
You can use log4j SMTP appender. The details of configuration are described here
I want to setup two Hudson Masters on the same Hardware. This will make administering Hudson easier, since both servers are used by two different (and independent) teams.
So far I tried to install one server as a service. I verified the installation and it is running ok. I than copied the installation into another path and changed the service information (different service Name and description) and the httpPort. I then create the service, once using sc.exe create and once using hudson.exe install. In both cases the server started. However, the configuration page acted goofy. So this approach is either not working at all or I missed another configuration file.
Does anyone has an idea how to accomplish this?
I tried the same approach as documented in the question but avoided the copying of the original installation. So I created two folders and put a copy of hudson.war in it. Then I performed the following steps for both folders.
Start Hudson with java -jar hudson.war
Installed Hudson as a service using the web UI
went into the Hudson Base Dir and ran hudson uninstall
modified the port and the Service information in hudson.xml
installed the service through command line hudson install
Now I have two services and the first quick test looks promising.
May I suggest:
run two instances of Tomcat
have each Tomcat running on its own HTTP port
deploy HUDSON.WAR in each Tomcat
set CATALINA_OPTS for each Tomcat to point to a different HUDSON_HOME