SAPLOGON GROUPS JDO

Hello:
I have the sneak preview WAS Server Java 6.4 (J2EE)
and I have also installed the MINIWAS 6.2..
When I select the groups in SAPLOGON
Systemid      BSP</b>
Message Server      acme
and click on Generate list, I get following mistake:
"Message Server could not find any Groups"
I can contactthe message server, but I can´t find the group.
My server files and my activities:
1.My MINIWAS 6.2 files
     DEFAULT.PFL
     SAPSYSTEMNAME = BSP
     SAPDBHOST = acme
     rdisp/mshost = acme
     rdisp/sna_gateway = acme
     rdisp/sna_gw_service = sapgw00
     rdisp/vbname = acme_BSP_00
     rdisp/enqname = acme_BSP_00
     rdisp/btcname = acme_BSP_00
     rdisp/bufrefmode = sendoff,exeoff
     login/system_client = 000
     ZTTA/DEFTITLE = "SAP ABAP Engine"
2.message server port in the WINDOWSsystem32driversetcservices
     sapdp00          3200/tcp
     sapmsBSP         3600/tcp
3. ABAP stack and start the transaction SMLG
     CCMS --> SMLG
     Logon Group     Instance
     PAPAS          acme_BSP_00
               Assignment-dependet
               acme_BSP_00
               IP address 127.0.0.1V
               roups-dependent
               ext RFC-anabled
     PUBLIC          ACME_BSP_00
               Assignment-dependet
               acme_BSP_00
               IP address 127.0.0.1V
               roups-dependent
               ext RFC-anabled
I want to call JDO sdl and it´s very important for me, to find the groups.
Can anyone please help me?
Thanks a lot.
Best wishes

Hello Gregor,
Many thanks for your answer.
I started the SAP APAP Engine and then
tested with netstat.
Active connections
Proto Local Adress           Remoteadresse          Status
TCP    acme:1862              10.10.0.10:sapmsBSP    HERGESTELLT
TCP    acme:1913              10.10.0.10:65000       HERGESTELLT
TCP    acme:1928              10.10.0.10:sapmsBSP    WARTEND
TCP    acme:sapmsBSP          10.10.0.10:1862        HERGESTELLT
TCP    acme:65000             10.10.0.10:1913        HERGESTELLT
TCP    acme:1866              acme:sapgw00           HERGESTELLT
TCP    acme:1918              acme:sapgw00           HERGESTELLT
TCP    acme:1920              acme:sapgw00           HERGESTELLT
TCP    acme:sapgw00           acme:1866              HERGESTELLT
TCP    acme:sapgw00           acme:1918              HERGESTELLT
TCP    acme:sapgw00           acme:1920              HERGESTELLT
Prozess erfolgreich beendet.
Prozess erfolgreich beendet.
It seemed, that I get connection with the false port.
My MS Loopback Adapter
IP address 10.10.0.10
sub net mask 255.255.255.0
Can you see the mistake and help me?
Regards
Georgios

Similar Messages

Ann: new JDO/DAO mail list

I have added a new mail list "JDO" at
http://www.basebeans.net:8080/mailman/listinfo/jdo

aimed at talking about DAO, such as JDO by KODO, DB Layer by iBatis,
Commons-SQL by Jakarta, JDBC RowSet, Hibernate, JDOSQL, Connection Pooling,
JDBC Realms, ADO.net, SQL, Stored Porcedures, sql.Date, Blob, Clob,
Connection Pooling, Data source, Castor, Cayene, Scaffolding, etc. and
related, in general Model Component (of MVC) and . DAO! Both SQL based DAO
and O/R based DAO how to. This list is also available via news form server,
for those that find mail lists messy, as most do at:
news.basebeans.com, just user your Outlook or Mozilla.

Please join this new JDO mail list, I found not other JDO/DAO mail lists out
there.

This is 1st new list a long time (other one is
http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers ) for
experienced project and tech leads, basicPortal.sf.net and Struts training.
Other mail lists that you can easily read there without getting any mail
traffic are: Struts, JDOM, Hibernate, SOAP Axis, JSP, AspectJ, Eclipse,
Flash Action Script, Resin, pgSQL, mySQL, etc. If you already use
news.basebeans.com, you will have to hit refresh to get the new groups (JDO
and Flash actionscript)

Flash is the other new one only one the news.basebeans, I started sending
XML from my formBeans to Flash Fire Fly with good results.

Thanks,

Vic Cekvenich,
1-800-917-JAVA
or 800-314-3295
Advanced <a href ="baseBeans.com">Struts Training</a> and project recovery
in North East. <p>
Open Source <a href ="baseBeans.com">Content Management</a> basic Portal
sofware<p>
Best practice<a href ="baseBeans.com">Supported Struts v.1.1</a> framework
ScafflodingXPress<p>

I have added a new mail list "JDO" at
http://www.basebeans.net:8080/mailman/listinfo/jdo

aimed at talking about DAO, such as JDO by KODO, DB Layer by iBatis,
Commons-SQL by Jakarta, JDBC RowSet, Hibernate, JDOSQL, Connection Pooling,
JDBC Realms, ADO.net, SQL, Stored Porcedures, sql.Date, Blob, Clob,
Connection Pooling, Data source, Castor, Cayene, Scaffolding, etc. and
related, in general Model Component (of MVC) and . DAO! Both SQL based DAO
and O/R based DAO how to. This list is also available via news form server,
for those that find mail lists messy, as most do at:
news.basebeans.com, just user your Outlook or Mozilla.

Please join this new JDO mail list, I found not other JDO/DAO mail lists out
there.

