Workspace in ALBPM Enterprise

When you deploy a project in ALBPM enterprise for WAS how do you get to the workspace like you see when you click the blue button in Studio versions toolbar? Stupid question but I need to see the audit trail.

Hi,
Please correct me if I am not following you.
You want to log into the workspace to do the task after deployment into the enterprise server as you did in your studio. If this is your problem then invoke the workspace by using the following URL
if you are in ALBPM 6.0/10g R3 then: http:/<server ip address>:<port no>/workspace
Example: http://localhost:8686/workspace/faces/jsf/workspace/workspace.xhtml
If you are in ALBPM 5.7: http:/<server ip address>:<port no>/portal
To view a work item's audit trail in 5.7:
1) To view details about a work item, in the right pane, click in the Description column for the work item.
2) In the Task toolbar, click the Audit Trail button. The Audit Trail dialog box opens and displays information about each of the activities for the work item.
3) To expand an activity, in the Activity column, click the minus icon for the activity.
Hope this help you.
Bibhu
Edited by: Bibhuti Bhusan on Aug 24, 2010 9:10 PM

Similar Messages

  • Error while configuring the directory in ALBPM Enterprise 6.0 WL edition

    Hi,
    We have installed ALBPM Enterprise 6.0 for Weblogic edition to deploy ALBPM processes into Enterprise 6.0. I tried to configure directory through ALBPM admin center.
    I have checked the below options and provided necessary information asked in the series of dialog boxes.
    - Create Directory Service
    - Create Process engine
    - Create ALBPM application EARs
    - BEA Weblogic Configuration
    We get error in the last step (BEA weblogic configuration) stating that there is some problem in executing the WLST script:-
    Problem invoking WLST - Traceback (innermost last):
    File "C:\Documents and Settings\14360\.configWizard\tmp\config.py", line 640, in ?
    NameError: engineType
    We tried to deploy the ALBPM application EARs manually to weblogic. But there are lot of dependencies, so we couldn't successfuly deploy them.
    Appreciate any help on resolving the WLST error.
    Thanks in advance
    Deepak

    Deepak:
    Could you please check the info on
    http://tracker.fuegolabs.com/browse/EAP-985
    HTH
    Nico
    Deepak Vinod Kumar wrote:
    Hi,
    We have installed ALBPM Enterprise 6.0 for Weblogic edition to deploy ALBPM processes into Enterprise 6.0. I tried to configure directory through ALBPM admin center.
    I have checked the below options and provided necessary information asked in the series of dialog boxes.
    - Create Directory Service
    - Create Process engine
    - Create ALBPM application EARs
    - BEA Weblogic Configuration
    We get error in the last step (BEA weblogic configuration) stating that there is some problem in executing the WLST script:-
    Problem invoking WLST - Traceback (innermost last):
    File "C:\Documents and Settings\14360\.configWizard\tmp\config.py", line 640, in ?
    NameError: engineType
    We tried to deploy the ALBPM application EARs manually to weblogic. But there are lot of dependencies, so we couldn't successfuly deploy them.
    Appreciate any help on resolving the WLST error.
    Thanks in advance
    Deepak

  • ALBPM Enterprise SA 5.7 MP3 and Weblogic Express 9.2

    We are using ALBPM Enterprise SA 5.7 MP3 and Weblogic Express 9.2. We have the following questions:
    1) Why, after assigning a Parametric Role to an user, we have to restart the portal in Weblogic before the user can log back into the system? When we do not do it, the user will see an error on the screen informing of a lack of permisions to visualize the activities of the new assigned role. This happens even when we have already clicked several times on the button labeled "Re-load Information from the Directory" (in ALBPM's WebConsole) and even after a few hours have passed. All our engines have a "Directory Polling Interval" of 1 minute, but it seems not to work.
    2) Do we have to modify any extra value, or set something in particular in Weblogic?
    Thanks in advance. We look forward for suggestions.

    We are using ALBPM Enterprise SA 5.7 MP3 and Weblogic Express 9.2. We have the following questions:
    1) Why, after assigning a Parametric Role to an user, we have to restart the portal in Weblogic before the user can log back into the system? When we do not do it, the user will see an error on the screen informing of a lack of permisions to visualize the activities of the new assigned role. This happens even when we have already clicked several times on the button labeled "Re-load Information from the Directory" (in ALBPM's WebConsole) and even after a few hours have passed. All our engines have a "Directory Polling Interval" of 1 minute, but it seems not to work.
    2) Do we have to modify any extra value, or set something in particular in Weblogic?
    Thanks in advance. We look forward for suggestions.

  • How to Import Custom Views and JSPs to ALBPM Enterprise

    Hi,
    I am using ALBPM 5.7. I have developed a custom view in Studio. When I publish and Deploy the Project in ALBPM Enterprise (WebLogic 9.2), I check true the Import Custom JSPs and Views (or similar terminology). But when I login to the portal after installing the EAR, the view is not listed in my work pane.
    Also, in one of the Interactive Activity I am calling a JSP, which gives a Null Pointer Exception when execute the instance, In my opinion, the Custom JSP is not deployed.
    I have also copied the JSP file in location \bea\ALPBM5.7\j2eewl\webapps\portal\customjsp\
    Please suggest as how do I deploy the View and JSP
    Thank you,
    Regards
    Jayant
    Edited by jayantbit at 06/19/2008 8:01 AM
    Edited by jayantbit at 06/19/2008 8:21 AM

    Hi Mohamed,
    Please check below link.
    What is Drag and Relate in SAP Business One - YouTube
    https://help.sap.com/saphelp_sbo882/helpdata/en/45/100314cf465d7ae10000000a11466f/content.htm
    https://help.sap.com/saphelp_sbo882/helpdata/en/45/10ff71cf465d7be10000000a11466f/content.htm
    SAP - SAP Business One: Your Solution for Generating Custom Reports
    Hope this helps
    Regards::::
    Atul Chakraborty

  • Scope of ALBPM Studio and ALBPM Enterprise Server

    Hi
    I have some simple questions about ALBPM Enterprise Server:
    it is really necessary to have this component in a production environment?.
    For example, if a company is very small with 10 or 15 employees and you have only 2 processes in the company, ALBPM Studio is not enough to execute and to administrate these processes?
    What are the problems that I would have if I decided to set up a production environment only with ALBPM Studio?
    What things I could not do if I will not have the Enterprise Server?
    How many users simultaneosly support the ALBPM Studio in a testing environment?
    Thank you so much...

    Hi,
    The short answer is 'yes', you'll need an Enterprise server. Here are some of the issues with using Studio:
    Functionality:
    You can't do everything you can do in the Enterprise server in the Studio engine. However, whether this is an issue would depend on the complexity of your processes/requirements. For example, the Studio engine doesn't support the versioning of processes.
    Licensing:
    I don't know for sure, but I doubt the ALBPM licensing allows for Studio to be used in 'production'.
    Runtime
    The Studio engine can't be isolated from the Studio application. So you'd always have to make sure someone had studio running on a PC somewhere.
    Users
    You are limited to 5 concurrent users in Studio.
    There did actually used to be a copy of the Engine that was aimed at small scale deployments called 'Express' (I think), but it disappeared a while back.
    Hope this helps,
    Tim

  • Integrate LDAP with ALBPM Enterprise

    hi,
    Did anyone tried to integrate LDAP with ALBPM Enterprise?
    If using LDAP for creating directory, will it create a new schema in LDAP?
    If need to make use of existing LDAP schema, how can we do it?
    Need HELP!!!
    Thanks

    Hi Jasmine,
    Here are the choices you have for your Directory Service in ALBPM 6.0 Enterprise Standalone (I pulled them off of http://portal.plumtree.com/portal/server.pt?open=512&objID=3422&&PageID=5325&mode=2&in_high_userid=573417&cached=true).
    Sorry - I don't see "Open LDAP" in the list.
    Single Source JNDI Plugins: Sun ONE Java System Directory Server 5.2 (JNDI), MS Active Directory 2003 (JNDI). (Deprecated - they cannot be created any more); Single Source JDBC Plugins: Oracle 9i and 10g, MS SQLServer 2005, IBM DB2 UDB 8.2 and 9.1 using DataDirect JDBC Drivers 3.6; Sybase ASE 15.0.2 will be supported in ALBPM 6.1; Hybrid Plugins: Sun ONE System Directory Server 5.2 and Oracle 9i, Sun ONE System Directory Server 5.2 and Oracle 10g, MS Active Directory 2003 and Oracle 9i, MS Active Directory 2003 and Oracle 10g, MS Active Directory 2003 and MS SQL Server 2005, Sun ONE System Directory Server 5.2 and IBM DB2 8.2 or 9.1
    hth,
    Dan

  • Issue with Deploying and calling a BPEL process on ALBPM enterprise server

    Hi,
    I am trying to put in place a POC using Aqualogic BEA products (using ALBPM 5.7, Enterprise Server 5.7, ALSB 2.6, Weblogic App server 9.2). My goal is to put in place a simple BPEL process (using ALBPM) which would call a webservice exposed through ALSB. This BPEL process is initiated by a wrapper BPMN process calling the BPEL process through fuego code.
    Though we are able to do the above on a standalone ALBPM studio, When we try to deploy the exported BPM project on the enterprise server and access it through the hiper workspace portal we are getting the following error in the BPM Process Administrator Log of the Engine.
    A component failed while executing activity '/Process#Default-1.0/Global' (BP-method Global). Details: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. Caused by: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. fuego.lang.ComponentExecutionException: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:916) at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1068) at fuego.server.execution.TaskExecution.invoke(TaskExecution.java:389) at fuego.server.execution.GlobalTaskExecution.invoke(GlobalTaskExecution.java:106) at fuego.server.execution.TaskExecution.executeCIL(TaskExecution.java:481) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:655) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:616) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:442) at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:164) at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:142) at fuego.server.execution.Global.execute(Global.java:81) at fuego.server.AbstractProcessBean$38.execute(AbstractProcessBean.java:2496) at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:290) at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:462) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:540) at fuego.transaction.TransactionAction.start(TransactionAction.java:213) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:117) at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66) at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2491) at fuego.ejbengine.EJBProcessControlAdapter.runGlobalActivity(EJBProcessControlAdapter.java:386) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl.runGlobalActivity(EJBProcessControlAdapter_hu750h_EOImpl.java:2877) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:335) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl_921_WLStub.runGlobalActivity(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at fuego.papi.impl.AbstractProcessControlHandler.invokeInternal(AbstractProcessControlHandler.java:48) at fuego.papi.impl.j2ee.EJBProcessControlHandler.doInvoke(EJBProcessControlHandler.java:111) at fuego.papi.impl.j2ee.EJBProcessControlHandler.invoke(EJBProcessControlHandler.java:66) at $Proxy77.runGlobalActivity(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1478) at fuego.lang.JavaObject.invoke(JavaObject.java:185) at fuego.papi.impl.j2ee.EJBExecution.next(EJBExecution.java:200) at fuego.portal.wapi.InteractiveExecution.process(InteractiveExecution.java:157) at fuego.portal.wapi.WebInteractiveExecution.process(WebInteractiveExecution.java:54) at fuego.portal.wapi.InteractiveExecution.process(InteractiveExecution.java:200) at fuego.portal.servlet.ExecutionDispatcher.runGlobalActivity(ExecutionDispatcher.java:659) at fuego.portal.servlet.ExecutionDispatcher.processRequest(ExecutionDispatcher.java:144) at fuego.portal.servlet.ExecutionDispatcher.doPost(ExecutionDispatcher.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at fuego.portal.servlet.AuthenticatedWamServlet.service(AuthenticatedWamServlet.java:1049) at fuego.portal.servlet.SingleThreadPerSession.service(SingleThreadPerSession.java:73) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at fuego.servlet.multipart.BaseMultipartFilter.doFilter(BaseMultipartFilter.java:57) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) Caused by: fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. at fuego.connector.ConnectorException.connectorNotFound(ConnectorException.java:55) at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:586) at fuego.connector.ConnectorTransaction.getConnectorInterface(ConnectorTransaction.java:618) at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:254) at fuego.soaptype.WSConfiguration.getInstance(WSConfiguration.java:55) at fuego.soaptype.Endpoint.create(Endpoint.java:42) at fuego.soaptype.WebServiceInstantiator.instantiate(WebServiceInstantiator.java:58) at fuego.component.Component.instantiateDynamic(Component.java:123) at CapGemini.Process.Default_1_0.Instance.CIL_callBPEL(Instance.java:241) at CapGemini.Process.Default_1_0.Instance.CIL_callBPEL(Instance.java:307) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:907) ... 64 more
    Two things here that might help to understand the problem better :
    1) As I understand the error is due to some issue while calling the BPEL process from the Fuego code.
    The Fuego code which call's the BPEL from the BPMN process is as follows :
    helloResponse as String = "someoutput"
    helloRequest as String = "someinput"
    sessionid as String
    // Starting a Session.
    // In case you are testing this in the Studio,
    // the password must be the same as the user
    startSession BPELWSDL.ProcessServiceListenerWSDL.ProcessService
    using user = "test",
    password = "test"
    returning sessionid = result
    // createTest is the name of the operation
    // in the exposed process.
    // In this case the process "ExposedProcess"
    // has a web service operation
    // called "createTest" that is a "Process Creation" type
    // and uses the Begin activity's argument set
    callHello BPELWSDL.ProcessServiceListenerWSDL.ProcessService
    using sessionId = sessionid,
    arg1 = helloRequest
    returning helloResponse = result
    // Closing the session
    discardSession BPELWSDL.ProcessServiceListenerWSDL.ProcessService
    using sessionId = sessionid
    display "The BPEL's response : " + helloResponse
    2) Further, I had catalogued the BPEL's wsdl to the location http://localhost:9000/fuegoServices/ws/ProcessServiceListener?WSDL while running the same in Studio, but while deploying on the enterprise server , I made this point to http://localhost:7001/fuegoServices/ws/ProcessServiceListener?WSDL Is this correct ?
    Any thought on this issue would be appreciated.
    Regards
    Deepak

    Hi Deepak,
    We are also facing a similar problem, while accessing an external webservice from a BPM process.
    Were you able to resolve this issue.
    If so, Could you please let us know the procedure that you followed to resolve the issue.
    Thanks in Advance,
    Krishnaveni.

  • Adding an External Resource - ALBPM Enterprise Server V 6.0

    Hi ,
    In our BPM application, we are consuming an external webservice. In BPM studio, when we tested the application, It was working fine.
    But when we deployed our application in Enterprise server, We are facing issues while invoking the external web service.
    We are getting the following exception in the logs of Enterprise Server.
    A component failed while executing activity '/LocateTerminal#Default-1.0/ComponentExecution[fetchlocation]' (BP-method fetchlocation) over instance '/LocateTerminal#Default-1.0/82/0'.
    Details:
    The method 'CIL_fetchlocation' from class 'bea.LocateTerminal.Default_1_0.Instance' could not be successfully executed.
    Caused by: The configuration name [null] and type [Web Service] is not defined.
    Detail:The connector must be configured in the appropiate context.
    fuego.lang.ComponentExecutionException: The method 'CIL_fetchlocation' from class 'bea.LocateTerminal.Default_1_0.Instance' could not be successfully executed.
         at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:506)
         at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:260)
         at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:215)
         at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1175)
         at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:127)
         at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:85)
         at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:89)
         at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:63)
         at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
         at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:264)
         at fuego.server.execution.ToDoItem.run(ToDoItem.java:559)
         at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:767)
         at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:747)
         at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:143)
         at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:135)
         at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446)
         at fuego.component.ExecutionThread.work(ExecutionThread.java:831)
         at fuego.component.ExecutionThread.run(ExecutionThread.java:409)
    Caused by: fuego.connector.ConnectorException: The configuration name [null] and type [Web Service] is not defined.
    Detail:The connector must be configured in the appropiate context.
         at fuego.connector.ConnectorException.connectorNotFound(ConnectorException.java:55)
         at fuego.connector.CompositeConnectorService.getConnectorInterface(CompositeConnectorService.java:268)
         at fuego.connector.ConnectorTransaction.registerConnectorInterfaceCoordinator(ConnectorTransaction.java:649)
         at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:265)
         at fuego.webservices.connector.WSConfiguration.create(WSConfiguration.java:57)
         at fuego.soaptype.WebServiceInstantiator.instantiate(WebServiceInstantiator.java:70)
         at fuego.component.Component.instantiateDynamic(Component.java:133)
         at bea.LocateTerminal.Default_1_0.Instance.CIL_fetchlocation(Instance.xcdl:3)
         at bea.LocateTerminal.Default_1_0.Instance.CIL_fetchlocation(Instance.xcdl)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:499)
    Can you please tell me , to how to configure an external webservice in Enterprise Server.
    please help me in resolving this issue.
    Thanks,
    Krishnaveni.

    Hi,
    There is nothing to do with the versioning. There is a problem with the tool (Configuration Wizard).
    This is how the problem was solved,
    After creating the Directory Service start and login to the Process Admininstrator,
    ALBPM web console-> Organizational settings->Export->Views, export the views.xml and check for any invalid characters.
    After removing the invalid characters save the xml and import the modified views.xml to the same location.
    This should solve the problem.
    Thanks,
    Krina

  • Workspace of BPM Enterprise 10.3.1 for Weblogic

    I just install BPM Enterprise 10.3.1 for weblogic. I configure it using default setting.
    In the BPM admin center, it has 5 options:
    Start
    Stop
    Start process administrator
    configuration
    exit
    Where is the workspace?

    Hi YE,
    If you are deploying BPM on a Weblogic Server you'll find your workspace on the following url
    http://localhost:7001/workspace
    This is because the all the jar services are deployed to the WLS. You can monitor if it is installed by going into the Process administrator -> Engines -> J2EE jar deployment (or something)
    There you'll find all the jars that are/can be deployed. If you make any changes using the BPM admin center configuration don't forget to recreate and redeploy the jar file.
    Hope this helps.
    Kind regards
    Nils

  • Weblogic-Albpm enterprise Error

    Hi all ,
    when i tried configuring ALBPM5.5 enterprise with weblogic ,i reached till the point JDBC data source properties. i am following "ALBPM_5-7_WebLogic_9-2_Installation.pdf" It explains step by step. All the steps went successful till the point of configuring JDBC data source and even testing the configuration went successful.After this ,i am getting the error when i hit "Targets flap" and clicked on Lock and Edit...
    please help usAn unexpected exception has occurred processing your request
    Message: null
    Stack Trace: java.lang.NullPointerException at com.bea.console.actions.jdbc.datasources.JDBCDataSourceTargetAction.execute(JDBCDataSourceTargetAction.java:74) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:221) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:130) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1169) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:688) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.renderInternal(ScopedContentCommonSupport.java:268) at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.render(StrutsStubImpl.java:107) at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:288) at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:427) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:708) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:720) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:183) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:339) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:186) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:140) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:370) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:229) at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:195) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:180) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3229) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2002) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1908) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1362) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    hi!
    if after save, u click in "Data Source" at "Domain Structure" before "Activate Changes", it'll work.
    Rgs, Carlos Okamoto

  • ALBPM Enterprise Standalone Clustering - HA Setup

    I wanted to know how would the HA setup be done for ALBPM standalone edition as it comes with a built in Tomcat?

    We checked the ADF source (pasted below). It reads that markScopeDirty is getting skipped if ADF_SCOPE_HA_SUPPORT is not configured but when we debug our application the serialization fires after every pageScope/viewScope variable gets changed regardless of markScopeDirty() is being called or not. That signifies that markScopeDirty() call is not needed. Do we really need markScopeDirty() everywhere in our application or this is just a public helper method to manually trigger replication for some exceptional case? Can anyone from team Oracle explain this behavior?
    @Override
    public void markScopeDirty(Map<String, Object> scopeMap)
    Boolean handleDirtyScopes =
    (Boolean)ControllerConfig.getProperty(ControllerProperty.ADF_SCOPE_HA_SUPPORT); //checks for adf-scope-ha-support
    if (handleDirtyScopes.booleanValue())
    if (!(scopeMap instanceof SessionBasedScopeMap))
    String msg = AdfcExceptionsArb.get(AdfcExceptionsArb.NOT_AN_ADF_SCOPE);
    throw new IllegalArgumentException(msg);
    ((SessionBasedScopeMap)scopeMap).markDirty();
    }

  • ALBPM Workspace - Process Administrator

    My ALBPM workspace through the Process Administrator i.e. the ALBPM Server is not opening..But it works through studio...What could be the possible reason? Anyone?
    I give the URL as http://localhost:8686/workspace
    The Process Administrator Console is running at http://localhost:8686/webconosle
    The engine is running
    The project is deployed..
    The project runs via. the Weblogic Portal but does not through ALBPM Server workspace..
    Why is that so?
    Anyone?

    As you are using the ALBPM Enterprise for Weblogic, all the ears will be deployed on weblogic. Check if all the ears are deployed properly and all of them are up and running in the weblogic console.
    You need to open the follwoing link to get the workspace.
    [http://|http:///]&lt;hostname&gt;:&lt;port&gt;/workspaceadmin
    hostname: is the machine name where weblogic is deployed.
    port: number on which the weblogic server is running.
    ex:
    [http://localhost:7001/workspaceadmin]
    Thanks.

  • Error while running an albpm process on enterprise server 5.7

    Hi,
    I am trying to run an ALBPM project on the ALBPM Enterprise Server 5.7 on weblogic 9.2
    This Order management process, makes a call to the sub process < CreateOrderWSCaller >, which using an interactive activity further calls the webservice <OrderService>. This webservice is hosted at http://localhost:7001/webservices/OrderService
    The process is getting successfully deployed but when running the same on the enterprise server, I am getting the following exeption
    A component failed while executing activity '/CreateOrderWSCaller#Default-1.0/callWS' (BP-method Add Order) over instance '/CreateOrderWSCaller#Default-1.0/2/0'. Details: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [OrderService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. Caused by: The configuration name [OrderService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. fuego.lang.ComponentExecutionException: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [OrderService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '.
    Please help.
    Thanks
    deepak

    Hi Wilson,
    Iam trying to install Siebel 8.1.1.0, with the next image creator utility (Linux_ImageCreator ) in console mode.
    But i got the error message when creating the install image. I have downloaded the file four times, and also i checked the MD5 and SHA-1 codes in order to validate the integrity of the downloaded file. The codes are the same that are available in Oracle Edelivery.
    About the O.S. i will change it, however, at this time i have not be able neither create the install image.
    What could i do for solving this issue?
    Thanks in advance.

  • ALBPM - Custom JSP

    How can we refer to JSP files that are placed in customJSP Folder.
    What I want to do is, I want to call this JSP from a Dashboard Presentation. A link in the Dashboard presentation refers to this JSP.
    Currently in Studio if I use /workspace/webRoot/customJSP/myjsp.jsp it works. But when I deploy it on ALBPM Enterprise server it doesnt, I get 404-Page not found error.
    We did change the ContextRoot from workspace to portal, still it doesnt work.
    And I am not talking about any ScreenFlows.

    We are also facing the same below issue .Please help us to solve the problem ....
    How can we refer to JSP files that are placed in customJSP Folder.
    What I want to do is, I want to call this JSP from a Dashboard Presentation. A link in the Dashboard presentation refers to this JSP.
    Currently in Studio if I use /workspace/webRoot/customJSP/myjsp.jsp it works. But when I deploy it on ALBPM Enterprise server it doesnt, I get 404-Page not found error.
    We did change the ContextRoot from workspace to portal, still it doesnt work.
    And I am not talking about any ScreenFlows.

  • LIVE workspace is missing... or is it? [9.2.0.6.0]

    Dear all
    Under Workspace|Workspaces in Enterprise Manager I expect to see "LIVE". This is the case for all my databases except one, which I'll call "AAPSD". Under AAPSD there are no workspaces listed in Enterprise Manager. However, if I connect to SQL*Plus and query the database directly I get this:
    SQL> select dbms_wm.getworkspace from dual;
    GETWORKSPACE
    LIVE
    I have tried uninstalling and reinstalling the Oracle Workspace Manager but this has had no effect. I had no interest in workspaces before I discovered that this "missing" LIVE workspace was causing a problem in our MapInfo-based software application.
    Any ideas why it's there in SQL*Plus but not Enterprise Manager?
    Would be grateful for any advice.
    Thanks
    Stuart

    Hi,
    I ran into this situation recently. This can potentially happen when doing a full import/export of a database where the workspace manager version on the exported database does not match the version on the import database.
    In database releases since 10.2, the wmsys schema is no longer exported when performing a full database export. When the versions do not match, the procedural actions that are used to import the required data will not be run. As a result, the LIVE workspace will be missing. Since you are on 9.2.0.6, this could also occur due to any other error that prevents the procedural actions from running. You would need to check the import logs to see if this occurred.
    If this is what happened in your case, inserting the missing row into the wmsys.wm$workspaces_table table will not completely fix the problem as there is additional metadata that will not be imported.
    Regards,
    Ben

Maybe you are looking for

  • Itunes store problm

    Whenever i try to look through the itunes store i get this error message "we could not complete your itunes store request. The network connection was reset. Make sure your network connection is active and try again." Some time half the front page of

  • Aperture import stopped working?

    I have used Aperture for about a year now and love it. Never really had much of a problem with it. I recently went to add photo's from my Rebel XT's CF card and it popped up like normal. I selected the photo's from the card to import and told it was

  • Cumulative total - how to have a footer cell give running total

    I'm working on a gas mileage spreadsheet. One column shows how many miles I went between gas fill ups. I'd like the footer cell in that column to show the running total. I'm running into a problem with the empty cells - they're causing a red triangle

  • BI process chain problem

    hi, In BI, we are using process chain for uploading the data from CRM to BI. In process chain, when we are schedulling it at any point of time the job is not getting displayed in sm37 as well as the chain is not getting strarted at scheduled time. Wh

  • CF Enterprise vs Standard when used to host CF sites

    Hi, Can anyone tell me the merits of having my site hosted at a host who uses the enterprise version as opposed to the standard version? I am looking for a host for my CF site - developed for cfmx7, i have narrowed it down to 2 hosts but one is much