Work Manager 6.1 Initialize / Default Collection

Hi,
I'm trying to default the Crew Member Collection from a complex table when the application initializes. I have added a Sub-Action to the Transmit Action which has an Enable Rule to determine if it executes.
My issue is when I launch the Agentry Application, the Transmit Action is triggered and I can see my Enable Rule returns - True but my Sub-Action doesn't execute. ATE log extract below -
The ATE log says my Action - ZCrewMemberDefaultAction has no enable rule configured, but the it has been set to "Always Enable"
However if I manually trigger the Transmit Action (after the application has initialized) my Sub-Action executes and the Crew Members are defaulted.
Can someone please help identify why my SubAction isn't being executed OR suggest any other options where I can execute my "Default Crew Member Logic" when the application is launched?
I'm targeting the WPF platform (v7.0.4.203) and the complete ATE log is attached.
Thanks,
Stephen

Of the actions in the ATE trace, Transmit seemed to make the most sense to try and plug my action into; hadn't tried the PM Login Action. I couldn't see other actions that might be suitable when the application is initialized.
As a last resort I was going to create a Fetch BAPI to populate the collection, but thought it was redundant because I already have the required data in the Complex Table.
OR
Create a "Default Crew" button on the Crew Management View (Just got that working)
Cheers.

Similar Messages

  • SAP Work Manager 6.0 - Creating notification on mobile device (customizing the default Start and End date)

    Dear all,
    When I create a notification in SAP Work Manager 6.0, the notification gets created in the back-end with Start Date equal to Current Date + 1 day and End Date equal to Current Date + 3 days.
    Can you advise where I can customize this behaviour, so that the Start Date is for example equal to the Current Date and End Date being 14 days in the future? Is this something that would need to be configured in Agentry Editor or within the ABAP stack?
    Many thanks for your support.
    Pavel
    Tags edited by: Michael Appleby

    Hi Jason,
    We went this route and identified the initial values, and tried to modify those.
    No impact though, as if those values are being overwritten elsewhere (whatever value we set, no change on the backend).
    Please see the attachments with screenshots of Agentry Editor.
    Many thanks.
    Pavel

  • Solved: I cannot manage (bring online, initialize, partition, format, or write to) a VHDX hard drive once it has "Enable Virtual Hard Disk Sharing" enabled.

    Hello,
    Issue:
    On a Virtual Machine with a secondary VHDX attached, I cannot manage (bring online, initialize, partition, format, or write to) the VHDX hard drive once it has "Enable Virtual Hard Disk Sharing (VHD Sharing)" enabled.
    Questions:
    Should I be able to manage (bring online, initialize, partition, format, and write to) a VHDX hard drive once it has VHD Sharing enabled? If I should be able to manage it, what am I missing?
    Topography:
    One SuperMicro Cluster In a Box (CIB) with 2012 R2 Data Center on each node. Microsoft Failover Cluster installed and working on each node. The Failover Cluster Servers on each host passes all cluster validation tests. Two Hyper-V 2012 R2 Data Center Virtual
    Machine (VM) servers, one on each node. 1 common Cluster Shared Volume (CSV) and 1 Generation 2 Scale-Out File Server (SOFS) shared volume both Resilient File System (REFS) formatted. One 5 Gigabit (Gb) Virtual Hard Drive Type X (VHDX) file on the CSV and/or
    SOFS. Integrity bit and read only turned off on VHDX file.
    Each of the two Hyper-V VMs have one 127Gb VHDX Generation 2 primary hard drive and 1 VHDX secondary hard drive attached, both on SCSI Controller #1.
    Background:
    If I start VM1 without the VHD Sharing enabled on the secondary hard drive, I can bring the drive online, initialize, partition, format, and write to the drive.
    If I enable VHD Sharing, I can no longer modify the drive in Disk Management in any way. With or without VM2 running.
    Both VMs and the CSV and SOFS are on the same host cluster server, or not, no difference…
    The VHDX is referenced either by the CSV name C:\ClusterStorage\Volume1\TEST1.VHDX
     or a Shared Folder name
    \\sharedfolder\folder\Test1.VHDX .
    If I start VM1 with VHD Sharing disabled and I format the drive, then shut down and enable VHD Sharing, the drive is offline and requests initialization which fails with an "I/O device error", every other attempt to manage the drive fails with
    the same "I/O device error", error.
    Events:
    VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
    Log Name:      System
    Source:        Virtual Disk Service
    Date:          3/3/2015 11:39:18 AM
    Event ID:      10
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Server1.Domain.local
    Description:
    VDS fails to write boot code on a disk during clean operation. Error code: 8007045D@02070008
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Virtual Disk Service" />
        <EventID Qualifiers="49664">10</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-03T19:39:18.000000000Z" />
        <EventRecordID>27318</EventRecordID>
        <Channel>System</Channel>
        <Computer> Server1.Domain.local </Computer>
        <Security />
      </System>
      <EventData>
        <Data>8007045D@02070008</Data>
      </EventData>
    </Event>
    AND
    Log Name:      System
    Source:        disk
    Date:          3/3/2015 12:16:42 PM
    Event ID:      153
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Server1.Domain.local
    Description:
    The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\MPIODisk1) was retried.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="32772">153</EventID>
        <Level>3</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-03-03T20:16:42.017090000Z" />
        <EventRecordID>27333</EventRecordID>
        <Channel>System</Channel>
        <Computer>Server1.Domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk1\DR1</Data>
        <Data>0x0</Data>
        <Data>1</Data>
        <Data>\Device\MPIODisk1</Data>
        <Binary>0F01040004002C00000000009900048000000000000000000000000000000000000000000000000000020488</Binary>
      </EventData>
    </Event>
    Thanks again for any help,
    Robert

    Hi All,
    I had to buy a Willy Wonka bar and spend a golden ticket to get an answer to this one.
    We found that the default LogicalSectorSizeBytes of a VHDX is 512b. It needs to be 4kb.
    The Host drive doesn't seem to matter CSV or SOFS. Below is a way to create a VHDX with the correct LogicalSectorSizeBytes.
    In Power Shell, type --> New-VHD -Path C:\ClusterStorage\Volume4\Cluster2DataDisks\Cluster2Disk1.vhdx -SizeBytes 200Gb -PhysicalSectorSizeBytes 4kb -LogicalSectorSizeBytes 4kb
    Attach the resulting file to your guest cluster servers and set the Enable Virtual Hard Disk Sharing option on both server. You should now be able to bring the drives on-line and initialize them. They will also add to the guest cluster pool.
    Change the size, path and file name above to fit your Cluster Servers configuration.
    Thank You 
    Sachin Kumar Support Engineer | Windows Server Setup Team | Microsoft Enterprise Platform for finding the answer to this one.
    Hope this helps others.
    Robert

  • Failed to lazily initialize a collection -, could not initialize proxy - no Session

    I have an application that i am extending to provide a REST API.  Everything works fine in the main site, but I am getting the following in the exception log when I try to hit the REST API:
        "Error","ajp-bio-8014-exec-3","12/02/14","12:54:06","table","failed to lazily initialize a collection of role: field, could not initialize proxy - no Session The specific sequence of files included or processed is: service.cfc'' "
        org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: field, could not initialize proxy - no Session
            at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationExc eption(AbstractPersistentCollection.java:566)
            at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeed ed(AbstractPersistentCollection.java:186)
            at org.hibernate.collection.internal.AbstractPersistentCollection.readSize(AbstractPersisten tCollection.java:137)
            at org.hibernate.collection.internal.PersistentBag.size(PersistentBag.java:242)
            at coldfusion.runtime.xml.ListIndexAccessor.getSize(ListIndexAccessor.java:44)
            at coldfusion.runtime.xml.ArrayHandler.serialize(ArrayHandler.java:69)
            at coldfusion.runtime.xml.CFComponentHandler.serialize(CFComponentHandler.java:106)
            at coldfusion.runtime.XMLizerUtils.serializeXML(XMLizerUtils.java:83)
            at coldfusion.rest.provider.CFObjectProvider.writeTo(CFObjectProvider.java:378)
            at com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
            at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationIm pl.java:1479)
            at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImp l.java:1391)
            at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImp l.java:1381)
            at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
            at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
            at coldfusion.rest.servlet.CFRestServletContainer.service(CFRestServletContainer.java:141)
            at coldfusion.rest.servlet.CFRestServletContainer.service(CFRestServletContainer.java:86)
            at coldfusion.rest.servlet.CFRestServlet.serviceUsingAlreadyInitializedContainers(CFRestServ let.java:556)
            at coldfusion.rest.servlet.CFRestServlet.invoke(CFRestServlet.java:434)
            at coldfusion.rest.servlet.RestFilter.invoke(RestFilter.java:58)
            at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:94)
            at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8)
            at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
            at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
            at coldfusion.rest.servlet.CFRestServlet.invoke(CFRestServlet.java:409)
            at coldfusion.rest.servlet.CFRestServlet.service(CFRestServlet.java:400)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
            at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:303)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
            at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 )
            at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:241)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
            at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:422)
            at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:198)
            at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.jav a:607)
            at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    Disabling lazy loading will fix this, but results in unacceptable performance (load times go from 200ms to 22s).  I'm not sure how else to handle this.
    I am new to REST in ColdFusion, and it seems to me that the CFC's are being handled in an unusual way.  They do not appear to be initialized (init method does not seem to run) and now it seems that ORM is not handled the same either.  Am I missing something?
    Here is the excerpt of my code producing this error:
        component rest="true" restpath="item"
            import model.beans.*;
            remote item function getitem( numeric id restargsource="Path" ) restpath="{id}" httpmethod="GET"
                var item = entityLoad("item",{ id = id },true);
                return item;
    And the bean:
        component persistent="true" table="item" output="false" extends="timestampedBean" batchsize="10" cacheuse="read-only"
            /* properties */
            property name="id" column="id" type="numeric" ormtype="int" fieldtype="id" generator="identity";
            property name="title" column="title" type="string" ormtype="string";
            property name="description" column="description" type="string" ormtype="string";
            property name="status" column="status" type="numeric" ormtype="byte" default="0" ;
            property name="user" fieldtype="many-to-one" cfc="user" fkcolumn="userid" inversejoincolum="userid" lazy="true" cacheuse="read-only";
            property name="field" type="array" fieldtype="many-to-many" cfc="field" fkcolumn="id" linktable="items_fields" inversejoincolumn="fieldid" lazy="extra" batchsize="10" cacheuse="read-only";
    I also noticed in the stdout log that Hibernate is logging the query, but then it logs the "No session" error:
        Hibernate:
            select
                item0_.id as id0_0_,
                item0_.dtcreated as dtcreated0_0_,
                item0_.dtmodified as dtmodified0_0_,
                item0_.title as title0_0_,
                item0_.description as descript6_0_0_,
                item0_.status as status0_0_,
                item0_.userid as userid0_0_
            from
                item item0_
            where
                item0_.id=?
        Dec 2, 2014 15:23:00 PM Error [ajp-bio-8014-exec-3] - failed to lazily initialize a collection of role: field, could not initialize proxy - no Session The specific sequence of files included or processed is: service.cfc''
    I should probably also add that this "item" table is part of a many-to-many relationship, so "collection of role: field" is referencing the foreign table.

    I have an application that i am extending to provide a REST API.  Everything works fine in the main site, but I am getting the following in the exception log when I try to hit the REST API:
        "Error","ajp-bio-8014-exec-3","12/02/14","12:54:06","table","failed to lazily initialize a collection of role: field, could not initialize proxy - no Session The specific sequence of files included or processed is: service.cfc'' "
        org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: field, could not initialize proxy - no Session
            at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationExc eption(AbstractPersistentCollection.java:566)
            at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeed ed(AbstractPersistentCollection.java:186)
            at org.hibernate.collection.internal.AbstractPersistentCollection.readSize(AbstractPersisten tCollection.java:137)
            at org.hibernate.collection.internal.PersistentBag.size(PersistentBag.java:242)
            at coldfusion.runtime.xml.ListIndexAccessor.getSize(ListIndexAccessor.java:44)
            at coldfusion.runtime.xml.ArrayHandler.serialize(ArrayHandler.java:69)
            at coldfusion.runtime.xml.CFComponentHandler.serialize(CFComponentHandler.java:106)
            at coldfusion.runtime.XMLizerUtils.serializeXML(XMLizerUtils.java:83)
            at coldfusion.rest.provider.CFObjectProvider.writeTo(CFObjectProvider.java:378)
            at com.sun.jersey.spi.container.ContainerResponse.write(ContainerResponse.java:306)
            at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationIm pl.java:1479)
            at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImp l.java:1391)
            at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImp l.java:1381)
            at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
            at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
            at coldfusion.rest.servlet.CFRestServletContainer.service(CFRestServletContainer.java:141)
            at coldfusion.rest.servlet.CFRestServletContainer.service(CFRestServletContainer.java:86)
            at coldfusion.rest.servlet.CFRestServlet.serviceUsingAlreadyInitializedContainers(CFRestServ let.java:556)
            at coldfusion.rest.servlet.CFRestServlet.invoke(CFRestServlet.java:434)
            at coldfusion.rest.servlet.RestFilter.invoke(RestFilter.java:58)
            at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:94)
            at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8)
            at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
            at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
            at coldfusion.rest.servlet.CFRestServlet.invoke(CFRestServlet.java:409)
            at coldfusion.rest.servlet.CFRestServlet.service(CFRestServlet.java:400)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
            at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:303)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
            at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 )
            at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:241)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
            at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:422)
            at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:198)
            at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.jav a:607)
            at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    Disabling lazy loading will fix this, but results in unacceptable performance (load times go from 200ms to 22s).  I'm not sure how else to handle this.
    I am new to REST in ColdFusion, and it seems to me that the CFC's are being handled in an unusual way.  They do not appear to be initialized (init method does not seem to run) and now it seems that ORM is not handled the same either.  Am I missing something?
    Here is the excerpt of my code producing this error:
        component rest="true" restpath="item"
            import model.beans.*;
            remote item function getitem( numeric id restargsource="Path" ) restpath="{id}" httpmethod="GET"
                var item = entityLoad("item",{ id = id },true);
                return item;
    And the bean:
        component persistent="true" table="item" output="false" extends="timestampedBean" batchsize="10" cacheuse="read-only"
            /* properties */
            property name="id" column="id" type="numeric" ormtype="int" fieldtype="id" generator="identity";
            property name="title" column="title" type="string" ormtype="string";
            property name="description" column="description" type="string" ormtype="string";
            property name="status" column="status" type="numeric" ormtype="byte" default="0" ;
            property name="user" fieldtype="many-to-one" cfc="user" fkcolumn="userid" inversejoincolum="userid" lazy="true" cacheuse="read-only";
            property name="field" type="array" fieldtype="many-to-many" cfc="field" fkcolumn="id" linktable="items_fields" inversejoincolumn="fieldid" lazy="extra" batchsize="10" cacheuse="read-only";
    I also noticed in the stdout log that Hibernate is logging the query, but then it logs the "No session" error:
        Hibernate:
            select
                item0_.id as id0_0_,
                item0_.dtcreated as dtcreated0_0_,
                item0_.dtmodified as dtmodified0_0_,
                item0_.title as title0_0_,
                item0_.description as descript6_0_0_,
                item0_.status as status0_0_,
                item0_.userid as userid0_0_
            from
                item item0_
            where
                item0_.id=?
        Dec 2, 2014 15:23:00 PM Error [ajp-bio-8014-exec-3] - failed to lazily initialize a collection of role: field, could not initialize proxy - no Session The specific sequence of files included or processed is: service.cfc''
    I should probably also add that this "item" table is part of a many-to-many relationship, so "collection of role: field" is referencing the foreign table.

  • How to publish Work Manager 6.0 on SMP3.0 ?

    Hi SCN Community,
    I'm trying to get the Work Manager 6.0 running on SMP 3.0 (running on Linux). Currently the events.log within the Agentry folder states, that the Agentry Server was started. But If I look into the Threads*.log I see there might be a problem and I'm also not able to connect to the server.
    Unfortunately I couldn't find any manual or post where someone described the steps to get a work manager running on SMP 3.0. The SMP 3.0 server manual as well as the SDK manual just describing in general how to publish an application to the SMP 3.0. But for Work Manager, there might be some special things to be done ...
    Any help/hints are welcome!
    Here what I did so far:
    Install SMP 3.0 up to SP02 on Suse SLES 11
    Install SAP JCo 2.1.11 (test successful:  java -jar /DVD_HANA/jco/sapjco.jar -stdout )
    Create a new application in SMP with type Agentry and select security profile default
    Install SMP3.0 SDK SP02 (Agentry)
    Setup Eclispe 4.2.2 with Agentry Plugin 7.0.2
    Import a Work Manager 6.0 from Teamshare
    Export Agentry Project as a production version and point to the Agentry.ini which is in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application
    Include all jar files to the ZIP file
    Import the ZIP file within Agentry application in SMP 3.0
    Create JavaBE.ini in folder /opt/SAP/MobilePlatform3/Server which is copied from WM6.0 server
    Adjust Agentry.ini in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application  (see section config files)
    Restart Server
    Config files:
    Agentry.ini
    [Server Administration]
    authenticationCertificateStore=AgentryServer.pfx
    authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
    authenticationCertificateStorePasswordEncoded=true
    [System Connections]
    2=ag3httpxmlbe.dll
    1=ag3javabe.dll
    [Configuration]
    apnsCertificateDirectory=apnsCertificates
    apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
    apnsCertificatePasswordEncoded=True
    apnsEnabled=True
    applicationGlobalsFile=Globals.ini
    applicationStringsFile=ApplicationText.ini
    clientStringNamesFile=ClientStringNames.ini
    clientStringsFile=ClientText.ini
    developmentServer=False
    enableFailedTransactionLogging=True
    enableOverrideFile=Enables.ini
    enableTransactionFailureHandling=False
    failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
    failedTransactionsQueue=FailedTransactionsQueue
    gcmEnabled=True
    gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
    gcmServerLink=https://android.googleapis.com/gcm/send
    imagesPath=Application\Development\Images
    localizationPath=
    localizations=
    overrideInfoTableDirectory=OverrideInfoTable
    overrideTypesFile=OverrideTypes.ini
    postedTransactionDirectory=posted
    postedTransactionFile=%{device}.pli
    scriptsPath=Application\Development\Scripts
    spinDocIniFile=
    threadCount=0
    transmitConfigurationFile=TransmitConfigurations.ini
    trustedCertificateStore=
    updateIdleWait=60
    updatePeriod=60
    urlPath=
    [HTTPXML-2]
    authenticationCertificateStore=MY
    authenticationCertificateStorePassword=
    authenticationCertificateStorePasswordEncoded=False
    autoDequote=True
    baseURL=http://localhost:8282
    basicAuthenticationPassword=
    basicAuthenticationPasswordEncoded=False
    basicAuthenticationUserID=
    constantsFile=httpxml_sd.ini
    enableAuthentication=False
    enablePreviousUserAuthentication=False
    httpConnectTimeout=60
    httpReceiveTimeout=300
    httpResolveTimeout=60
    httpSendTimeout=300
    listenOn=
    name=2
    timeZoneName=
    timeout=300
    trustedCertificateStore=
    useSSL=False
    xmlNamespaces=
    [Java-1]
    classPath=./ini4j.jar;./Agentry-v5.jar;./Z_SAPWM-6.0.0.0.jar;./SAPWM-6.0.0.0.jar;./SAPCommon-130881.jar;
    constantsFile=
    deleteSource=True
    enableAuthentication=True
    enablePreviousUserAuthentication=True
    name=Java-1
    outputDirectory=.
    performCompile=True
    printBusinessLogicStackTrace=False
    printStackTrace=False
    scriptsPath=
    serverClass=com.syclo.agentry.Server
    sourceDirectory=.
    timeZoneName=
    [SpinDoc]
    facePath=sql\custom;sql
    facepath=sql\custom;sql
    [TimeZoneAlias]
    Log files:
    events.log
    02/27/2014 18:51:45, 0,         0,         0, Thr 140352349296384, New files opened events.log, messages.log
    02/27/2014 18:51:45, 0,         0,         2, Thr 140352349296384, Agentry Startup
    02/27/2014 18:51:45, 0,        17,        14, Thr 140352349296384, WebSockets Front End v7.0.2.151
    02/27/2014 18:51:45, 0,         1,         4, Thr 140352349296384, Agentry v7.0.2.151
    02/27/2014 18:51:45, 0,        20,       150, Thr 140352200132352, Loading Production application definitions using file "SAPWM-v1-0-0-app"
    02/27/2014 18:51:45, 0,        20,       152, Thr 140352200132352, Loading Production application definitions for default localization
    02/27/2014 18:52:07, 0,        20,       153, Thr 140352200132352, Finished loading Production application definitions for default localization
    02/27/2014 18:52:07, 0,        20,       151, Thr 140352200132352, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
    02/27/2014 18:52:08, 0,        24,         4, Thr 140352349296384, Loaded 2 (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
    02/27/2014 18:52:08, 0,        23,         4, Thr 140352349296384, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
    02/27/2014 18:52:08, 0,        20,         4, Thr 140352349296384, Server v7.0.2.151
    02/27/2014 18:52:08, 0,        17,        10, Thr 140352349296384, WebSockets Front End v7.0.2.151
    02/27/2014 18:52:08, 0,         0,         0, Thr 140352349296384, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-27-185145
    02/27/2014 18:52:08, 0,         0,        23, Thr 140352349296384, Agentry startup is complete.
    Thread-140352200132352.log
    2014/02/27 18:52:07.310: Opening log file
    2014/02/27 18:52:07.310: + Thread=140352200132352
    2014/02/27 18:52:07.310:   + Server=Agentry
    2014/02/27 18:52:07.310:     + Load Loop=Production
    2014/02/27 18:52:07.310:       + AppIniFile=SAPWM-v1-0-0-app
    2014/02/27 18:52:07.310:         + Module=PM
    2014/02/27 18:52:07.310:           + Service Event=WorkOrderPushHTTPListener
    2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'
    2014/02/27 18:52:07.310:           + Service Event=WorkorderPushByOperationHTTPListener
    2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'
    2014/02/27 18:52:07.311:           + Service Event=WorkorderPushBySubOperationHTTPListener
    2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'
    2014/02/27 18:52:07.311:           + Service Event=BDSDocumentPushHTTPListener
    2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'
    2014/02/27 18:52:07.311:           + Service Event=DMSDocumentPushHTTPListener
    2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'
    2014/02/27 18:52:07.311:           + Service Event=WorkorderPushByMRSHTTPListener
    2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'
    When trying to connect with the WPF client I get a communication error (14) and nothing is shown in the log files ..
    Best Regards,
    Michel

    Jason,
    deleting the service events was helpful regarding the error shown in the Thread log file. After publishing a new version the server seems to start, but has no activity to SAP. I expected at least an initial logon to the SAP system using the service user.
    Current log files are:
    events.log:
    02/28/2014 06:16:36, 0,         0,         0, Thr 140136552040192, New files opened events.log, messages.log
    02/28/2014 06:16:36, 0,         0,         2, Thr 140136552040192, Agentry Startup
    02/28/2014 06:16:36, 0,        17,        14, Thr 140136552040192, WebSockets Front End v7.0.2.151
    02/28/2014 06:16:36, 0,         1,         4, Thr 140136552040192, Agentry v7.0.2.151
    02/28/2014 06:16:36, 0,        20,       150, Thr 140136413689600, Loading Production application definitions using file "SAPWM-v1-1-0-app"
    02/28/2014 06:16:36, 0,        20,       152, Thr 140136413689600, Loading Production application definitions for default localization
    02/28/2014 06:17:06, 0,        20,       153, Thr 140136413689600, Finished loading Production application definitions for default localization
    02/28/2014 06:17:06, 0,        20,       151, Thr 140136413689600, Finished loading Production application definitions using file "SAPWM-v1-1-0-app"
    02/28/2014 06:17:06, 0,        24,         4, Thr 140136552040192, Loaded HTTP-XML Back End (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
    02/28/2014 06:17:06, 0,        23,         4, Thr 140136552040192, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
    02/28/2014 06:17:06, 0,        20,         4, Thr 140136552040192, Server v7.0.2.151
    02/28/2014 06:17:07, 0,        17,        10, Thr 140136552040192, WebSockets Front End v7.0.2.151
    02/28/2014 06:17:07, 0,         0,         0, Thr 140136552040192, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-28-061636
    02/28/2014 06:17:07, 0,         0,        23, Thr 140136552040192, Agentry startup is complete.
    messages.log is empty and Thread*.log doesn't exist anymore.
    Any further idea how to get this up and running?
    Best Regards,
    Michel

  • Required steps to add standard SAP field to Work Manager 6.0

    Dear Agentry experts,
    I need some help on how to add standard SAP backend fields to the Work Manager 6.0 application. The application is freshly setup and not yet customized apart from filters, so we are also new to develop it.
    Specifically we want to add fields QMTXT and QMCOD from Notification Header. We have checked and the fields are activated in the backend configuration, so I hope there are no changes required to the backend. However, when checking the data in the ATE, the fields are currently not added / available in the Notification Collection.
    I have searched this forum and found several pointers, but they deal with adding a full new field, and I want to keep changes limited. Can you please advise what specific steps I need to do on the Agentry / Eclipse side to close the gap between SAP backend and the Notification Collection. (I know how to add the fields to the UI if they are in the collection). Do we need to create custom Java Classes? Can I solve this by just Agentry configuration?
    Thank you very much for your kind advice!

    Look at the attachment, diagram depicts a data flow across the systems. You have to extend Java code for  the object  your trying to enhance and plus you have to make  necessary changes on  Agentry side as well.
    if you have access to Service Market place , check out  SAP-WM-6.0-EnhancementsGuide.pdf document under Work Manager 6.0 documentation which describes the steps involved in enhancing application.
    Alternatively you can also check this blog Syclo Customization Extension-First Steps.
    Syclo Customization Extension-First Steps
    Thanks
    Manju.

  • Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

    Hello Experts.
    I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.
    It has been installed successfully and does start up, however I get some annoying error messages during start up.
    It seems that the server is running - I can succesfully synchronize to an ATE client.
    Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.
    Port issues - SMP and Agentry
    Errors from the startup.log:
    13:26:00 05/05/2014: HTTP-XML Back End Back End: Started
    13:26:00 05/05/2014: Server: Starting threads.
    13:26:00 05/05/2014:    1 initial threads.  Threads will auto-scale.
    13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3
    13:26:00 05/05/2014: Starting front ends
    13:26:00 05/05/2014: ANGEL Front End: Starting threads.
    13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
    13:26:00 05/05/2014:    3 initial threads.  Threads will auto-scale.
    13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523
    13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
    13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open
    13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3
    13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
    13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546
    13:26:00 05/05/2014: Event: 0, 23, 4
    13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
    13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.
    13:26:01 05/05/2014: Agentry Application startup complete
    Can anybody help with the meaning and implications of these errors ?
    Thank you.
    Søren Hansen.

    Damn... I missed one port
    You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.
    Thanks Steve.
    For others:
    Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.
    Now the server starts without errors.
    [ANGEL Front End Ports]
    1=7523
    [TCP Front End]
    listenOn=7521
    [Java-1]
    nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n
    [HTTPXML-2]
    baseURL=http://localhost:7522
    listenOn=7525
    Søren Hansen.

  • Inspection Rounds in Work Manager 6.0

    Hi all,
    We've setup Work Manager 6.0 running on SMP2.3.  One of the functions that I'd like to get working is inspection rounds.
    We have
    Configued the standard order type PM01 to be an inspection rounds order in the work order MDO filter INSP_ORDER_TYPE.
    Assigned a measurement point PRT to the order operation.
    Added an Equipment number to the order operation.
    In work manager I am able to access the PRT screen from the Work Order Detail PRT link.  In that screen I can see the buttons for Tools, Inspection Types, Measuring Points, and Attachments.  In all my testing I've never seen a Measurement Point under the Measurement Point selection.
    When I've checked the data structure in the Agentry Test Environment the measurement point entries come up in the PRT section under the Operation section.  They are missing any value in the RecordID field.  Other PRT types have this information filled and I assume that it provides the link to the measurement point information downloaded for the functional location and equipment data structures under the operation structure.
    Inspection Rounds are working fine in the back end using standard confirmation transaction iw42.
    Any suggestions?
    thank you
    Steve.
    Tags edited by: Michael Appleby

    Thank you Syam,
    We have activated 'LOG_EAM_LINEAR_1' and '/SMERP/EHP5_EAM_BUS_FUNC' and we now get inspection round measurement points coming through to Work Manager.
    Separate switches for the functions in future releases is a solid idea.  Any customer who is not running linear assets will have to debate with their account manager if the want to use inspection rounds.  Linear generally attracts an additional license cost.
    Back to Inspection Rounds.  The measurement points come through only if the functional location or equipment record is explicitly specified on the operation.  In the ECC functionality any measurement point can be specified as long as it is in the hierarchy beneath the functional location/equipment referenced on the operation.  I assume that work manager limits this to minimise data sent to the device. 
    Does the parameter OBJECT_HIER_LEVEL'' on the 'WORKORDER_GENERIC' MDO have any impact on the collection of Functional Location and Equipment data at the operation level.  We are debugging and initially find a section of code relating to BDS documents.  Do you know the scope of the parameter?  Changing it's value seems to have no impact on the inclusion/exclusion of measurement points.  Debugging continues.....
    Ideally the get work order routine would be able to identify the required Functional Location and Equipment records from the measurement point PRTs themselves, that way only push the required records to the device, rather than a full hierarchy (assuming that full hierarchy was an option).  As it stands it looks like we'd need to implement a BADI to restrict the assignment of measurement point PRTs in ECC to only measurement points attached to the functional location and equipment record explicitly referenced on the operation.  If that wasn't done then you could add measurement PRTs in ECC that you couldn't process in Work Manager.
    Thank you again for your assistance.
    Steve.

  • How to create 2 Work Manager Apps on SMP Server (Agentry)

    Hi All,
    I encountered a problem with my SMP 2.3 SP3 in combination with Agentry  6.1.. and Work Manager 6.0.
    I have an already working version of WorkManger on my SMP Server on port 7003, but whenever I create another WorkManager version on a different port e.g. 7005 the SMP/Agentry Server displays the status STARTING but never finishes this processs state.
    The version of both Work Manager instances is the same, with the exception that the section [ANGEL Front End Ports] in the file Agentry.ini contains once the port 7003 and in the other file e.g. 7005.
    Has anyone a encountered a similar problem or is able to create two different WorkManager versions on the same AgentryServer?
    Regards,
    Thomas

    Hello Steve,
    thanks for your quick reply, the listenOn Port is at both applications the same I will fix that in a few seconds.
    the entry nonStandardJavaOptions is at both apps empty.
    the startup.log of the second application:
    14:16:58 03/19/2014: Starting server (64-bit Windows)
    14:16:58 03/19/2014: Administration client command port is 55086, status port is 55087
    14:16:58 03/19/2014: Looking for initial status connection...
    14:17:04 03/19/2014: Event: 0, 30, Admin client 10.33.160.94:55094 authenticated successfully.
    14:17:04 03/19/2014: Event: 0, 27, Admin client 10.33.160.94:55094 has connected
    14:17:04 03/19/2014: Reading system ini file.
    14:17:04 03/19/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
    14:17:04 03/19/2014: Starting log file.
    14:17:04 03/19/2014: Loading message groups.
    14:17:04 03/19/2014: Starting threads.
    14:17:04 03/19/2014:    1 initial threads.  Threads will auto-scale.
    14:17:04 03/19/2014: Starting Server: Agentry v6.1.3.10212
    14:17:04 03/19/2014: Event: 0, 2, System Startup
    14:17:04 03/19/2014: Loading 1 front ends
    14:17:04 03/19/2014: Loading front end from angelvine.dll
    14:17:04 03/19/2014: ANGEL Front End: reading init files.
    14:17:04 03/19/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
    14:17:04 03/19/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
    14:17:04 03/19/2014: Event: 0, 2, Key pair loaded successfully.
    14:17:04 03/19/2014: Starting Server Agent.
    14:17:04 03/19/2014: Agentry: Starting threads.
    14:17:04 03/19/2014:    1 initial threads.  Threads will auto-scale.
    14:17:04 03/19/2014: Agentry: Adding messages.
    14:17:04 03/19/2014: Event: 1, 4, Agentry v6.1.3.10212
    14:17:04 03/19/2014: Loading 1 agents
    14:17:04 03/19/2014: Loading agent from ag3.dll
    14:17:04 03/19/2014: Starting Server
    14:17:04 03/19/2014: Server: reading ini file
    14:17:04 03/19/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
    14:17:04 03/19/2014: SystemConnection-2: Reading configuration information.
    14:17:04 03/19/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
    14:17:04 03/19/2014: HTTP-XML Back End: Initialized.
    14:17:04 03/19/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
    14:17:05 03/19/2014: Initializing 1-Java from ag3javabe.dll
    14:17:05 03/19/2014: SystemConnection-1: Reading configuration information.
    14:17:05 03/19/2014: SystemConnection-1: Setting name to 'Java Back End'.
    14:17:05 03/19/2014: Java Back End: Initialized.
    14:17:05 03/19/2014: Java Back End: Java Virtual Machine loaded.
    14:17:08 03/19/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
    14:17:08 03/19/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
    14:17:08 03/19/2014: Java Back End: Initialized.
    14:17:08 03/19/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_22, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
    14:17:08 03/19/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
    14:17:08 03/19/2014: Event: 20, 152, Loading Production application definitions for default localization

  • Default Collection Option Set

    I currently use multiple collectors that I have created to scan different locations based upon IP Ranges. I have created them so that the collection is spread out over a one week period to minimize network activity.
    I have been directed to change my collection so that it happens every Sunday. All machines in the company are now "woken up" every Sunday to receive any necessary patches. I will be changing my collection schedule so that my inventories take place on Sunday also but I have a question about the Default Collection Option Set.
    Would it be better to make use of the Default Collection Option Set or should I create a separate Collection Set for this task? Also since I have only targeted specific IP Ranges in the past what should my settings be to ensure that I am looking at the entire network?
    I also do not remember - when they wake up the systems on the network will the machines inventory from the Login Page or do they actually need to be logged onto the network to complete the inventory.

    Originally Posted by DaryRo
    Would it be better to make use of the Default Collection Option Set or should I create a separate Collection Set for this task?
    I always create my own option sets and give them meaningful titles to make it a little easier to track what is going on. There is really no need (or advantage) to using the Default Option Set.
    Originally Posted by DaryRo
    Also since I have only targeted specific IP Ranges in the past what should my settings be to ensure that I am looking at the entire network?
    If you really want that one option set to collect from all clients then just the default settings in a new option set will work as long as you select a valid schedule on the first tab when creating the option set.
    Make sure that any new option set you create that you wish to use is actually associated to collection servers. Look at the properties of the collection servers and if they are set to inherit standard option sets then add the new option set in the Collection Server, Domain properties, if they are not set to inherit then add the new option set to each collection server.

  • How to configure the work manager java code to eclipse?

    Hello all,
                   I am working with the syclo work manager app. I have successfully installed all components required.
                   I imported the work manager mobile application and I want to import the standard work manager java code, what is the process to import java code into work space.
                   Guide me with some screen shots.
                   When I try to start the WM server it is giving me the following error:
    How to resolve the error.
    Please anyone provide me complete setup needed to run the work manager app smoothly.
    Please guide me.
    Thanks & Regards,
    Swaroopa.

    Swaroopa,
    That error is telling you the SAP JCo library cannot find one of the needed DLLs on the system.  The sapjco.jar loads two additional DLL files (sapjcorfc.dll and librfc32.dll).  Both should be installed by default into your ServerDev directory (assuming you are running Agentry 6.0.x).
    I would guess it is having trouble loading the librfc32.dll based on the message but confirm both are in the correct location.
    --Bill

  • Oracle service bus: Work manager and Throttling

    Hi
    Flow is PS_C--->BS_A (based on PS_A)
    I created a http protocol based proxy service PS_A and a business service based on PS_A, i.e. BS_A.
    Now this BS_A is deployed on four different managed servers. I have implemented failover so at a time copy of only one of the managed severs will be accessed by multiple external clients through PS_C. To say all will hit Managed server-1 copy of BS_A. If Managed server-1 is down then it will hit Managed server-2 copies of BS_A.
    I have created a workmanager named "CustomWorkManager" which has MaxThreadConstraint=1. PS_A has not enabled CustomWorkManager. i.e. PS_A works under default policy.
    My goal is to process only one request at one time through BS_A.
    In business service, BS_A I can see work manager and throttling options.
    My question is this:
    Scenario I: I make throttling enabled and set maximum concurrency=1 for BS_A
    Scenario II: I apply CustomWorkManager to BS_A
    Scenario III: I do both Scenario I and Scenario II
    What is the difference between I, II and III?
    Fundamentally, what is the difference between throttling with maxConcurrency=1 and MaxThreadConstraint of workmanager=1 for a http business service?
    Thanks and Regards,
    Swapnil Kharwadkar

    @Abhishek: Thanks for descriptive reply.
    @Anuj: Thanks for links, I am having a look..
    Use case:
    What is the target app/service? Is it DB, HTTP or anything else?
    Back end: Amadeus web services
    Role of DB:
    1. It will store data to attach transaction context to a request. This is to call more than one services in the backend - it is necessary for backend to understand in which context services are being invoked.
    For example, if I need to make PNR related changes, I need to invoke service X and fetch transaction context from back-end. The transaction specific identifier (read session) will be received in header part. After retrieve suppose I need retrieve PNR, I will invoke service Y. When I invoke, I need to put the transaction specific header part received in response of service X and then change body as per request format of service Y (read the response header of X will be the same as request and response header of Y) which will actually make changes and commit in the backend. (So back-end will understand that service X and Y are invoked as a part of single transaction, and transaction can be identified through logs)
    3. Once my X+Y call is over and transaction is committed, the context for transaction specific part received in header to the transaction is removed from back-end. Then I can use session again for the next transaction.
    4. To re-use session I am storing it in DB and retrieving as per need for each call to Amadeus.
    Problem is, it is absolute necessary for all transactions which are being processed simultaneously, to have unique session in header.
    For example,
    I do the following:
    Request 1: receives session from service X, uses for service Y. After use, inserts session in DB. Now context for that session is removed from back-end.
    Request 2: looks for session DB, puts in header and invokes backend. Context for Request 2 is attached to session retrieved from DB.
    Request 3: looks for session DB, puts in header and invokes backend. Context for Request 3 is attached to session retrieved from DB.
    As you can see if Request 2 and Request 3, pick up the same session from DB and invoke back-end, back-end services won't be able to understand which request the session belongs to, and will fail both requests. Ideally Request 2 should retrieve it from DB use for itself and Request 3 should make a call to service X at back-end to receive context. With this new context Request 3 should proceed for transaction.
    Why are you using a BS to call from one Proxy to another Proxy?:
    1. To interact with DB, I use DBAdapter business services with QueryByExample/Update/Insert operation.
    2. My PS_A is proxy which orchestrates these operations. (Read: SelectandUpdateDBForSessionRetrieve, UpdateDBWhenTransactionOver functionaries) Since there are two admin and four managed servers, all copies of PS_A will try to access DB simultaneously, and concurrency will fail.
    3. Hence I made BS_A on the basis of PS_A. BS_A is deployed on all four managed servers, used Load Balancing Algorithm as "None" and gave hard-coded urls of four managed servers in sequence of MS1, MS2, MS3 and MS4.
    4. Idea is if MS1 is ok, all requests will go to BS_A of MS1 only, and if somehow if I make it single threaded *(Read from DB+mark retrieved data as "in use" so other request can not use it)*, concurrency issue will not arise. In case MS1 is down, the requests will automatically forwarded to MS2 and since that is also single threaded, concurrency issue won't arise. In short both fail-over and concurrency can be achieved with BS_A making out of PS_A.
    The problem as you have correctly pointed out, is that OSB is stateless and one request has no relation with another. Somehow, I need to make every retrieve/update/insert to database as single threaded, i.e. once one is done then another should not be done at the same time. Else entire point of this pooling will fail.
    Please share any thoughts you might have. Even another approach to handle this single threaded need will do.
    Thanks and Regards,
    Swapnil Kharwadkar

  • SAP Work Manager status STOPPED in SCC

    Hi All,
    We have installed and deployed SAP Work Manager 6.0 on SMP 2.3. In the SCC it shows the app was registered or started successfully, however the Agentry instance server status is STOPPED. The Task Manager shows the Agentry Server is running, and can actually accessed from ATE.
    The problem is we can't see anything in any of the other tabs. The tab Configurations is blank and we are not able to see or maintain any settings and/or parameters. The other tabs are also blank, for example Logs is not pulling in the data from the log files. See screenshots below.
    The startup.log is also noit giving me any indications or errors. See also below.
    Any suggestions as to what might be wrong? And how this can be resolved?
    Kind regards,
    Edwin
    STARTUP.LOG
    09:16:47 03/27/2014: Starting server (64-bit Windows)
    09:16:48 03/27/2014: Administration client command port is 60880, status port is 60881
    09:16:48 03/27/2014: Looking for initial status connection...
    09:16:58 03/27/2014: Event: 0, 2, Status connection not detected.  Continuing startup
    09:16:58 03/27/2014: Reading system ini file.
    09:16:58 03/27/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
    09:16:58 03/27/2014: Starting log file.
    09:16:58 03/27/2014: Loading message groups.
    09:16:58 03/27/2014: Starting threads.
    09:16:58 03/27/2014:    1 initial threads.  Threads will auto-scale.
    09:16:58 03/27/2014: Starting Server: Agentry v6.1.3.10212
    09:16:58 03/27/2014: Event: 0, 2, System Startup
    09:16:58 03/27/2014: Loading 1 front ends
    09:16:58 03/27/2014: Loading front end from angelvine.dll
    09:16:58 03/27/2014: ANGEL Front End: reading init files.
    09:16:58 03/27/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
    09:16:58 03/27/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
    09:16:58 03/27/2014: Event: 0, 2, Key pair loaded successfully.
    09:16:58 03/27/2014: Starting Server Agent.
    09:16:58 03/27/2014: Agentry: Starting threads.
    09:16:58 03/27/2014:    1 initial threads.  Threads will auto-scale.
    09:16:58 03/27/2014: Agentry: Adding messages.
    09:16:58 03/27/2014: Event: 1, 4, Agentry v6.1.3.10212
    09:16:58 03/27/2014: Loading 1 agents
    09:16:58 03/27/2014: Loading agent from ag3.dll
    09:16:59 03/27/2014: Starting Server
    09:16:59 03/27/2014: Server: reading ini file
    09:17:00 03/27/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
    09:17:00 03/27/2014: SystemConnection-2: Reading configuration information.
    09:17:00 03/27/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
    09:17:00 03/27/2014: HTTP-XML Back End: Initialized.
    09:17:00 03/27/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
    09:17:00 03/27/2014: Initializing 1-Java from ag3javabe.dll
    09:17:00 03/27/2014: SystemConnection-1: Reading configuration information.
    09:17:00 03/27/2014: SystemConnection-1: Setting name to 'Java Back End'.
    09:17:00 03/27/2014: Java Back End: Initialized.
    09:17:02 03/27/2014: Java Back End: Java Virtual Machine loaded.
    09:17:07 03/27/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
    09:17:07 03/27/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
    09:17:07 03/27/2014: Java Back End: Initialized.
    09:17:07 03/27/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_35, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
    09:17:07 03/27/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
    09:17:07 03/27/2014: Event: 20, 152, Loading Production application definitions for default localization
    09:17:18 03/27/2014: Event: 20, 153, Finished loading Production application definitions for default localization
    09:17:18 03/27/2014: Event: 20, 151, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
    09:17:18 03/27/2014: HTTP-XML Back End Back End: Started
    09:17:18 03/27/2014: Server: Starting threads.
    09:17:18 03/27/2014:    1 initial threads.  Threads will auto-scale.
    09:17:19 03/27/2014: Event: 20, 4, Server v6.1.3.10212
    09:17:19 03/27/2014: Starting front ends
    09:17:19 03/27/2014: ANGEL Front End: Starting threads.
    09:17:19 03/27/2014:    3 initial threads.  Threads will auto-scale.
    09:17:19 03/27/2014: ANGEL Front End: opening listen socket on port 7003
    09:17:19 03/27/2014: Event: 17, 10, 0.0.0.0:7003 open
    09:17:19 03/27/2014: Event: 17, 10, ANGEL Front End v6.1.3.10212
    09:17:19 03/27/2014: Event: 0, 0, Old log files moved into E:\SAP\MobilePlatform\Servers\UnwiredServer\logs\com.sap.wm\Rolled\2014-03-27-091647
    09:17:19 03/27/2014: Event: 0, 23, SAP Mobile Platform
    09:17:19 03/27/2014: Event: 0, 2, Server startup is complete.
    09:17:19 03/27/2014: Agentry Application startup complete

    Hi Stephen,
    We installed SP04, but we are still experiencing the same issue. We even went as far as deleting and re-deploying the app.
    Again it shows the app registered successfully:
    On the General tab it still shows status STOPPED:
    The other tabs don't show anything, e.g. Configurations or Logs:
    After restarting SMP the node completely disappears:
    The Region & Language settings on the SMP server:
    Any further suggestions are much appreciated.
    Regards,
    Edwin

  • How do I stop/remove screen saver photos in default collections?

    I installed Mavericks with no problems, however, I want to get rid of the screen savers/default collections. The desktop/wallpaper seems to be working fine: it rotates through my own "desktop pictures" collection.  However, I have been unable to eleminate the default collections photos from the screen savers. In System Preferences the source for screen savers is my "desktop pictures" folder, and my photos do come up, however, all the default collections photos are mixed in. If I uncheck Shuffle Slide Order, the default collections photos come on first.
    Now, here's the mystery: I deleted (with a Secure Empty Trash) the default collections photos! The folder is empty. I've also put all the
    com.apple.screensaver..... plist files in the trash. But they aren't deleted. Where are these photos coming from?  Why do they still show up? What do I have to do to get rid of them? I've searched the hard drive (as best I can) using a couple of the file names, but nothing comes up. Would I get a better search by using Terminal?

    Screen Saver changes on it’s own

  • Looking up a custom work manager

    Hi All,
    I'm a little stumped with accessing a custom work manager in WLS 9.2. I think I've followed the docs exactly.
    I tried to use the default wm by looking up "java:comp/env/wm/default" and that worked fine. I didn't in any was define that in any config files. I then created 2 custom work managers in weblogic.xml and named them "sync" and "async." In web.xml I added 2 resource refs to those same names, matching the "sync" and "async" names like the docs say. However looking them up by either "java:comp/env/wm/sync" or just "sync" gave me a NameNotFoundException.
    I also tried defining the work managers in weblogic-application.xml and omitting the resource-ref, but that didn't work. I do see the work managers show up in the console. If I define them in weblogic.xml, they show up under the web app and if I define them in weblogic-application.xml, they show up under the app (ear.)
    What step am I missing?
    The instructions I'm using are at the bottom of this page: http://download.oracle.com/docs/cd/E11035_01/wls100/config_wls/self_tuned.html
    thanks
    john

    I got it working. I don't know what I was doing wrong before.
    My weblogic-application.xml contains this:
        <work-manager>
          <name>sync</name>
          <fair-share-request-class>
            <name>half share</name>
            <fair-share>100</fair-share>
          </fair-share-request-class>
        </work-manager>
        <work-manager>
          <name>async</name>
          <fair-share-request-class>
            <name>half share</name>
            <fair-share>100</fair-share>
          </fair-share-request-class>
        </work-manager>My web.xml contains this:
      <resource-ref>
        <res-ref-name>sync</res-ref-name>
        <res-type>commonj.work.WorkManager</res-type>
        <res-auth>Container</res-auth>
      </resource-ref>
      <resource-ref>
        <res-ref-name>async</res-ref-name>
        <res-type>commonj.work.WorkManager</res-type>
        <res-auth>Container</res-auth>
      </resource-ref>And my jndi lookup looks like this:
    WorkManager wm = (WorkManager)context.lookup("java:comp/env/sync");thanks

Maybe you are looking for

  • Unable to change the operating mode in informatica admin tool.

    hi i have installed Informatica 8.6.0 my repository service is running . and i have also created the integration service but its not running, the reason as i fount out in various blogs is that my repository is iin exclusive mode . so , i tried to cha

  • Configuration of JMS receiver  Using Jboss JMS provider

    Hi all.. I am configuring JMS adapter as receiver. I am using JMS provider JBOSS . I hav done configuration as Transport protocol :Acess JMS provider with JNDI JNDI lookUp Name of q connection factory: org.jboss.naming.LinkRefPairService Name of JNDI

  • Copy user setting

    Hi,     I used this query for copy user setting from Manager to all other users. This query running successfully but problem is this all the setting is copied but manager user lost all settings i.e all udf's come under general category which is previ

  • Lion replaces text with 'block A' characters in safari

    about 1/4 of the sites i vist now (including my own--in safari) have a 'block A' character where there is html text. does anyone know how to fix this? thanks.

  • Lost connection to my wireless router

    My HP printer has been working for 2 years and all of a sudden I can't print.  I had someone set up my printer back in the say so I don't know much. I am not tech savy but hope to acquire some help.  I have printed the wireless network test results p