This is 1st new list a long time (other one is
http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers ) for
experienced project and tech leads, basicPortal.sf.net and Struts training.
Other mail lists that you can easily read there without getting any mail
traffic are: Struts, JDOM, Hibernate, SOAP Axis, JSP, AspectJ, Eclipse,
Flash Action Script, Resin, pgSQL, mySQL, etc. If you already use
news.basebeans.com, you will have to hit refresh to get the new groups (JDO
and Flash actionscript)

Flash is the other new one only one the news.basebeans, I started sending
XML from my formBeans to Flash Fire Fly with good results.

Thanks,

Vic Cekvenich,
1-800-917-JAVA
or 800-314-3295
Advanced <a href ="baseBeans.com">Struts Training</a> and project recovery
in North East. <p>
Open Source <a href ="baseBeans.com">Content Management</a> basic Portal
sofware<p>
Best practice<a href ="baseBeans.com">Supported Struts v.1.1</a> framework
ScafflodingXPress<p>

Set FQDN in Logon Group

Hi Gurus,
In SMLG - Maintain Logon Groups, is there possible to set fully qualified domain name (FQDN) instead of IP address to Logon Group?
This is because if I only set the Public IP for this Logon Group, internal user in LAN is not able to use this Logon Group to access R3.
Anyone has any idea? Please help.
Thanks,
HauChee

Hi Hau,
(Sorry if Hau is not your first name !)
It is not possible to enter a FDQN as the help is :
IP address
(Numeric) IP address of the application server. This should be specified only if the application host belonging to the instance has to be addressed from the frontend side using a different IP address than that used for communication within the application host. This could be the case if, for example, the communication from application host to application host uses a different network than that used for the communication from the frontend to application host
I think you need the 2 different saplogon groups AND you need to find a way from the portal to check if the laptop is connected internally or externally. The portal would then choose the right saplogon group :
Also, I don't really understand the need : I think it would be much nicer for your users to use directly sapgui when connected internally than webgui.
webgui, IMHO is just an acceptable way to work when not in house.
Regards,
Olivier

Cannot enable SNC in SAPlogon with alternative IP address in SMLG groups

Hello everyone,
I am looking for someone who has overcome the following situation:
We run SAP Enterprise on Unix (640 kernel). The systems have 2 networks - one for internal server communications and one for end-user connections. This requires that in our production logon group (multiple servers) that we specify the end-user IP address as an alternative IP in SMLG (otherwise SAP returns the internal network IP to the client).
However, when I try to enable SNC in SAPlogon to the production logon group, the "enable SNC" flag is grayed out. I have also tried to manually configure the entry in saplogon.ini. This results in a logon balancing module error. All of this seems to be described in OSS note 913356. The note is not very clear, but seems to list a corrected kernel level for version 4.6D. Thinking that this might be true for 640, I updated the kernel to 640 patch 159. This did not resolve the problem.
I should also state that direct saplogon connections to production with SNC do work. The problem appears to be in the logon module.
Has anyone else experienced this situation? Any help would be highly appreciated.
Paul
Basis Admin, Medrad

> Hi Paul,
>
> I would read the note like SNC only being available
> starting with NW2004s (700 kernel).
>
> Regards, Patrick
Saying that "SNC is only available starting with NW2004s" could be missinterpreted. Instead, I think it is better to say that "When using load balancing with SNC, for logon to SAP, and using an alternative IP address only works out-of-box with NW2004s". We have many customers using SNC authentication products with load balancing on releases prior to NW2004s, so this patch must be required only because of the alternative IP address being added to the logon group configuration.
Thanks,
Tim

JDO Spec Discussion Group/Mailing List

Is there a newsgroup, mailing list or other forum where users of the JDO
spec and it's implementations can discuss the spec, best practices, ask
general spec-related (rather than implementation) questions, etc?
Thanks.
Sasha Haghani
Activience
http://www.activience.com/

Hi,
I have used the group mailing list feature and the group web service maillist archive.
In both cases the Mail service must be running. I set up the General panel to Enable POP and IMAP because I have users on those services. I did not Enable SMTP because I used my ISP for outgoing. I don't think you need IMAP or POP for teamsserver mail because no mailbox is created for that user by cyrus or postfix.
In the Relay panel set to accept SMTP relays from 127.0.0.1 and your server IP.
Use junk mail rejection from zen.spamhaus.org
In the Mailing lists panel Enable server group mailing list.
In the Advanced panel -> Hosting ensure you have a local host alias set for your groups domain.com
Group mailing list can be setup in WGM with Enable Mailing list for the group.
Group Mailing list web archive will only work when wiki/blogs are setup for the group.
HTH,
Harry

JDO & CMP Non-sensical Failures & Errors

I have an ejb-jar project I'm working on creating with the SJAS 8.1 build b41-fcs.
Attempting to deploy gives me the following sensless error.
     [exec] JDO72313: The field person must be consistently defined as either a CMP field or a CMR.
     [exec] Please check for an inconsistency in your module contents (beans, deployment descriptor, cmp-mapping, ejb-jar).
     [exec] JDO74025: JDOCodeGenerator: Caught an Exception validating CMP bean 'PersonBean' in application 'UmcBase' module 'UmcBase': JDO72326: The field thisRelationshipFieldWasGeneratedByTheNameMapper1 has an invalid related field person. Related fields must be set for both relationship fields.
     [exec] Make sure the CMR field is set on both sides of the relation.I have checked, double-checked, triple-checked, etc. The definition is consistant.
Further, the relationship is currently mapped as a one-way relationship. It shouldn't be defined on the other side at this point in time.
I decided to try re-mapping the files with deploytool (a "tool" I try to avoid like the plague) and get the following error message from deploy tool:
JDO7704: This error (In DatabaseGenerator, failed to get 'relMappingClass' for 'byte[]') should not occur. Please contact support and file a bug.Oh freakin' great.
Any suggestions? I sorta need this to work.

