I have two servers. They are supposed to be identical. I also enabled the RESTful services on both servers. On one of the server, It gave me a 503 status error code saying the password for apex_pu is invalid, expired or account is locked when I tried to use the sample API in oracle.example.hr.
https://hostname/ords/Schema Alias/hr/
However, the same sample API works fine on my other server.
I checked the apex_pu.xml file in conf folder under product folder and compared the two apex_pu.xml on both server. I found that the apex_pu.xml file on the failed one is missing standalone = "no". I installed standalone mode before to look into some issues related to Oracle RESTful services. Then I left it like that ever since. I'm not sure if this is related to the issue that I'm currently encountering, but I'm trying to eliminate this difference by reverting it back to ORDS on Apache. I think this is the first step to troubleshoot my issue. Can anyone tell me how to revert this?
Commands that I used to enable standalone mode:
Java –jar ords.war configdir
Java –jar ords.war (to start standalone oracle)
Java –jar ords.war standalone (to start standalone oracle rest api)
failed one:
<?xml version="1.0" encoding="UTF-8"?>
normal one:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
Related
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
I have a web application (maven) which uses mariadb as a database and I'm deploying the app with Tomcat on a Raspberry Pi.
Since I wanted to create and deploy a similar version of the original application. I slightly modified the application (which has originally been created by another person). The only change that I made to the application was to connect it to another database instance on my Raspberry Pi, by changing this line:
spring.datasource.url=jdbc:mariadb://localhost:3306/myDatabase2_db
Of course, I created a database by the name of "myDatabase2_db" on the Raspberry Pi in advance. And I also changed the name of the WAR-file to MYAPP2, so that the two applications have different names.
My goal was to deploy the original application and the modified version as completely separate applications (with different databases), but on the same Tomcat instance on my Raspberry Pi.
My observations so far:
(1) If I stop the "original" application in Tomcat and AFTERWARDS deploy the "modified" application and try to run it, it works without any issues.
(2) Only when I try to run both applications at the same time in Tomcat, it always displays the following error in tomcat:
FAIL - Application at context path /MYAPP2 could not be started FAIL -
Encountered exception org.apache.catalina.LifecycleException: Failed
to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/MYAPP2]]
So far, my guess is that this happens because I used the same code basis for both applications and only changed the above-mentioned 1 line of code. Do I for example have to change something in the pom.xml file or somewhere else?
The problem is just that I didn't create the original application and only have a very limited unterstanding of maven, mariadb and tomcat. I would really appreciate if someone could explain what is happening and how to resolve this issue.
Thanks in advance!
I am running a glassfish 3.1.2 server with ADF essential libraries added to it. The server runs fines, deploys all my applications without any errors but serves up xml code instead of web pages. I have to say that the rich client faces demo runs fine. So there must be something wrong with my applications' EARs. I have tried taking the RCF demo's libraries to manually package them in my war inside my ear without success.
Does anyone have an idea of what could be wrong?
I have a unmodified straightforward glassfish 3.1.2 downloaded from Oracle and configured as per Oracle's instructions to run ADF applications (hence the demo works), adf essentials downloaded from Oracle as well. Versions of adf essentials match the version of jdeveloper (12.1.2) Here is the document declaration from the outputed xml code:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html>
<f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
xmlns:dvt="http://xmlns.oracle.com/dss/adf/faces">
I tried adding different libraries to the application deployment settings to no avail. I have tried none-to-all of them without success. (this took a long time to try)
Do you have any suggestions for me to check in order for the glassfish server to serve webpages instead of brute xml?
Best regards
Marc.
I stumbled across the answer:
I needed to add /faces in front of the webpage. Thus the url looks like
http://is-marca-v:9090/HRSystem-ViewController-context-root/faces/DeptEmpPage.jsf
and not
http://is-marca-v:9090/HRSystem-ViewController-context-root/DeptEmpPage.jsf
Have a nice day to you all.
I am here to get some expert advice on deploying applications to WebLogic Production Server.
Is it a best practice to use Admin Server Console for deploying and redeploying applications in production. Actually I am deploying to a cluster having two managed server instances.
I have encountered this issue while i am redeploying application in the production. When i am deleting existing .ear file and adding updated .ear file will put the updated .ear file into prepared state. I can not make it Active state using Admin Server Console. If i try it will through some exceptions. But after some time it automatically goes in to active state, but i don't know what is happening inside. Sometimes i restart the server to make it active. Could anybody explain me what is the procedure when deploying application and redeploying applications in weblogic
Thanks in advance for any Help...
Generally WLST (WebLogic Scripting Tool) is used to deploy the applications. Administration Console can also be used to deploy/upgrade the applications but if there are many environments that need to be upgraded then WLST (which works like a command line tool) is much better option.
Get an overview of WLST to know how to use it to deploy/undeploy/upgrade applications.
Check out "Understanding WebLogic Server Deployment" and the "Redeploying Applications in a Production Environment". There are different factors that affect redeployment of an application which you might be running into.
http://docs.oracle.com/cd/E23943_01/web.1111/e13702/understanding.htm#i1057116
http://docs.oracle.com/cd/E23943_01/web.1111/e13702/redeploy.htm#g1039635
Additionally, there is a WebLogic Plug-in for Maven in more recent WebLogic releases that you can use for deployments in conjunction with Maven.
I installed a java web service on a machine that accesses an Oracle DB via JDBC on the same network. The service was functioning fine for several months until this morning when I installed another applicaiton that access the database using ODP.NET. I'm trying to figure out what went wronge to cause the ORA-01017 exceptions that I'm getting. This generally means that the login credentials are invalid, but the login credentials haven't changed. I also verified it the service's log4j output that it is indeed still trying to connect to the DB correctly.
I realize I don't have much to go off of here, but I'm trying to figure out what other dependencies that. The web service came packaged with ojdbc14.jar, so that tells me that it targets java1.4, but presumably would work fine in later java versions. Not too sure about it working with later java versions, however, it was working fine until today.
Does OJDBC rely on tnsnames.ora. If it depends on how the service uses OJDBC, then I'm not sure which it is doing. I suppose it's possible I deleted the tnsnames.ora, but that is a bit of a longshot. I also tried manging Apache Tomcat (running on Win Server 2003 x64) to target different java jvm versions, but to no avail. It was initially targeting the default jvm.
Are there other dependencies that I've missed here, or any diagnostic measures I could try? THe same web service is running on another machine on the same network which I am pretty sure is configured exactly the same. Again, it was working on both machines until today, and is now just working on the one.
Tomcat targets JDK 7.
Looks like replacing ojdbc14.jar with ojdbc6_g.jar did the trick. No idea why it was the case only for 1 of the 2 machines. ojdbc6 targets JDK 6, but ojdbc14 did, and should have continued to work. If anyone has any additional insight here, let me know.