Bajr Prakash Singh Posted September 1, 2022 Share Posted September 1, 2022 After installing WF client , tomcat 8.0.21 seems to be installed but 'localhost:8080/ibi_apps' does not loads and throws 404 error.I checked the Tomcat logs and it shows failed to connect to port, but the port is open.Has anyone seen this before? Link to comment Share on other sites More sharing options...
Ron Moore Posted September 6, 2022 Share Posted September 6, 2022 I would try http://localhost:8080 - assuming you are using the browser on the server where WebFOCUS is installed. If this loads, Tomcat is running and is accessible. I would also look closer at the logs. Errors loading ibi_apps are often because Tomcat cannot connect to the WebFOCUS repository Link to comment Share on other sites More sharing options...
Bajr Prakash Singh Posted September 6, 2022 Author Share Posted September 6, 2022 Hello Ron, http://localhost:8080 is running. Regarding repository connection issue....you are right, I already checked the logs before and found issue in event log. But the weird thing is I am able to connect to Repository DB using the required credentials but for same credentials WF is showing invalid UN/PW error.I am able to connect to the DB server through Linux server so its not the network issue.Any idea what is could be? Link to comment Share on other sites More sharing options...
Ron Moore Posted September 6, 2022 Share Posted September 6, 2022 Hi Bajr. I would take a look at ibiWebFOCUSxxconfiginstall.cfg and check that the repository configuration is correct. Make a backup before you make any changes:IBI_REPOS_DB_USER=wfuserIBI_REPOS_DB_PASSWORD=[AES128I]71GTY%2F6Rix0IoFqxlIMnXA%3D%3DIBI_REPOS_DB_DRIVER=com.microsoft.sqlserver.jdbc.SQLServerDriverIBI_REPOS_DB_URL=jdbc:sqlserver://TIBCO-sqlhost:1433;DatabaseName=wfrepos9You can change the password in clear text by removing the '[AES128I]', so it would look like this: IBI_REPOS_DB_PASSWORD=mypasswordAfter you make this change you must restart Tomcat. My guess is this is not a new repository as I would have expected the Client install to fail. I would also check that you have the correct port for your repository. Note, the repository connection uses JDBC and sometimes that port is blocked Link to comment Share on other sites More sharing options...
Bajr Prakash Singh Posted September 6, 2022 Author Share Posted September 6, 2022 Hello Ron, I have already verified this config file and all information related to repository connection is there.Since my WF version is 8105m and I am using oracle DB, IBI_REPOS_DB_URL=jdbc:sqlserver://TIBCO-sqlhost:1433;DatabaseName=wfrepos9 changes toIBI_REPOS_DB_URL=jdbc:oracle:thin:@TIBCO-oraclehost:1521:wfrepos9 Link to comment Share on other sites More sharing options...
Ron Moore Posted September 6, 2022 Share Posted September 6, 2022 Bajr. This is a new 8105 install? If it is not a new install, what has changed? If it is a new install, I would have expected the install to fail to create the repository. You could check the install log and that the tables were created in the Oracle schema. I would test the jdbc connection to Oracle from the server where the WebFOCUS Client is installed - ping, telnet, jdbc test tool. I would also open a case with support and provide the Tomcat logs Link to comment Share on other sites More sharing options...
Bajr Prakash Singh Posted September 8, 2022 Author Share Posted September 8, 2022 Hello Ron, this is a new install but we are using a copy of existing WF repository to configure it. I checked the connection between db and new wf server and it seems to connect without any issue.I have opened a case with TIBCO and provided relevant files Link to comment Share on other sites More sharing options...
Ron Moore Posted September 8, 2022 Share Posted September 8, 2022 Hi Bajr. I am sorry you are still having problems. Be sure you provide the latest Tomcat logs in the case. The log should give some clarity if this is a connection problem or an authentication problem. That is step one. If it is a connection problem, be sure you are testing the connection to the database using jdbc Link to comment Share on other sites More sharing options...
Bajr Prakash Singh Posted September 27, 2022 Author Share Posted September 27, 2022 This issue has been resolved and the problem was with oracle client version. Once the relevant version was installed the authentication problem with respect to DB credentials was resolved. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now