Absolutely.
sun-cmp-mappings.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-cmp-mappings PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.0 OR Mapping//EN" "http://www.sun.com/software/appserver/dtds/sun-cmp-mapping_1_1.dtd">
<sun-cmp-mappings>
     <sun-cmp-mapping>
          <schema/>

          <entity-mapping>
               <ejb-name>BeanKeyBean</ejb-name>
               <table-name>BeanKey</table-name>
               <cmp-field-mapping>
                    <field-name>beanName</field-name>
                    <column-name>BeanKey.beanName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>nextId</field-name>
                    <column-name>BeanKey.nextId</column-name>
               </cmp-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>PreferenceDataBean</ejb-name>
               <table-name>PreferenceData</table-name>
               <cmp-field-mapping>
                    <field-name>dataId</field-name>
                    <column-name>PreferenceData.preferenceDataId</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>keyName</field-name>
                    <column-name>PreferenceData.keyName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>objectValue</field-name>
                    <column-name>PreferenceData.data</column-name>
               </cmp-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>node</cmr-field-name>
                    <column-pair>
                         <column-name>PreferenceData.preferenceNodeId</column-name>
                         <column-name>PreferenceNode.preferenceNodeId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>PreferenceNodeBean</ejb-name>
               <table-name>PreferenceNode</table-name>
               <cmp-field-mapping>
                    <field-name>name</field-name>
                    <column-name>PreferenceNode.nodeName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>nodeId</field-name>
                    <column-name>PreferenceNode.preferenceNodeId</column-name>
               </cmp-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>parentNode</cmr-field-name>
                    <column-pair>
                         <column-name>PreferenceNode.parentNodeId</column-name>
                         <column-name>PreferenceNode.preferenceNodeId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>children</cmr-field-name>
                    <column-pair>
                         <column-name>PreferenceNode.preferenceNodeId</column-name>
                         <column-name>PreferenceNode.parentNodeId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>data</cmr-field-name>
                    <column-pair>
                         <column-name>PreferenceNode.preferenceNodeId</column-name>
                         <column-name>PreferenceData.preferenceNodeId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>PersonBean</ejb-name>
               <table-name>Person</table-name>
               <cmp-field-mapping>
                    <field-name>dateOfBirthDb</field-name>
                    <column-name>Person.dateOfBirth</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>firstNameDb</field-name>
                    <column-name>Person.firstName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>gender</field-name>
                    <column-name>Person.gender</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>lastNameDb</field-name>
                    <column-name>Person.lastName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>middleNameDb</field-name>
                    <column-name>Person.middleName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>personId</field-name>
                    <column-name>Person.personId</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>salutation</field-name>
                    <column-name>Person.salutation</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>suffix</field-name>
                    <column-name>Person.suffix</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>activeDb</field-name>
                    <column-name>Person.active</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>hashKey</field-name>
                    <column-name>Person.hashKey</column-name>
               </cmp-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>personUser</cmr-field-name>
                    <column-pair>
                         <column-name>Person.personId</column-name>
                         <column-name>PersonUser.personId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>groups</cmr-field-name>
                    <column-pair>
                         <column-name>Person.personId</column-name>
                         <column-name>PersonGroup.personId</column-name>
                    </column-pair>
                    <column-pair>
                         <column-name>PersonGroup.groupId</column-name>
                         <column-name>Groups.groupId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>PersonUserBean</ejb-name>
               <table-name>PersonUser</table-name>
               <cmp-field-mapping>
                    <field-name>personId</field-name>
                    <column-name>PersonUser.personId</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>loginName</field-name>
                    <column-name>PersonUser.loginName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>passwordHash</field-name>
                    <column-name>PersonUser.passwordHash</column-name>
               </cmp-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>GroupBean</ejb-name>
               <table-name>Groups</table-name>
               <cmp-field-mapping>
                    <field-name>groupId</field-name>
                    <column-name>Groups.groupId</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>name</field-name>
                    <column-name>Groups.groupName</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>description</field-name>
                    <column-name>Groups.description</column-name>
               </cmp-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>groupMembers</cmr-field-name>
                    <column-pair>
                         <column-name>Groups.groupId</column-name>
                         <column-name>PersonGroup.groupId</column-name>
                    </column-pair>
                    <column-pair>
                         <column-name>PersonGroup.personId</column-name>
                         <column-name>Person.personId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>CountryBean</ejb-name>
               <table-name>Country</table-name>
               <cmp-field-mapping>
                    <field-name>countryCode</field-name>
                    <column-name>Country.code</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>name</field-name>
                    <column-name>Country.name</column-name>
               </cmp-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>StateProvinceBean</ejb-name>
               <table-name>StateProvince</table-name>
               <cmp-field-mapping>
                    <field-name>stateProvinceCode</field-name>
                    <column-name>StateProvince.code</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>name</field-name>
                    <column-name>StateProvince.name</column-name>
               </cmp-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>country</cmr-field-name>
                    <column-pair>
                         <column-name>StateProvince.country</column-name>
                         <column-name>Country.code</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
          </entity-mapping>

          <entity-mapping>
               <ejb-name>SecurityQuestionBean</ejb-name>
               <table-name>SecurityQuestion</table-name>
               <cmp-field-mapping>
                    <field-name>securityQuestionId</field-name>
                    <column-name>SecurityQuestion.securityQuestionId</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>type</field-name>
                    <column-name>SecurityQuestion.type</column-name>
               </cmp-field-mapping>
               <cmp-field-mapping>
                    <field-name>answer</field-name>
                    <column-name>SecurityQuestion.answer</column-name>
               </cmp-field-mapping>
               <cmr-field-mapping>
                    <cmr-field-name>person</cmr-field-name>
                    <column-pair>
                         <column-name>SecurityQuestion.personId</column-name>
                         <column-name>Person.personId</column-name>
                    </column-pair>
                    <fetched-with>
                         <none/>
                    </fetched-with>
               </cmr-field-mapping>
          </entity-mapping>
     </sun-cmp-mapping>
