I'm trying to deploy a JSR 286 portlet in websphere portal.
Deployment goes fine but when I try to access a resource url directly I get the following:
Error 403: Direct portlet access prevented by WebSphere Portal
I'm very new to portlets and websphere.
Any ideas what could be wrong?
This is the standard default for portal, if you install it THROUGH portal, if you want it to be accessible I would recommend pre-deploying the portlet as a war into websphere appserver then registering it to portal.
http://www-01.ibm.com/support/knowledgecenter/SSYJ99_8.5.0/admin-system/j2ee.dita
for more information.
To access a portlet you need to put it on a page when it is installed through portal, all portlets are viewed in the context of being on a page
Related
When I start jboss server with liferay (6.2), everything works. I can access the portal, access the administration section of liferay, even war deployed outside of liferay (activiti-explorer,...)
But when I hot deploy a war with portlets, jboss is still running but I can't access anything, even war deployed outside of liferay.
In chrome, i get a ERR_EMPTY_RESPONSE for any url pointing to the jboss server.
In the jboss console, there is nothing showing up after liferay telling the war has been deployed.
Could you help or indicate me leads to resolve my problem?
Thanks in advance
Is it possible to deploy the J2EE Module only into Bluemix? Because what I did now is I deployed the entire whole WebSphere Application Server. But then, what happen is that I can't run the application locally anymore because the server.xml configuration has been changed to use the database service selected in the Bluemix platform.
Here's a snippet of the current setup. If there's another way, can someone tell me how
You can publish EAR and web modules directly to the Bluemix server in Eclipse. The Tools also support incremental publish of both type of modules.
To deploy the application, you can simply right click on the Bluemix server on the Servers view and select the Add and Remove option. For details, you can refer to Publishing an EAR file section of the documentation. The steps for publishing a web module is the same as publishing an EAR module.
Note that publishing the module directly does not allow you to include Liberty server configuration, i.e. the server.xml, as part of the publish operation. In case your application require specific server configuration settings, then you need to continue to publish the entire server as before.
I have some challenges configuring Bluemix SSO Service with a Spring application that is bundled as a jar file.
I need to understand:
If Bluemix SSO configuration is supported for a app.jar file (instead of a war). I do not want to change ths for now
Is Bluemix SSO supported in Tomcat application in Bluemix.
I was able to successfully test SSO with a war file, but it breaks for a jar file.
The Bluemix Single Sign On Service, supports Node.JS and JAVA(Liberty) Applications.
If the .jar is created via JAVA(Liberty) and has a Server.xml file so it can read the oidc configuration, it should be able to work.
If there is no Server.xml file then the SSO Binding will fail.
I have an ear maven project which contain an ejb moudle which has 4 stateless session beans annotated as web services. I was doing all my testing in Glassfish and have never complained when i deployed the ear file. Glassfish published the ejb's as web services and generated the WSDL and life was pink.
However, when i tried to deploy the same ear in WAS 8.5 nothing is published, and i can see the status of the service has x icon and when i hover it, it says that the service endpoints are not listening but the deployed asset is running.
I have spent a 3 day trying to solve this but no progress.
Have anyone faced such a problem? how you solved that and managed to publish the ejb as a web service?
For anyone later who may face the same issue. there is a utility in websphere/appserver/bin called endptEnabler. You must run it on your ear before installment in the app server.. Good luck for all
while deployment of webservices you have to enable the check box "Webservice" available in deployment settings in websphere
Currently I have set up liferay 6.1 to weblogic server 10.3.5.
Now I can use liferay portal from weblogic server.
After that, I am trying to deploy the other sample portlet to liferay on weblogic server.
I would like to know how to deploy that sample portlet?
Another problem is that I want to develop portlet applicatin that use JSF 2.0 for view and EJB 3.0 for business layer. Can I deploy that portlet applicatin on liferay with weblogic server. Is that possible. If possible, Please guide me.
Keep in mind that Weblogic only supports hot deploy for the admin server. There are 2 import settings that liferay needs for hot deployment on weblogic. You need a setting for the weblogic dest dir and a liferay home setting that refers to the root folder of the Weblogic domain. The env.DOMAIN_HOME doesn't work in WLS 10.3.6, that's why you need to set the home location with the full path.
Normally Liferay has a "deploy" folder that it monitors for .war files. You just copy your portlet .war file to that folder, and Liferay deploys it. You can change location of that folder by configuring "auto.deploy.dest.dir" setting in portal-ext.properties.
According to documentation, on WebLogic by default it has this value:
auto.deploy.weblogic.dest.dir=${env.DOMAIN_HOME}/autodeploy
Also another part of documentation mentions that on some containers portlets hot deployment may not work or be problematic. But I think this is not about WebLogic.