Overview
You have an Aurea Monitor Server (AMS) deployment file with some Policies and Business Processes and you want to import it to an existing setup that already has some but not all of the same policies and business processes already.
When you try to import it (or validate it with Validate Files) you get the following error:
LGSERVER0255: The resource already exists
In the logs you might find something like this:
<event>
<date>2021/04/01 18:51:57.11+0000</date><severity>ERROR</severity><reqid></reqid><thread>JettyHttpListener0-14</thread><user>Administrator/Admin</user><runid>123456789</runid><subsys>LGSERVER</subsys><logid>ddddd2d3-3333-4444-aabb-666666622222</logid><msgid>LGSERVER0255</msgid>
<msg>LGSERVER0255: The resource BusinessProcess1 already exists
at com.actional.task.busdel.DeploymentDelegate.importCustom(DeploymentDelegate.java:762)
at com.actional.lg.server.busdel.LGDeploymentDelegate.importCustom(LGDeploymentDelegate.java:621)
at com.actional.soapstation.task.DeploymentTask.importCustom(DeploymentTask.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.actional.APISessionFacade$Handler$1.invokeNext(APIFactory.java:735)
at com.actional.AuditSessionProxy.invoke(AuditSessionProxy.java:67)
at com.actional.APISessionFacade$Handler$1.invokeNext(APIFactory.java:729)
at com.actional.LogExceptionSession$Proxy.invoke(LogExceptionSession.java:142)
at com.actional.APISessionFacade$Handler$1.invokeNext(APIFactory.java:729)
at com.actional.AsyncCallSession$Proxy.invoke(AsyncCallSession.java:94)
at com.actional.APISessionFacade$Handler.invoke(APIFactory.java:747)
at com.sun.proxy.$Proxy20.importCustom(Unknown Source)
at com.actional.ui.deployment.ImportServlet.doPost(ImportServlet.java:146)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.actional.j2ee.J2EEServlet.service(J2EEServlet.java:127)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:399)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:366)
at com.actional.servlet.XForwardFilter.doFilter(XForwardFilter.java:101)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.ui.TunnelSensitiveRedirectionFilter.doFilter(TunnelSensitiveRedirectionFilter.java:41)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.UiHttpHeadersFilter.doFilter(UiHttpHeadersFilter.java:119)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.IndexFilter.doFilter(IndexFilter.java:71)
at com.actional.lg.server.LGIndexFilter.doFilter(LGIndexFilter.java:52)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.j2ee.SessionFilter.doFilter(SessionFilter.java:53)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.ImpersonateFilter.doFilter(ImpersonateFilter.java:113)
at com.actional.servlet.ImpersonateFilter.doFilter(ImpersonateFilter.java:86)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at com.actional.servlet.BaseFilter.doFilter(BaseFilter.java:75)
at com.actional.j2ee.J2EEFilter.doFilter(J2EEFilter.java:86)
at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:357)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:306)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:586)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1861)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:526)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1811)
at org.mortbay.http.HttpServer.service(HttpServer.java:886)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at org.mortbay.http.SocketChannelListener.handle(SocketChannelListener.java:339)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:526)
</msg>
</event>
Solution
This is expected behavior and it is by design.
The problem occurs when your deployment file contains existing Business Processes or Policies using existing Business Processes. AMS does not allow the import of the configuration if a Business Process to be imported already exists in AMS.
The solution is that you need to remove from AMS the existing Business Processes or the Policies using Business Processes before importing the new ones (before importing the deployment file containing the same Business Processes).