</sun-cmp-mappings>ejb-jar.xml (Entire thing, so you get the full picture)
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
     <display-name>UMCBaseJAR</display-name>
     <enterprise-beans>

          <entity>
               <ejb-name>BeanKeyBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.beanKey.BeanKeyLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.beanKey.BeanKeyLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.beanKey.BeanKeyBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>BeanKey</abstract-schema-name>
               <cmp-field>
                    <field-name>beanName</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>nextId</field-name>
               </cmp-field>
               <primkey-field>beanName</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
          </entity>

          <entity>
               <ejb-name>PreferenceDataBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.preferenceData.PreferenceDataLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.preferenceData.PreferenceDataLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.preferenceData.PreferenceDataBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>PreferenceData</abstract-schema-name>
               <cmp-field>
                    <field-name>objectValue</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>keyName</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>dataId</field-name>
               </cmp-field>
               <primkey-field>dataId</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
               <query>
                    <query-method>
                         <method-name>findDataForNode</method-name>
                         <method-params>
                              <method-param>edu.umc.umcBase.bean.ejb.preferenceNode.PreferenceNodeLocal</method-param>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT DISTINCT OBJECT(d) FROM PreferenceData AS d WHERE d.node = ?1 AND d.keyName = ?2</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findDataForNode</method-name>
                         <method-params>
                              <method-param>edu.umc.umcBase.bean.ejb.preferenceNode.PreferenceNodeLocal</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(d) FROM PreferenceData AS d WHERE d.node = ?1</ejb-ql>
               </query>
          </entity>

          <entity>
               <ejb-name>PreferenceNodeBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.preferenceNode.PreferenceNodeLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.preferenceNode.PreferenceNodeLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.preferenceNode.PreferenceNodeBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>PreferenceNode</abstract-schema-name>
               <cmp-field>
                    <field-name>nodeId</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>name</field-name>
               </cmp-field>
               <primkey-field>nodeId</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
               <query>
                    <query-method>
                         <method-name>findRoot</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>SELECT DISTINCT OBJECT(p) FROM PreferenceNode p WHERE p.name = '/'</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findByName</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                              <method-param>edu.umc.umcBase.bean.ejb.preferenceNode.PreferenceNodeLocal</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT DISTINCT OBJECT(p) FROM PreferenceNode AS p WHERE p.name = ?1 AND p.parentNode = ?2</ejb-ql>
               </query>
          </entity>

          <entity>
               <ejb-name>PersonBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.person.PersonLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.person.PersonLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.person.PersonBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>Person</abstract-schema-name>
               <cmp-field>
                    <field-name>gender</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>dateOfBirthDb</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>suffix</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>salutation</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>middleNameDb</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>personId</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>firstNameDb</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>lastNameDb</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>activeDb</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>hashKey</field-name>
               </cmp-field>
               <primkey-field>personId</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(p) FROM Person AS p</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findByLoginName</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(p) FROM Person AS p WHERE p.personUser.loginName = ?1</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findByLastName</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(p) FROM Person AS p WHERE p.lastNameDb LIKE ?1</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findByFirstName</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(p) FROM Person AS p WHERE p.firstNameDb LIKE ?1</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findByLastFirstName</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(p) FROM Person AS p WHERE p.lastNameDb LIKE ?1 AND p.firstNameDb LIKE ?2</ejb-ql>
               </query>
          </entity>

          <entity>
               <ejb-name>PersonUserBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.person.PersonUserLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.person.PersonUserLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.person.PersonUserBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>PersonUser</abstract-schema-name>
               <cmp-field>
                    <field-name>loginName</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>passwordHash</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>personId</field-name>
               </cmp-field>
               <primkey-field>personId</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
          </entity>

          <entity>
               <ejb-name>GroupBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.group.GroupLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.group.GroupLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.group.GroupBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>Group</abstract-schema-name>
               <cmp-field>
                    <field-name>groupId</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>name</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>description</field-name>
               </cmp-field>
               <primkey-field>groupId</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(g) FROM Group g</ejb-ql>
               </query>
               <query>
                    <query-method>
                         <method-name>findByName</method-name>
                         <method-params>
                              <method-param>java.lang.String</method-param>
                         </method-params>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(g) FROM Group AS g WHERE g.name = ?1</ejb-ql>
               </query>
          </entity>

          <entity>
               <ejb-name>CountryBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.country.CountryLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.country.CountryLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.country.CountryBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>Country</abstract-schema-name>
               <cmp-field>
                    <field-name>countryCode</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>name</field-name>
               </cmp-field>
               <primkey-field>countryCode</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(c) FROM Country AS c</ejb-ql>
               </query>
          </entity>

          <entity>
               <ejb-name>StateProvinceBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.stateProvince.StateProvinceLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.stateProvince.StateProvinceLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.stateProvince.StateProvinceBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.String</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>StateProvince</abstract-schema-name>
               <cmp-field>
                    <field-name>stateProvinceCode</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>name</field-name>
               </cmp-field>
               <primkey-field>stateProvinceCode</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params/>
                    </query-method>
                    <ejb-ql>SELECT OBJECT(sp) FROM StateProvince AS sp</ejb-ql>
               </query>
          </entity>

          <entity>
               <ejb-name>SecurityQuestionBean</ejb-name>
               <local-home>edu.umc.umcBase.bean.ejb.securityQuestion.SecurityQuestionLocalHome</local-home>
               <local>edu.umc.umcBase.bean.ejb.securityQuestion.SecurityQuestionLocal</local>
               <ejb-class>edu.umc.umcBase.bean.ejb.securityQuestion.SecurityQuestionBean</ejb-class>
               <persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
               <reentrant>false</reentrant>
               <cmp-version>2.x</cmp-version>
               <abstract-schema-name>SecurityQuestion</abstract-schema-name>
               <cmp-field>
                    <field-name>securityQuestionId</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>type</field-name>
               </cmp-field>
               <cmp-field>
                    <field-name>answer</field-name>
               </cmp-field>
               <primkey-field>securityQuestionId</primkey-field>
               <resource-ref>
                    <res-ref-name>jdo/UMCBASE</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
                    <res-sharing-scope>Shareable</res-sharing-scope>
               </resource-ref>
               <security-identity>
                    <use-caller-identity/>
               </security-identity>
          </entity>
     </enterprise-beans>
     <relationships>

          <ejb-relation>
               <ejb-relationship-role>
                    <multiplicity>One</multiplicity>
                    <relationship-role-source>
                         <ejb-name>PreferenceNodeBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>children</cmr-field-name>
                         <cmr-field-type>java.util.Collection</cmr-field-type>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <multiplicity>Many</multiplicity>
                    <relationship-role-source>
                         <ejb-name>PreferenceNodeBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>parentNode</cmr-field-name>
                    </cmr-field>
               </ejb-relationship-role>
          </ejb-relation>

          <ejb-relation>
               <ejb-relationship-role>
                    <multiplicity>One</multiplicity>
                    <relationship-role-source>
                         <ejb-name>PreferenceNodeBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>data</cmr-field-name>
                         <cmr-field-type>java.util.Collection</cmr-field-type>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <multiplicity>Many</multiplicity>
                    <cascade-delete/>
                    <relationship-role-source>
                         <ejb-name>PreferenceDataBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>node</cmr-field-name>
                    </cmr-field>
               </ejb-relationship-role>
          </ejb-relation>

          <ejb-relation>
               <ejb-relationship-role>
                    <multiplicity>One</multiplicity>
                    <relationship-role-source>
                         <ejb-name>PersonBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>personUser</cmr-field-name>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <multiplicity>One</multiplicity>
                    <cascade-delete/>
                    <relationship-role-source>
                         <ejb-name>PersonUserBean</ejb-name>
                    </relationship-role-source>
               </ejb-relationship-role>
          </ejb-relation>

          <ejb-relation>
               <ejb-relationship-role>
                    <multiplicity>Many</multiplicity>
                    <relationship-role-source>
                         <ejb-name>GroupBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>groupMembers</cmr-field-name>
                         <cmr-field-type>java.util.Collection</cmr-field-type>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <multiplicity>Many</multiplicity>
                    <relationship-role-source>
                         <ejb-name>PersonBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>groups</cmr-field-name>
                         <cmr-field-type>java.util.Collection</cmr-field-type>
                    </cmr-field>
               </ejb-relationship-role>
          </ejb-relation>

          <ejb-relation>
               <ejb-relationship-role>
                    <multiplicity>Many</multiplicity>
                    <cascade-delete/>
                    <relationship-role-source>
                         <ejb-name>StateProvinceBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>country</cmr-field-name>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <multiplicity>One</multiplicity>
                    <relationship-role-source>
                         <ejb-name>CountryBean</ejb-name>
                    </relationship-role-source>
               </ejb-relationship-role>
          </ejb-relation>

          <ejb-relation>
               <ejb-relationship-role>
                    <multiplicity>Many</multiplicity>
                    <cascade-delete/>
                    <relationship-role-source>
                         <ejb-name>SecurityQuestionBean</ejb-name>
                    </relationship-role-source>
                    <cmr-field>
                         <cmr-field-name>person</cmr-field-name>
                    </cmr-field>
               </ejb-relationship-role>
               <ejb-relationship-role>
                    <multiplicity>One</multiplicity>
                    <relationship-role-source>
                         <ejb-name>PersonBean</ejb-name>
                    </relationship-role-source>
               </ejb-relationship-role>
          </ejb-relation>
     </relationships>

     <assembly-descriptor>
          
          <container-transaction>
               <method>
                    <ejb-name>BeanKeyBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>PreferenceDataBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>PreferenceNodeBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>PersonBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>PersonUserBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>GroupBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>CountryBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>StateProvinceBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
          
          <container-transaction>
               <method>
                    <ejb-name>SecurityQuestionBean</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>Everything deploys perfectly cleanly, passes all verification tests, etc until I try to add SecurityQuestion and relate it to the person. I've tried uni-directional relationships, bi-directional relationships, everything I could think of. I've read the ejb 2.1 spec backwards and forwards trying to figure out if this was something I did or not.
