Messages

16

OD/WEK & JAVA API / Re: ODWek REST - Search with SQL - Segment start and stop date

« on: March 08, 2023, 12:23:15 PM »

Thanks Russel,

Do you mind also explain how we can use the segment startdate and stopdate?
I dont get how I should get that value to make the search more efficient.

17

OD/WEK & JAVA API / ODWek REST - Search with SQL - Segment start and stop date

« on: March 08, 2023, 01:28:38 AM »

Hi,

In the documentation https://cmod.wiki/dox/RESTapiDoc/CMOD_10_5_REST_API_Documentation.html chapter 3.5.2. Search with SQL it says

When using search with SQL, it is imperative you include a segment start and stop date when available. The format of the start/stop dates is %Y-%m-%d. Failure to include a segment feild will result in a search across all application group data tables severly impacting system performance.

My question is, how do I know what segment start and stop date to use?

Failure to include a segment feild will result in a search across all application group data tables severly impacting system performance.

Hence that quote, it seems like I should be able to know what segment start and stop date I can use for a query.

In this sample request, the startdate and stopdate spans over 27 years. 27 years of records seems a bit odd to search through if the point of segment startdate and stopdate is to narrow the search down to increase performance.

Code: [Select]

POST /cmod-rest/v1/hits/ HTTP/1.1
usi-date: 2020-02-25T00:31:30Z
Authorization: CMODSharedKey externpool1-P0mFoCU5H83lN9uQcRUA:5au9U9epefygVH22mKfR8yGkS+XiA0D8CDmcOvZrt58=
Content-Type: application/json; charset=UTF-8
Host: localhost
Content-Length: 191

{
  "startdate" : "1993-01-01",
  "stopdate" : "2020-02-11",
  "query" : "where name like 'VILL%'",
  "folder" : "Baxter Bay CC Statements",
  "applicationgroup" : "Baxter Bay Credit"
}

18

OD/WEK & JAVA API / Re: Can we adjust the ODWek REST max hits

« on: March 02, 2023, 01:58:16 AM »

Guess I found the solution,

In the rest configuration template file(cmod_installation\www\rest\default.tmpl), you have a property called 'maxHits'.
I have adjusted this to maxHits=1000

Created a new connection pool and access keys
Restarted the cmod-rest application

Now I retrieve up to 1000 hits.

19

OD/WEK & JAVA API / Re: Can we adjust the ODWek REST max hits

« on: March 01, 2023, 04:53:44 AM »

ups noticed I put this under wrong topic..
Maybe some moderator can move this topic to the correct topic.

20

OD/WEK & JAVA API / Can we adjust the ODWek REST max hits

« on: March 01, 2023, 04:11:53 AM »

Hi,

Through ODWek Java Api - ODFolder.setMaxHits(...) we can adjust the max hits.
With ODWek Rest, is it possible to increase the max hits through ODWek Rest ? or is the ODWek Rest limited to max 200 hits?

Thanks in advance

21

OD/WEK & JAVA API / Re: ODWEK Tomcat Issue

« on: March 01, 2023, 02:12:07 AM »

I'd just like to say this solution helped a ton, thanks Alessandro. Was missing to terminate the initialization one or two places so ended up in memory leak.
For later troubleshooting, was using tools like jconsole, visualvm, jprofiler to see that our application was performing Garbage Collection - it was, but still saw memory was being allocated. Appeared to be CMOD native application allocating the memory

If you do an ODServer.initialize(...), then you MUST do a ODServer.terminate(), otherwise you'll have a leak of memory because the native libraries that are used behind won't be freed. And since ODWEK use JNI, if you don't have enough memory for the native libraries... then it can simply crash.

22

OD/WEK & JAVA API / Re: Odwek - Afp2Pdf - AFP Files - Memory leack

« on: February 23, 2023, 02:05:12 PM »

Hi,

