Can anyone list out all the steps involved in migration of IFS Lobbies and related objects from one instance to another (Example DEV to PROD)?
Thanks in advance!
Solved
Migrate Lobbies across environments
+18Best answer by Kasun Balasooriya
The above error seems to be related to the bug fix 154952 ( If you are below UPD9 as the fix is released with UPD9) The solution for states the following workaround:
Workaround: You may export the Lobby as Full Format or ZIP archive and manually remove the duplicated Data Sources. Modifying the ZIP file is the easiest since it is easy to spot the duplicated data sources as they have the same file name. Open the ZIP archive and remove each of the duplicated Data Sources, only leaving just one. Same could be carried out with the Full Format XML file but, it should be carefully done since editing the XML file should not break its structural validity.
Hope this helps.
This topic has been closed for replies.
+20Hi Srikanth,
I believe you can easily perform this from the Lobby Overview screen.
- Navigate to the Lobby Overview window
- Select the Lobby to be exported
- Click on Export Page and the following options will be available:
- Select the desired export option
To import the lobbies, the same Lobby overview window can be used in the destination environment.
Hope this helps.
Thanks,
Kasun
Kasun B - https://www.linkedin.com/in/kasunbalasooriya/
+18Tried these steps on one of the custom lobby with Full Format Page option and giving me XML Parsing failed error, whilst importing:
Details:
Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> Ifs.Fnd.FndSystemException: Unexpected error while calling server method AccessPlsql/Invoke ---> Ifs.Fnd.FndServerFaultException: ORA-31011: XML parsing failed
ORA-31011: XML parsing failed
ORA-19213: error occurred in XML processing at lines 21
LPX-00245: extra data after end of document
ORA-06512: at "SYS.XMLTYPE", line 272
ORA-06512: at "IFSAPP.COMPOSITE_PAGE_REPOSITORY_API", line 861
ORA-06512: at "IFSAPP.COMPOSITE_PAGE_REPOSITORY_API", line 882
ORA-06512: at "IFSAPP.COMPOSITE_PAGE_REPOSITORY_API", line 1492
ORA-06512: at "IFSAPP.COMPOSITE_PAGE_REPOSITORY_API", line 1586
ORA-06512: at "IFSAPP.COMPOSITE_PAGE_REPOSITORY_API", line 304
ORA-06512: at "IFSAPP.COMPOSITE_PAGE_REPOSITORY_API", line 310
ORA-06512: at line 9
at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions)
at Ifs.Fnd.AccessProvider.FndConnection.UnMarshalResponseHeader(Stream responseStream, FndManualDecisionCollection decisions)
at Ifs.Fnd.AccessProvider.FndConnection.HandleHttpSuccessResult(HttpWebResponse result, FndManualDecisionCollection decisions, String operation, FndBodyType responseBodyType, Object responseBody)
at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway)
--- End of inner exception stack trace ---
at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync, Boolean integrationGateway)
at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync, Boolean integrationGateway)
at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommandCollection.Invoke()
at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommand.ExecuteNonQuery()
at Ifs.Fnd.Explorer.Extenders.CompositePages.Repository.SaveCompletePage(String pageId, String xml, String& objid, String& objversion, String clientType)
at Ifs.Fnd.Explorer.Extenders.CompositePages.Repository.SavePage(String pageId, PageViewModel page, Boolean pageOnly)
at Ifs.Fnd.Explorer.Extenders.CompositePages.ImportExportUtilities.ImportPage()
at Ifs.Fnd.Explorer.Extenders.CompositePages.Visuals.PageOverview.ImportPage()
at Ifs.Fnd.Explorer.Extenders.CompositePages.Visuals.PageOverview.buttonImport_Click(Object sender, RoutedEventArgs e)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.UIElement.OnMouseLeftButtonUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(Delegate genericHandler, Object genericTarget)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.UIElement.RaiseEvent(RoutedEventArgs args, Boolean trusted)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
--- End of inner exception stack trace ---
+20The above error seems to be related to the bug fix 154952 ( If you are below UPD9 as the fix is released with UPD9) The solution for states the following workaround:
Workaround: You may export the Lobby as Full Format or ZIP archive and manually remove the duplicated Data Sources. Modifying the ZIP file is the easiest since it is easy to spot the duplicated data sources as they have the same file name. Open the ZIP archive and remove each of the duplicated Data Sources, only leaving just one. Same could be carried out with the Full Format XML file but, it should be carefully done since editing the XML file should not break its structural validity.
Hope this helps.
Kasun B - https://www.linkedin.com/in/kasunbalasooriya/
Hi Srikanth,
I believe you can easily perform this from the Lobby Overview screen.
- Navigate to the Lobby Overview window
- Select the Lobby to be exported
- Click on Export Page and the following options will be available:
- Select the desired export option
To import the lobbies, the same Lobby overview window can be used in the destination environment.
Hope this helps.
Thanks,
Kasun
I dont see export option in lobby overview page.
Kindly let me know , that how can do that .
+20Hi Srikanth,
I believe you can easily perform this from the Lobby Overview screen.
- Navigate to the Lobby Overview window
- Select the Lobby to be exported
- Click on Export Page and the following options will be available:
- Select the desired export option
To import the lobbies, the same Lobby overview window can be used in the destination environment.
Hope this helps.
Thanks,
Kasun
I dont see export option in lobby overview page.
Kindly let me know , that how can do that .
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.