Finally I decided I'm not going to find it... so hopefully someone else's eyeballs will.
Thanks.

Kodo JDO 2.5.0 beta now available

All,
Kodo JDO 2.5.0 beta 1 is now available at:
http://solarmetric.com/Software/beta/2.5.0/
Some notable new features since 2.4 include:
- Queries have received a major overhaul. Queries now support unbound
variables, Collections as parameters to generate SQL IN (...) clauses,
traversing fields of persistence-capable parameters, and more. The SQL
produced by queries is also much more efficient.
- Kodo JDO EE can now participate correctly in XA transactions.
- Kodo JDO now includes support for custom fetch groups.
- Queries and Extents can be constructed for interfaces.
- Multi-table mappings now permit different tables to have different
primary key column names.
- The data cache framework can now cache query results.
Known issues:
- The JCA resource adapter will not seamlessly work with WebLogic -- to
use it with WebLogic, it is necessary to unzip the kodo.rar and remove
empty config-param-value elements
(i.e. <config-properrty-value></config-property-value>).
- We have done only limited integration testing with our IDE plugins.
- Cached query results do not obey the timeouts configured for the classes
in the query's access path.
As usual, please discuss any issues, desires, etc. on the beta newsgroup:
news://news.solarmetric.com/solarmetric.kodo.beta
Enjoy,
-Patrick
Patrick Linskey
SolarMetric Inc.