I am curious if you solved your memory leak issue and how you did it?
We are also in the same situation right now, we have an web application which serves web services which handles the afp2pdf.

I have used plenty of tools to monitor the JVM of our application, it seems to stay no more than 2-4GB.
The Java prosess will increase to endless of memory untill it crash because of out of memory on server.

Our system:

• Java 11
• ODWek 10.5.0.5
• OnDemand 10.5.0.5

23

MP Server / Re: AFP2PDF Plus Transform for CMOD 10.5 License type

« on: November 15, 2022, 06:44:22 AM »

Have you had a look at StreamEDS? owned by TargetStream.

We are developing our own ICN plugin for AFP2PDF with use of StreamEDS.

24

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 15, 2022, 06:41:39 AM »

Upgrading from CMOD 10.1.0.5 to 10.1.0.11 seems to have fixed the issue where group members where not added to the group
Instead of existing group members being removed from the group, they now are left in the group.

Code: [Select]

2022-11-15 14:36:07.340313: ARS1225I Group Member Exists: Name >Group456<  Userid >User123<
Also group members are being added to groups

Code: [Select]

2022-11-15 14:36:07.340818: ARS1222I Group Member Add Preview: Name >Group456<  Userid >User789<
PS: I noticed, you need to run ARSLSYNC twice if the group you are synchronizing does not already exist in OD.
First run of ARSLSYNC will create the group
Second run of ARSLSYNC will add users to that group.

Thanks for you help rjrussel!

25

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 10, 2022, 07:43:06 AM »

In the tracelog, I notide that the garbage character is always on character number 206

Is there a limit for how long the Distinguished Name can be?
It looks like the query is taking the value from a field u_dn

26

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 09, 2022, 02:28:38 PM »

Now I deleted User123 from OnDemand.
Started the synchronization preview.

Code: [Select]

arslsync -tv
2022-11-09 22:24:49.106304: ARS1212I User Add Preview: Userid >User123<

No records of Group456

27

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 09, 2022, 01:58:30 PM »

The users that are added to the group must exist exit in OnDemand as part of either the current sync or a previous sync.

User exist in OnDemand, user were manually created for some reason.

If you run your userFilter query it should contain the users that will also be synced to groups. If the users are NOT part of your userFilter, they will not only not end up in CMOD and not end up in your group either.

userFilter query contain the user.

Example
As an example lets say we have User123 that already exist in OnDemand - manually created in OnDemand.
User123 also exist in AD.
Then we have a group called Group456, this group exist in both OnDemand and AD.
User123 is a member of Group456 in both OnDemand and AD before running synchronization.

arslsync -tv says

Code: [Select]

2022-11-08 12:59:24.713383: ARS1215I User Exists: Userid >User123<
2022-11-08 12:59:24.762684: ARS1224I Group Member Delete Preview: Name >Group456<  Userid >User123<

28

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 09, 2022, 06:11:40 AM »

unfortunately changing locale to UTF-8 had no change.

Question: Synchronization of group membership, does that only work when the user does not exist in OD before running synchronization? or should the synchronization also add existing OD users to member of a group?

29

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 08, 2022, 12:28:31 PM »

I see the same garbage character for multiple search filters in the trace log.
But it differs a bit..

FYI: I'm reading this as UTF-8.. but I have not ran the arslsync with UTF-8 yet, cant install the locale today.

Search 1

Code: [Select]

(&(objectClass=user)(memberOf:1.2.840.113556.1.4.1941:=CN=...,OU=...,DC))
Search 2

Code: [Select]

(&(objectClass=user)(memberOf:1.2.840.113556.1.4.1941:=CN=...,OU=...,
Search 3

Code: [Select]

(&(objectClass=user)(memberOf:1.2.840.113556.1.4.1941:=CN=...,OU=...,DC=test
Ye well as you say, it could look like log bug

30

MP Server / Re: Group membership not adding user during synchronization with LDAP

« on: November 08, 2022, 12:12:17 PM »

unfortunately not