$home_url Value not updated with **company.default.home.url** - liferay

I have a scenario where I am successfully able to fetch $home_url in my vm file. But recently I updated company.default.home.url in portal-ext.properties from /web/guest to /web/abc/home. As a result $home_url started fetching /web/abc/home instead of /web/guest. Now the problem is, when i reverted back the company.default.home.url to /web/guest, $home_url still fetches /web/abc/home.
I tried restarting the server, clearing the browser cache and clearing server cache but still no luck. I can see that changes have been reflected succesfully in System properties in Server Administration section of Control Panel but $home_url is not picking up that value anymore.
I am using Liferay 6.0.6 CE on tomcat 6.0.29.

$home_url returns company home URL if present. If this not existed, then it returns the default value of property - company.default.home.url
Check for entry in table - Company in your database
select * from Company
This table has column "homeURL", if this has non null value, then $home_url indicates the same.
This "homeURL" can be updated in Portal Settings -> General, Home URL
As you mentioned its empty in your case, You need to provide value here so that it get updated for $home_url.

It could be that your configuration for company.default.home.url has been persisted to the database after your change to portal-ext.properties. This way, Liferay would always pick up the version from the database, instead of the properties file.
You can check for this value in Control Panel under Portal Settings/General if I remember correctly. If you find the value there, change it there. As it's discouraged to manipulate the database directly, you shouldn't attempt revert it to fetching the file's content.

Related

Error issuing part using Maximo integration framework MXINVISSUE

We are upgrading from Maximo 7.5 to 7.6.1. Our web service that uses MXINVISSUEInterface is throwing an exception when we try to issue a part that is marked as a spare part and the work order has an asset. The exception says "BMXAA4195 - A value is required for the Organization field on the SPAREOBJECT object." The part is not in the SPAREPART table for the asset so it is trying to add it, but for some reason the ORGID is not populated from the MXINVISSUE_MATUSETRANSType object.
I re-generated the WSDL on the new server and rebuilt the solution, but after populate a new required field, I still get the same error.
Is there a system property that must be set. It works in 7.5 writing the record to MATUSETRANS and SPAREPART.
This sounds like a bug, so you might raise a Support Case with IBM about it. For a workaround until IBM releases a fix and you install said fix, consider the following options.
Can you set the Default Insert Site for the user using the web service?
Is it practical to put a Default Value on SPAREPART.ORGID?
Create an automation script called SPAREPART.NEW that will somehow figure out an ORGID to use. To "figure out", my first would be to check if mbo has an owner that has an ORGID and, assuming it does, use that.

Refresh data from oracle database on jsf page refresh in adf 12c

I am using jdeveloper 12c to build fusion web app with oracle 12c database.
My project is running fine in browser and also can be accessible on other system's browser via static IP.
When someone is accessing application in browser and enter some data in table, it saves in database but it doesn't reflects on my browser even after refreshing page until unless i rebuild my project.
How can i get data without rebuilding my project (I want to fetch all updated data through page refresh).
I don't want to create a method for this.
Browser page refresh doesn't call data querying. You need to call Execute on needed iterators. For instance you can start a taskflow with Execute method before showing user interface.
I am not sure but, use Execute of that particular VO after commiting the data.Before using Execute in java code you have to add Execute in page deinition or go to that particular table in page. use binding property under property inspector. create the binding as given #{backingBeanScope.popupBean.refresh} and call it in java as like this to refresh the data while saving in DB 'AdfFacesContext.getCurrentInstance().addPartialTarget(refresh);'
Only you need to add EXECUTE button from that specific table (of which you want to refresh data) operation in data control tab, and you can label it as REFRESH button.

Managing state changes caused by an API patch