All,
Kodo JDO 2.5.0 beta 1 is now available at:
http://solarmetric.com/Software/beta/2.5.0/
Some notable new features since 2.4 include:
- Queries have received a major overhaul. Queries now support unbound
variables, Collections as parameters to generate SQL IN (...) clauses,
traversing fields of persistence-capable parameters, and more. The SQL
produced by queries is also much more efficient.
- Kodo JDO EE can now participate correctly in XA transactions.
- Kodo JDO now includes support for custom fetch groups.
- Queries and Extents can be constructed for interfaces.
- Multi-table mappings now permit different tables to have different
primary key column names.
- The data cache framework can now cache query results.
Known issues:
- The JCA resource adapter will not seamlessly work with WebLogic -- to
use it with WebLogic, it is necessary to unzip the kodo.rar and remove
empty config-param-value elements
(i.e. <config-properrty-value></config-property-value>).
- We have done only limited integration testing with our IDE plugins.
- Cached query results do not obey the timeouts configured for the classes
in the query's access path.
As usual, please discuss any issues, desires, etc. on the beta newsgroup:
news://news.solarmetric.com/solarmetric.kodo.beta
Enjoy,
-Patrick
Patrick Linskey
SolarMetric Inc.

Windows 7: Service unknown when using load balancing group

I try to run SAP GUI 7.10 on Windows 7. I use a load balancing group to connect to the server. The direct access to one of our cluster nodes works ok, but when clicking the link to the load balancing group says "load balancing error on logon 88: connection to messaging server not possible (rc=9)" (translated from german).
What is happening here? It works good on Windows XP. Do I have to use another saplogon.ini or something?
Thanks for any help!

Is it ok to deactivate UAC in a company?
That's something your M$ group must decide.
It sounds like a good security feature but as we see here it´s a pain in the @$$ for administrators...
Well - the purpose of it is to disable the ability of malware and virusses spreading around. I consider it as a security breach if a local user is able to simply copy files to the operating systems main directory. A user working with a frontend PC should not have local administrator rights at all; all software requiring this badly designed.
If you use the SAPGUI installation server you can distribute services, saplogon.ini etc. using the installation server provided service without the need of users having to have local administration rights:
Note 512040 - Distributing "services", "saplogon.ini", and similar files.
I just think that "administrators" must learn to do work properly as designed with operating systems without just "copying files around" in system directories (and I don't exclude me in that context).
Markus

Kodo JDO 2.5.0 now available

All,
Kodo JDO 2.5.0 is now available. Thanks, everyone, for helping out
throughout the 2.5.0 public beta period. You're all great.
You can get Kodo JDO 2.5.0 at:
http://solarmetric.com/Software/Purchase/download.php
Major changes include:
- Major query modifications. Unbound variables are now supported,
Collections can be used as parameters in queries, and several SQL
inefficiencies have been addressed.
- Custom fetch group support.
- Kodo now supports incremental flushing of data to the database.
This can be useful in EJB environments when using container-managed
transactions, in order to handle any flush-related exceptions
within the bean code. It can also be useful in conjunction with
Kodo's automatic flushing capabilities to accelerate querying when
the javax.jdo.option.IgnoreCache property is set to false.
- Added JDOException subclasses for certain interesting exception
types: OptimisticLockException and ObjectNotFoundException.
- Enhancement-time metadata enhancement has been improved. This means
that you may see some errors the next time you re-enhance your
project, but that's for the best -- they were errors anyways.
- Data caching framework now caches JDOQL query results as well as
persistence-capable data. This provides dramatic acceleration for
commonly executed queries.
- The data caching framework has been reworked to separate out the
data cache capabilities from the remote event notification
capabilities. As a result, 2.5.0 data cache configuration is not
compatible with earlier data cache configuration, and custom cache
extensions will likely need some level of revision. For details,
see the release notes in the Kodo JDO Developer's Guide.
For more details, see the Kodo JDO Developer's Guide and the full release
notes, available at:
http://solarmetric.com/docs/2.5.0RC3/docs/index.html
http://solarmetric.com/docs/2.5.0RC3/docs/relnotes.html
Enjoy,
-Patrick
Patrick Linskey
SolarMetric Inc.

Minor correction:
http://solarmetric.com/docs/2.5.0RC3/docs/index.html
http://solarmetric.com/docs/2.5.0RC3/docs/relnotes.html
The 2.5.0 final docs are actually at:
http://solarmetric.com/docs/2.5.0/docs/index.html
http://solarmetric.com/docs/2.5.0/docs/relnotes.html
In article <[email protected]>, Patrick Linskey wrote:
All,
Kodo JDO 2.5.0 is now available. Thanks, everyone, for helping out
throughout the 2.5.0 public beta period. You're all great.
You can get Kodo JDO 2.5.0 at:
http://solarmetric.com/Software/Purchase/download.php
Major changes include:
- Major query modifications. Unbound variables are now supported,
Collections can be used as parameters in queries, and several SQL
inefficiencies have been addressed.
- Custom fetch group support.
- Kodo now supports incremental flushing of data to the database.
This can be useful in EJB environments when using container-managed
transactions, in order to handle any flush-related exceptions
within the bean code. It can also be useful in conjunction with
Kodo's automatic flushing capabilities to accelerate querying when
the javax.jdo.option.IgnoreCache property is set to false.
- Added JDOException subclasses for certain interesting exception
types: OptimisticLockException and ObjectNotFoundException.
- Enhancement-time metadata enhancement has been improved. This means
that you may see some errors the next time you re-enhance your
project, but that's for the best -- they were errors anyways.
- Data caching framework now caches JDOQL query results as well as
persistence-capable data. This provides dramatic acceleration for
commonly executed queries.
- The data caching framework has been reworked to separate out the
data cache capabilities from the remote event notification
capabilities. As a result, 2.5.0 data cache configuration is not
compatible with earlier data cache configuration, and custom cache
extensions will likely need some level of revision. For details,
see the release notes in the Kodo JDO Developer's Guide.
For more details, see the Kodo JDO Developer's Guide and the full release
notes, available at:
http://solarmetric.com/docs/2.5.0RC3/docs/index.html
http://solarmetric.com/docs/2.5.0RC3/docs/relnotes.html
Enjoy,
-Patrick
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

JDO help required

Hi EveryBody,
I am new to JDO and I am planning to implement JDO for building a dictionary feature for my stand alone software product .Looking out the present scenario i am quite confused whether i should continue to build my dictionary feature with JDO.Can any one clarify my following questions:
1)Would JDO be included in Sun's JDK in near future?
2)Is it a good idea to implement JDO to build a dictionary feature for a stand alone software product?If not,which are best scenarios where i could implement JDO.
3)Is there any other better way to build a dictionary feature using java?
4)Why is there not much hype about JDO?Isn't it a good technology to implement??
By
Kiran&Supriya
iTech WorKShop,
Bangalore

