I want to setup Portal pages on my WebSphere Portal Server (WPS), which were already setup by someone else on his desktop. I have tried with the Export Portal page feature to export the Portal page from my colleague's desktop. exportPage.xml is created. I tried importing the same on my WPS, using Import XML feature. But gives below error
An error occurred while retrieving the resource with object ID
3_G5UKGAEUGB8B50A64RRL3H10N7. [portletinstance
5_G5UKGAEUGB8B50A64RRL3H1OO1]
The portlet reference ID which this XML is pointing to is present on my WPS.
i.e. I have deployed the same EAR ( which contains the set of portlets ) which my colleague has deployed on his WPS.
What could be the solution ?
This export / import saves a lot of time in setting up a new environment.
You have to identify the issue first.
If there is no additional information about the issue inside of
WAS_HOME/wp_profile/logs/WebSphere Portal/SystemOut.log
you should enable traces using WebSphere Portal console for XMLAccess
com.ibm.wps.services.xml.*=finest
more information should be in
WAS_HOME/wp_profile/logs/WebSphere Portal/trace.log and give you more insight
I just tried similar steps without an issue. The way you used it sounds reasonable
Related
I am new to HANA Cloud portal. I have created a standalone SAPUI5 Application following the below steps:
SAP HANA Cloud Platform
I have not set any destinations since I am using dummy data for now. The app works fine standalone but when I add it to a site in the HANA cloud portal the application fails with the error "could not open App.Try again Later". I have followed the below steps. Please let me know if I have missed put anything:-
1) Created a site from the site directory screen with a blank site temppplate.
2) Next I selected the app I want to add into the site from the account apps section in the left navigation inside the flpportal service and added it[using the forward icon].
3) Then when I try to add it as a menu configuration it shows up in the list and gets added but when I publish the site I get the above error mentioned.
Am I missing any step or doing it wrong altogether? BTW I am using a HANA trial account for now.
Also, I would like to know whether this is the correct way to do it. Also, any documentation on the same will be helpful
Adding the error description. The name of the app is Kpidemo:
When I try to deploy application to bluemix, I get following error
Error: Host taken error. A different mapped application URL is required before pushing or starting the application.
Though If I download a default application created bluemix, download the same and import in eclipse and then redeploying application works fine. I am sure I must be missing some key steps, wondering if someone can point me to the link that has those details or missing step.
Use the screenshot below to ensure that your mapped URL is correct:
according to the posted error you just set a wrong URL for your app's mapping URL: just check on Eclipse Server view, you should have Bluemix Server item, double click on it to open, it should show your server configuration, go to Applications and Services tab, here you could find you app listed; now double click on it, it should open you app properties, check on Mapper URL property under General configuration tab.
Otherwise could you provide some details more about the configuration used on Bluemix Eclipse plugin?
As per my understanding..
application name is globle. what ever application name using that already used by someone.
try to change Name.
ex:- cocacola.mybluemix.net change to cocacola429.mybluemix.net.
it worked for me.
currently I am working with mule esb in cloud, to achieve this I am using free trial version of Cloudhub. FYI, I am new to cloudhub and right now tring to deploy my mule application there. Unfortunately, everytime I tried to deploy my application, it can not be deployed.
I have tried 2 ways to deploy the apps.
The first one is from the Mule Studio, by following this documentation:
Deploy Apps to Cloudhub From Mule Studio
When I tried that way, I got following error:
I guess it was because of the proxy.
The second way I tried is by deploying it directly from the cloudhub.io, by following this documentation:
Deploying Apps Directly From Cloudhub.io
But, when I check on the deployment section, I found out, that my application is not uploaded. Then I tried to upload it again, update it, and run the application, but it seems that the application still not uploaded and the change I made is not applied.
Here is the error I got:
FYI, before I upload the application to cloudhub, I compressed the application folder into zip file.
How can I solved this problem? Do you think I did something wrong when deploying it? Thanks in advance.
I too faced similar problem, when deploying application in cloud hub, using Mule 3.5. My application inserts Contacts info (FirstName, LastName, Title, Email etc) from CSV file in Salesforce "Contacts" object. With proxy details configured, my application was running fine in local machine but when deployed in cloud hub, I was getting "Unknown host Exception. Root exception in proxy (something similar to this) " exception.
What I did:
I have removed proxy details from Salesforce connector and re-compiled and deployed in cloud hub. When I tested, the contacts from csv file are getting inserted in Salesforce "Contacts" objects.
Note: When Proxy details are removed, it works in cloud hub but fails in local. It seems cloud hub takes care of proxy connection and we don't need to explicitly mention it.
Regards
Ravi Nori
Be sure that you configure your http endpoint like this:
<http:inbound-endpoint host="localhost" port="${http.port}".... />
CloudHub will automatically expand http.port property to the correct value.
To make it work deploying from CloudHub you shouldn't compress your project yourself and upload but make Studio create a deployable archive: Right click on your project and then click export, select 'Anypoint Studio Project to Mule Deployable Archive' under Mule category. That will have Mule ESB application structure and should work in CloudHub.
Check your http global endpoint is like that
or you can give in properties file like http.host=0.0.0.0 http.port=8081
these values you can give directly in cloudhub properties.
From flow you can access like ${http.host} , ${http.port}
First check that domain name is available
I developed a sample application in visual studio 2010. I created an Empty SharePoint Project and gave the local site url for debugging. Checked "Deploy as Farm" as the trust level of the SharePoint solution. Added a visual webpart and also a class to the solution. I am able to build and successfully run the application using visual studio. In my local machine am using SharePoint foundation 2010 to debug the SharePoint application.
Now i want to deploy this application in the SharePoint server 2010 which is in a virtual machine.
1. I copied the .wsp file of the application i created to the virtual machine.
2. From the central administrator in the VM I created a web application and the site collection.
3. Then using Site Actions -> Site Settings -> Solution(Galleries), choose the .wsp file for uploading. it showed a "Warning: You should only activate this solution if you trust this solution. An activated solution can read, modify and delete your data. " and the activate button is disabled.
Then I tried to do same in my local machine on a different site collection. Here Activate button is enabled but when clicked it threw exception
Server Error in '/' Application.
This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'aee60282-765d-4c9f-b67a-5981f18a6d3b' failed validation, file manifest.xml, line 10, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'.
What could be this error?
The "TemplateFiles" element refers to items that will be copied onto the web server. This is allowed for farm solutions (which are deployed via CentralAdmin), but is not allowed for sandboxed solutions (which are deployed via the Solution Gallery).
When you deploy your wsp with visual studio, you deploy it as farm solution.
When you deploy your wsp from site settings into solution galery, you deploy it as user solution (sandbox solution) with some limitations :
first, avoid using out of the box visual webparts, it's prohibited !
Deploy your wsp by writing powershell script.
A good starting point here :
patrickboom.wordpress.com/2010/05/31/using-powershell-to-deploy-sharepoint-solutions-wsp-2/
Le_Fredo is correct here, when attempting to deploy a WSP file into the site collection directly under the site settings, you won't be able to. I found this article from microsoft to be extermely helpful
http://technet.microsoft.com/en-us/library/ff607688(v=office.14).aspx
Any time I try to publish my Portal project on a Websphere Portal 6.1 Server, I get the following error message:
Portal project publishing is not supported on WebSphere Portal v6.1 Server
Is that really true or have I done something wrong?
I'm trying to deploy a portal project, with the underlying goal of publishing a new theme.
Unfortunately, any time I try to deploy, I get the error message listed above from the IDE and no errors in the console.
The RAD version is 7.0.0.7.
Not sure this will help, but:
Limitation: Although the WebSphere
Portal installer contains an advanced
option to install an empty portal,
Portal Designer relies on
administration portlets for setting
access control; therefore, publishing
a portal project to an empty portal is
not supported.
Are you trying to deploy a portlet or an entire portal project? What version of RAD are you using? Any other information in the error log? (Both within RAD & on WP server) Is the error message posted verbatim?
It is possible to deploy such a project to a WebSphere Portal. I use v6.2 and deploy portlets, which are parts of a big Portal project, every day. I'm only a starter in such a stuff, but I can say that WebSphere is really buggy. You know, it is a big difference to run a deployed app "locally, in a workspace" or "on a server". I suggest you to work out with server options - administrative console.