i've got one issue with Websphere Portal application. The situation is when we removed one uploaded image file of Portal application from WAS intsalledApps folder path directly, that file would be regenerated by itself after we restart Websphere Portal application server. It seems that image file has been sync from somewhere else. But that websphere portal has been deployed within websphere standalone server, no dmgr node but just one application server profile. So i don't understand why that file would come out again? where is it from?
Thanks in advance
there should be a couple of directory where installation keeps their file
D:\IBM\WebSphere\wp_profile\config\cells\nodename\applications
and the second one
D:\IBM\WebSphere\wp_profile\installedApps
check both of them, if you confirm that there is no deployment manager in this configuration.
Related
Recently I ecountered situation where my WebSphere's admin console stop responding (tired to open it and got timeout). It happened after I've made some changes and saved them.
All the WebSphere application server and nodeAgent was working (checked in serverStatus.sh -all). I could still access my Web Application.
Is there a way to restart just admin console with a script or do I have to restart everything?
In my case the WebSphere works on linux.
I found a solution if someone will be interested. My dmgr process couldn't stop so I have to kill it manualy. Then I had to run startManager.sh script in IBM websphere dmgr location. It's done without restart the whole server.
I've created one VM windows 2016 on Azure and installed Weblogic 12.2.1.3 and SQLServer2016.
Deployed an ear file and can get to the application login page.
I've configured IIS with this my application to have https url. I followed everything that we usually do on our on premises servers but I'm getting a weird error. Does anybody can help me please?
According to your description, I suggest you could try to use below steps to solve this issue.
1.Ensure that the path to the ISAPI DLL is correct
Open the IIS mangement console and locate the web sites and find the hanlder mapping feature.
Then you find the myapp_iisproxy handler in it and check the executable's path is right or not.
2.Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
3.Verify permissions for the DLL. Make sure your application has the permission to access the dll file.
I have a war file which I deployed and ran in tomcat. Then I deployed it in websphere from admin console. The status of the webapplication is seen as started along with the built-in web applications such as "ivtApp", "query", etc. Now from this link:
Heading
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Frins_portnumber.html
It looks like the port number for web application is 9080 for http. I tried to run the application using the link:
http://{localhost}:9080/spring3HibernateMaven/index
(I am using "{" because this website didn't allow typing localhost)
the context root being spring3HibernateMaven. And I get page not found error in the browser. So I thought there must be something wrong with my web application. Hence I tried to run their web application:
http://{localhost}:9080/ivtApp
Which gives the same error. Even
http://{localhost}:9080/
gives the same error. I assume it should show something for this url as is shown from tomcat.
So how can I run the/any web application in websphere? FYI, I downloaded the latest version of websphere from their website.
Thanks
ivtApp has context path "ivt", so you need to use host:9080/ivt
Btw, you can find context path setting in websphere\application control panel
In our project we have installed both the “WebSphere application server” and “WebSphere Process Server” in a single machine. But we are unable to run both the server at a same time.
WebSphere Process Server is mounted on top of WebSphere Application Server, so while we are running the process server the default WebSphere application server instance is starting with the process server. So after that if we try to start the separately installed WebSphere application server, we are getting error that one instance is already running. Please suggest how to avoid this conflict and run both the process and application server in the single machine?
Both are using the same port. We already renamed the server name of the separately installed WebSphere application server with “server2” and Process Server’s application server name is “server1”
Please share your suggestions
You need to create separate profile. You don't have to install WAS first, or install it again, if you don't want. You may use Profile Management Tool from your installation to create new separate profile for WAS (choose Application Server profile type, not Process Server).
If you want complete separation e.g different versions (like vX of WPS and vY of WAS), or different fix pack level, you will need to do full separate WAS install.
Websphere Process Server extends Websphere Application Server (WAS), so you should install WAS first. Websphere Process Server (WPS) install should be made on top. When installation is complete you will be able to create WAS and WPS profiles on this machine. WPS profile always include WAS libraries and can be managed exactly the same way as WAS.
If you want separate servers, you should create two profiles, one for WAS and one for WPS.
You will be able to manage them separately.
I'd developed a WCF Service using netTCPBinding and embedded it in a Windows Service.
The configuration data of wcf is located in standart app.config file.
After that i had created an installation project and include my code (wcf in widows service) there. So I have the setup.exe file to install my windows service with wcf on board.
I've installed the windows service to my local drive (C:\Programs Files...\Service) and started it using the services page (pane) of my OS.
It works fine.
The app.config file was copied to the local drive and located across the same folder (C:\Programs Files...\Service).
One day i've tried to change the part of my endpoint address (PORT) in app.config (C:\Program Files...\app.config) and restarted the service using an appropriate page of services (services.msc) in windows.
I thought that the service would be working on another port (I've setted in app.config) but i was wrong. The service continued working on the previous PORT. As I've understood, it continued working using the copy of starting version of app.config. It stores the copy of this file in another path.
I need the ability to change the app.config file and get the updated windows service after it's restarting.
I am going to let my users set the specified port number where the developed wcf service will listening to.
Where am I wrong? Could you help me to find the solution of my problem?
Thank you for your help.
At the risk of stating the obvious...
How literally do you mean that you changed a file called app.config? Do you mean that you changed the file called [exename].exe.config? 'Coz if you changed a file called "app.config" in the installed-to folder, that file won't have any effect. You need to make the change in the file called [exename].exe.config.
--Shawn.