Hi
JDO 2.0 Expert Group is currently underway.
The J2EE expert group will decide when/if JDO is added to the platform. No decision has been made either way.
I am sure you can use JDO for your needs.
There is buzz about JDO but like any technology you have to review it to determine if it meets your specific needs.

Logon groups not visible/usable

Hi,
I'm experiencing problems with using logon groups for load-balancing connections to my NSP 7.01.
Ultimately I want to create a JCo Connection from my CE 7.1.1 to the ABAP system and CE forces me to use a load-balancing connection using a message server and a logon group. But in order to test the proper configuration of my ABAP system, I'm simplifying the scenario but just attempting to log on to the system via Sapgui with load balancing.
Here's my setup:
It's a local scenario where both Sapgui and the AS ABAP reside on the same server.
The system has SID NSP and SysNr 02.
The proper services (sapmsNSP 3602/tcp plus sapdp02, sapgw02) and hosts entries are present on the server.
Everything else works fine
The instance knows itself as tron7661_NSP_02 (I had to correct some errors in the standard installation
Profile file NSP_DVEBMGS02_TRON7661 contains: rdisp/enqname = tron7661_NSP_02, rdisp/myname = tron7661_NSP_02
In transaction SMLG, I created a logon group HUGO, assigning instance tron7661_NSP_02 with attribute "Ext. RFC enabled" = true and everything else left blank.
When I press the "Test" button, I get message "Internal error (SIMULATION:INACTIVE_SERVER)" (Message no. RZ783). I can confirm and save anyway. A green LED is displayed in the "Status" column for my logon group.
After restarting the server, I would expect the new logon group to be usable when creating a new entry in Saplogon.
In Saplogon, I choose "Create new entry", connection type "Group/Server Selection", and enter the host name of my message server TRON7661.
As a result, a single entry "tron7661 (tron7661_NSP_02, DIA UPD ENQ BTC SPO ICM)" appears in the field "Group/Server".
This entry represents not a logon group, but a single application server.
(When I try this for other SAP systems and message servers in my landscape, I always get the logon groups configured for this systems plus an entry for the application server.)
Do you have any idea what might be wrong here?
Thank you and best regards,
Thorsten
P.S.: I have found and reviewed thread /message/208613#208613 [original link is broken] but found nothing helpful in it.

Hi Raja,
Thank you very much! -- Thomas' blog solved my problem. It was in fact just a matter of running the report that makes the configured logon group usable.
Best regards,
Thorsten

BEx Analyzer :SAPLOGON_ID 'SAP BW7' not found in saplogon.ini

Hello,
The BEx Analyzer can't connect to my BW System , I got the following error:
Error Group
RFC_ERROR_PROGRAM
Message
SAPLOGON_ID 'SAP BW7' not found in saplogon.ini
The following is the copy of saplogon.ini:
=================
[Configuration]
SessManNewKey=2
[EntryKey]
Item1=
[Router]
Item1=
[Router2]
Item1=
[RouterChoice]
Item1=0
[Server]
Item1=xxx.xxx.xxx.com
[Database]
Item1=01
[System]
Item1=3
[Description]
Item1=SAPBW7IDES
[Address]
Item1=
[MSSysName]
Item1=BW7
[MSSrvName]
Item1=
[MSSrvPort]
Item1=
[SessManKey]
Item1=-1
[SncName]
Item1=
[SncChoice]
Item1=-1
[Codepage]
Item1=1100
[CodepageIndex]
Item1=5
[Origin]
Item1=USEREDIT
[LowSpeedConnection]
Item1=0
[Utf8Off]
Item1=0
[EncodingID]
Item1=DEFAULT_NON_UC
[ShortcutType]
Item1=0
[ShortcutString]
Item1=
[ShortcutTo]
Item1=
[ShortcutBy]
Item1=

I had the same issue with SAP Logon 7.30 patch 11, have looked in everything: internet, SAP Notes (1709502 for version 7.30), reinstall SAP from scracth, applied all patches available (11 so far) and nothing.
In the end I just removed the 'incorrect' entry and create again from scratch and voila, no more error.

SAPLOGON_ID not found in saplogon.ini while executing BEx

Hello All,
We have recently moved to Windows 7.
My SAP systems are working fine. However, when we try to use BEx applications, we are getting the following Error Message:
Error Group
RFC_ERROR_PROGRAM
Message
SAPLOGON_ID 'GMAM BW PRODUCTION' not found in saplogon.ini
Please advice.
Regards
Sneha

I had the same issue with SAP Logon 7.30 patch 11, have looked in everything: internet, SAP Notes (1709502 for version 7.30), reinstall SAP from scracth, applied all patches available (11 so far) and nothing.
In the end I just removed the 'incorrect' entry and create again from scratch and voila, no more error.

Check group membership and export result to file

Hi everyone,
Could you please assist? I need a script that get's a samAccountName from a text or csv file, then checks if the user belongs to Group A or Group B or Group C. If user belongs to group A, then output "Group A" and so on. Sample
output file:
JDoe Group A
JSmith Group B
KSmith Group C
DDoe Group A Group B Group C
Thanks in advance,

Hi Phathuynh,
We always recommend you can start your own script, and post the current script and the issue for a better response.
In addition, you can also refer to the cmdlet "Get-ADGroupMember" to list the members in group, and the script below is for your reference:
$output = @()
$groups = "user1","user2"
$array1 = Get-ADGroupMember Group1|select -ExpandProperty samaccountname
$array2 = Get-ADGroupMember Group2|select -ExpandProperty samaccountname
Foreach($u in $groups){
$user = Get-ADUser $u|select -ExpandProperty samaccountname
$param = @{"user" = $user
"group A" = ""
"group B" = ""}
$p = New-Object Psobject -Property $param
if ($array1 -contains $user){
$p."group A"= "YES"
if ($array2 -contains $user){
$p."group B" = "YES"
$output += $p
$output
The screenshot of result:
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

JDO 2 and EJB 3

I saw the letter posted on JavaLobby
(http://www.javalobby.org/thread.jspa?forumID=61&threadID=14630&start=0&mode=flat)
about the JDO and EJB working groups working together and think that's
great. I think a unified persistence API will be a huge win for the Java
community.
Here is my question/comment to the Solarmetric people on the JDO board:
What is the impact this has on JDO 2.0 and it's timeline? With Kodo 3.2.0
being on RC2 and having JDO 2.0 "preview" features, I had been hoping that
JDO 2.0 was going to be released soon. If JDO 2.0 is going to have to be
re-worked to work with (or be?) the EJB 3.0 persistence system, I would
assume that it will be a lengthy process and will have to push back the
release of JDO 2.0. After all, there are large differences between the way
the two specs handle persistence, and even with the new-found sence of
friendship, there is likely to be grounds for arguement.
The problem with pushing back the JDO 2.0 release, is that it increases the
amount of time that users of JDO have to choose between the 1.0 spec or
using "preview" releases of 2.0 which SEEM to follow a spec, but really
leads to vendor lock-in. If we use the JDO 2.0 features in Kodo 3.2.0, we
have to stay with Kodo since no other vendor supports their particular
version of the preview spec, and who knows if the post-EJB actual JDO 2.0
spec will differ significantly enough that Kodo will be forced to keep the
old "preview" 2.0 features simply as vendor-specific APIs. If we aren't
coding to a standard, why not just use Hibernate?
I would suggest considering how the unified persistence framework will
impact JDO, then make educated guesses as to how the JDO and EJB will come
together in order to make nessisary changes to the JDO 2.0 spec that will
help--but not significantly impact the JDO 2.0 timeline. Then, create a new
JSR for JDO 3.0 which will be able to work within the timeframe of the
EJB/J2EE spec timeframe. An added bonus would be the fact that EJB and JDO
would have the same version numbers which may help some people's confusion
(any little bit helps)
Thanks,
Nathan

Hi everybody,
I'm glad to hear some more pessimistic comments on TSS about the new plans
of SUN and the future of JDO/EJB.
My opinion about the "evolution" of persistence I have already mentioned
here:
http://theserverside.com/news/thread.tss?thread_id=28995#139908
http://theserverside.com/news/thread.tss?thread_id=28995#139903
I must admit that when KODO 3.2.0 RC2 was released I was a little bit
confused and suspicious about the new "Single String JDOQL".
The new syntax reminded me on the syntax of HQL and EJBQL.
I think that was a sign ...
If you compare the drafts of EJB 3.0 and JDO2 there were many common
concepts. But I think JDO2 has really more features which help you to
optimize the database access in the domain layer.
So the only think I wanted to know in which direction will the new JSR 220
go and will it support all the features of JDO2.
I think it can't since the new persistence will be part of J2SE and also
the new JSR is lead by the EJB lobby.
And especially I'm interested in how KODO will look like. KODO is very
good product with a plenty of features.
But how will KODO look like in 2 years. Which API's will be supported ?.
And how will an enterprise O/R mapping tool like KODO with support of
distributed cache,... fit in the new persistence API that will be part of
J2SE. Or will two version exists, one for J2SE and one for J2EE.
So think of a big project in which you have to realize a big domain layer.
Which persistence technology/API should you use in the next two years ?
I'm looking forward to the Q & A and hope that they will make everything
clearer ?
Thanks,
Matthias
Alex Roytman wrote:
Hi Patrick,
Any comments?
http://theserverside.com/news/thread.tss?thread_id=28995#139905
http://theserverside.com/news/thread.tss?thread_id=28995#139908
http://theserverside.com/news/thread.tss?thread_id=28995#139912
Thanks
Alex
"Patrick Linskey" <[email protected]> wrote in message
news:[email protected]...
Alex Roytman wrote:
If I understood Sun announcment, there will be no JDO2 - just maintenance
for JDO1 and some JDQL enhancements. So whatever JDO2 features are
implemented by vendors might be a dead-end since evolution of JDO2 is
not in plansSun's press announcements to date (or at least, as of five hours ago) were
relatively vague. According to my knowledge, JDO2 will continue pretty
much as planned, except that the JDO2 team will work on ensuring that a
few pieces of the JDO2 puzzle can be easily reused by the new team working
under the auspices of JSR220 as well.
Hopefully, Sun's FAQ will make these issues clear. Sun had intended to
release the FAQ today along with the announcement, but things got delayed,
basically for logistical reasons from what I understand.
-Patrick

SAPLOGON GROUPS JDO

Similar Messages

Maybe you are looking for