I have a data table that is populated GUI -> API call -> node backend -> loop back -> mongo db. Just displaying data works fine using NGRX state management. I use a modal dialog to edit one of the fields, trigger a submit change action, call the relevant patch API and successfully update the relevant record(s).
In order to reflect this changed record in the GUI. I call the get API when the SUCCESSFUL_SUBMIT action comes. This works fine, but i think it's not the correct way to do things with NGRX and I worry that this will cause maintenance problems in the future.
So my question is, how do i reflect the changed state in the GUI. Please note that I do not wish to display the change in the GUI until i know that the DB patch was successful.
The image shows the table with the console log having just submitted a change to auto archive.
This seems fine to me, but:
if the POST object reflects the GET object and if the server doesn't modify properties, you could update your store without the extra GET
the POST response body could include the object to prevent the extra GET

SSIS Woes: Dynamic OData Connection for Same SharePoint List on Multiple Sites

I am having an issue using an OData SharePoint List Source with a dynamically changing connection string (inside the OData Connection Manager). The OData Source inside of my Data Flow Task fails to validate with the error message, “Cannot acquire a managed connection from the run-time connection manager” when executing the DFT from a parent package.
I have done some extensive Googling, and combed the forums relentlessly; however, I have not found anything that seems to offer a solution to this problem. Any help figuring out a solution would be greatly appreciated!
Here is the general flow of the main SSIS package:
Truncate staging table
Get all Site Collection URLs and their GUIDs from SQL Table
Execute Package Task for each site collection (foreach ADO loop container)
Extract data from UserInformationList (OData source)
Add a column for the GUID of this site collection
Load the data into staging table
etc. . .
Main Package:
Child Package Control FLow:
E-L UserInformationList DFT:
Package Output With Error Message:
When testing the entire solution, everything (tasks, parameters, variables, etc.) behaves properly until 3.1(see above), when the OData Source fails during validation. The only aspects of the source and connection manager that change are the URL and ConnectionString for the connection manager; the specific SharePoint list that I access on each site never changes. When the solution enters the child package, the URL and ConnectionString for the Connection Manager are properly set, prior to entering the DFT.
When testing the child package via the Execute Package Task, using hard-coded parameter values, the child package fails to validate.
When testing just the child package, there are no errors and the list information is stored in the database, as expected. However, with individual testing, the OData Connection Manager uses the default value of the package parameters.
Things I have tried so far:
Set DelayValidation to True
Changing the debugging runtime from 64 to 32 bit (and back again)
Use collection to specify the list (in the OData Source Editor)
Use resource path to specify the list (in the OData Source Editor)
Running the child package as a Farm Admin
Running the solution as Farm Admin
Other information:
SharePoint 2013
Data Tools for Visual Studios 2012
Microsoft’s OData Source for SQL Server 2012
i think you don't have access to the source sharepoint or you are not passing the right credentials thats why you are getting this error. Please use valid connection and test your connections.
I had the same issue while I was reading the URL for OData source from database. In my case, I was passing old value for URL which has changed in the SharePoint side that is, the DB had URL value http://sharepointsite/News but the actual site was modified by user to http://sharepointsite/NewsUpdated
So, check the passing URL value in your case in case you still having this issue
I had the same issue, and it looks like at the moment of starting for loop container, you need to provide a valid value for the URL variable, it will be overwritten this or the other way, but if I would go with "0" or null I would get the same error as you

Kentico Forcing New Website

I have backed up the Kentico Database and website from one of our Live servers and placed it within our Dev server and configured the website in IIS.
When I navigate to the website, it currently asks for New installation.. Whereas it should just show me the current website.
How do I get it to show the website?
EDIT
The following error occurs when going ahead and creating a new instance with the restored Database:
Restore the backed up database and add database connection string to the web.config of the application. Simple as that :)
Who or what is set as the DB objects owner/schema in the DB? Does this match the setting in Site Manager (or, CMS_SettingsKey table)? I would make sure these two match.
Another option is that the connection string was not initialized by .Net - I would do a dummy change in the web.config file to force the app restart and/or also clearing the .Net cache.

Resources