76
MP Server / Re: Inserting PPD'S using Itext
« on: February 08, 2017, 04:22:29 AM »Yes. It is possible to insert PPD's using itext :-)
Maybe to give a sample code on how to do it, would be also nice :-D since we don't know how to it!!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Maybe to give a sample code on how to do it, would be also nice :-D since we don't know how to it!!
77
MP Server / Re: issue in CMOD 9.5 exporting users end up missing groups
« on: February 08, 2017, 04:21:42 AM »
I would go with 9.5.0.7 and not 9.5.0.4, since there are lots of corrections done.
I also don't understand why you are using 9.5.0.4, if you migrated "recently" to 9.5, since 9.5.0.4 is nearly 14 month old... which is for CMOD really old...
I don't know exactly what is wrong between 9.0.0.3 and 9.5.0.4, but the error you are describing is strange, at first I would have said like Justin that you are exporting things in wrong order.
So except advising you to upgrade to 9.5.0.7 (normally the IBM Support will ask you that), and since you have already open a PMR, I have no idea what could cause such error :-/
I also don't understand why you are using 9.5.0.4, if you migrated "recently" to 9.5, since 9.5.0.4 is nearly 14 month old... which is for CMOD really old...
I don't know exactly what is wrong between 9.0.0.3 and 9.5.0.4, but the error you are describing is strange, at first I would have said like Justin that you are exporting things in wrong order.
So except advising you to upgrade to 9.5.0.7 (normally the IBM Support will ask you that), and since you have already open a PMR, I have no idea what could cause such error :-/
78
MP Server / Re: recover expired segment docs
« on: February 08, 2017, 04:16:03 AM »
Basically, in your test system you might need to do the following:
- Restore the tablespace containing the segment table DAA8. If you don't have a tablespace per table for the segments, then you will need to restore the complete database.
- Restore the table ARSSEG
So with the table ARSSEG you can discover the row where TABLE_NAME = 'DAA8', this row will need to be put exactly as is in the target ARSSEG.
The table DAA8, will need to be created and filled with the data in the target system (db2dump and db2look are your friend here...)
Concerning the data, you will need to do basically a "SELECT DISTINCT DOC_NAME FROM DAA8", to get the name of the objects in the cache that you need to extract.
Then you can add them back in the target cache FS. Be aware that you need to relink them in the retr directory.
AND in addition to that, you must ensure that the owner/permission are correct in the cache.
Then, once you have that, you can retrieve your documents, BUT BE AWARE that the next time you do a "arsmaint -c" or/and "arsmaint -d", you will loose all your documents again...
To avoid that you can simply use "ARSMAINT" with the option -g in order to tell CMOD which Application Group is allowed to expire or not. and not include this specific application group.
And also to change in the application group the retention of documentation / cache to a bigger number...
Hope that will help you a little bit to solve your problem.
Cheers,
Alessandro
- Restore the tablespace containing the segment table DAA8. If you don't have a tablespace per table for the segments, then you will need to restore the complete database.
- Restore the table ARSSEG
So with the table ARSSEG you can discover the row where TABLE_NAME = 'DAA8', this row will need to be put exactly as is in the target ARSSEG.
The table DAA8, will need to be created and filled with the data in the target system (db2dump and db2look are your friend here...)
Concerning the data, you will need to do basically a "SELECT DISTINCT DOC_NAME FROM DAA8", to get the name of the objects in the cache that you need to extract.
Then you can add them back in the target cache FS. Be aware that you need to relink them in the retr directory.
AND in addition to that, you must ensure that the owner/permission are correct in the cache.
Then, once you have that, you can retrieve your documents, BUT BE AWARE that the next time you do a "arsmaint -c" or/and "arsmaint -d", you will loose all your documents again...
To avoid that you can simply use "ARSMAINT" with the option -g in order to tell CMOD which Application Group is allowed to expire or not. and not include this specific application group.
And also to change in the application group the retention of documentation / cache to a bigger number...
Hope that will help you a little bit to solve your problem.
Cheers,
Alessandro
79
Content Navigator / Re: To set up SSO login in ICN 2.0.3.8
« on: February 01, 2017, 08:45:41 AM »
The syntax I used was the one you were using in your post of the "January 30, 2017, 06:44:07 AM". I did only a copy paste.
Now, this is a user exit is a public "hook" from CMOD. So if you want to test it, or use it, you cannot run it.
It will also never work (since there are no main method) as you have seen with the core dump output.
You need to add arsusec in the directory "${CMOD_INSTALL_DIR}/bin/exits" (check the permissions 755), and add in the ars.ini the line SRVR_FLAGS_SECURITY_EXIT=1 as you already did correctly.
Then you can restart CMOD and test it.
At my knowledge, you can only test it with a CMOD server...
When I was doing my user exit development, I was always doing that:
1) Stop CMOD Development
2) Replace the user exit
3) Start CMOD Development
4) Test what I wanted to test
5) If CMOD crashed, then I did something wrong, correct, and restart from step 1)
6) If CMOD didn't crash, then I check that everything I wanted was working, and if not, correct it, and back to step 1)
7) If everything worked as expected, then I could prepare to exit to test in the CMOD test system, that everything works as expected also there... if not, correct it, and back to step 1)
If the test phase was successfully performed, then the next step was to implement it in production, with full documentation on how to deploy it.
Hope that helps on how to develop, test these very special CMOD components.
Now, this is a user exit is a public "hook" from CMOD. So if you want to test it, or use it, you cannot run it.
It will also never work (since there are no main method) as you have seen with the core dump output.
You need to add arsusec in the directory "${CMOD_INSTALL_DIR}/bin/exits" (check the permissions 755), and add in the ars.ini the line SRVR_FLAGS_SECURITY_EXIT=1 as you already did correctly.
Then you can restart CMOD and test it.
At my knowledge, you can only test it with a CMOD server...
When I was doing my user exit development, I was always doing that:
1) Stop CMOD Development
2) Replace the user exit
3) Start CMOD Development
4) Test what I wanted to test
5) If CMOD crashed, then I did something wrong, correct, and restart from step 1)
6) If CMOD didn't crash, then I check that everything I wanted was working, and if not, correct it, and back to step 1)
7) If everything worked as expected, then I could prepare to exit to test in the CMOD test system, that everything works as expected also there... if not, correct it, and back to step 1)
If the test phase was successfully performed, then the next step was to implement it in production, with full documentation on how to deploy it.Hope that helps on how to develop, test these very special CMOD components.
80
Presentations, Newsletters, and such / Re: CMOD Updates
« on: February 01, 2017, 01:27:03 AM »
As far as I am concerned, you can use without problems the latest WAS 8.5.5.X release.
I suppose, but never had the chances to test it, that WAS 9.X will also work, BUT you must check with your IBM sales representative, if you are allowed to use WAS 9.x, since CMOD V9.5 is a bundle that contains WAS 8.5.X licenses, which might not include the license to use WAS 9.x. So you need to check that point with IBM in your specific case.
Concerning Java, you can use Java 8 with WAS 8.5.5.X, so you should be at the latest on that side.
Concerning ODWEK, since CMOD and ODWEK are since V9.5 together... as long as you install the latest CMOD, you have at the same time the latest ODWEK. (time of writing V9.5.0.7)
If you use the Content Navigator (ICN) then you will have the latest CMIS interface included in ICN installation. That will also help to keep you up-to-date.
About Version Next (v10, V9.6, V10.1, whatever the exact version will be), I have heard/read that it might come in a few month... but again, this is not sure...
Cheers,
Alessandro
I suppose, but never had the chances to test it, that WAS 9.X will also work, BUT you must check with your IBM sales representative, if you are allowed to use WAS 9.x, since CMOD V9.5 is a bundle that contains WAS 8.5.X licenses, which might not include the license to use WAS 9.x. So you need to check that point with IBM in your specific case.
Concerning Java, you can use Java 8 with WAS 8.5.5.X, so you should be at the latest on that side.
Concerning ODWEK, since CMOD and ODWEK are since V9.5 together... as long as you install the latest CMOD, you have at the same time the latest ODWEK. (time of writing V9.5.0.7)
If you use the Content Navigator (ICN) then you will have the latest CMIS interface included in ICN installation. That will also help to keep you up-to-date.
About Version Next (v10, V9.6, V10.1, whatever the exact version will be), I have heard/read that it might come in a few month... but again, this is not sure...
Cheers,
Alessandro
81
Other / Re: Content Integrator - Websphere - WEBi
« on: January 31, 2017, 07:35:17 AM »
All I can tell you is:
yes, Content Navigator is the replacement of WEBi. So my advice would be to use ICN or to migrate to ICN.
For CI (Content Integrator) I am sorry, I haven't played with it very much... so cannot help you with it, maybe someone else can answer you.
yes, Content Navigator is the replacement of WEBi. So my advice would be to use ICN or to migrate to ICN.
For CI (Content Integrator) I am sorry, I haven't played with it very much... so cannot help you with it, maybe someone else can answer you.
82
Windows Client / Re: OD 9.5.0.5 AFP Errors
« on: January 31, 2017, 07:26:31 AM »Is OD ver 9.5.0.5 compatible with Win 10 ? Client seems to be getting errors when trying to load on their test machine running Windows 10.
It should be compatible, but just to be on the safe side, try if you can reproduce the problem with the latest client 9.5.0.7.
If yes, then it would be good to open a PMR
83
General / Re: CMOD -HCP Integration
« on: January 31, 2017, 07:22:43 AM »Hello all,
Just to be sure.
If we want to use NetApp SnapLock WORM, we have to use a TSM/SSAM Layer between NetApp and CMOD?
My advice is YES.
If you use the WORM functionality of NetApp SnapLock and use CMOD with the cache only, then you will get lots of permissions problems, since CMOD does a lot of operation with the cache... and you will get some strange errors.
So NetApp SnapLock WORM should only be used with TSM/SSAM in conjunction with CMOD.
Maybe some other people here have other thought or experience, and please share them :-)
Regards,
Alessandro
84
Content Navigator / Re: ICN and CMOD on mixed platforms
« on: January 31, 2017, 07:18:58 AM »Thanks for the info and sorry this reply took so long - for some reason I don't get notified when someone replies to a post.
We have gotten it working and, ultimately, there were two main causes. One, installing to all the default paths seems to be a requirement. Second, you have to install the GSKit, which is not a documented step in the info center.
Well default path is not a requirement, but that's much more easier. I've done it many times without using default path, but it means that you must use configuration variables (ARS_INSTALL_SERVER_V95_DIR and ARS_INSTALL_ODWEK_V95_DIR) correctly. Otherwise it will NOT work.
But I agree, with default path you get less frustration.
Concerning the GSKit... I don't know where you don't see this is a requirement, and it is nowhere described. In the CMOD documentation it is written everywhere, that one of the pre-req is the GSKit installation: http://www.ibm.com/support/knowledgecenter/en/SSEPCD_9.5.0/com.ibm.ondemand.installmp.doc/dodlx097.htm and in this link you've got the point:
Code: [Select]
Installing IBM Global Security Kit on Linux
Determine whether you already have GSKit installed on your system and, if so, which version of GSKit.
If you read the README of CMOD, it is also written there: https://delivery04.dhe.ibm.com/sar/CMA/IMA/06k67/0/readme.txt Chapter 4.
85
Content Navigator / Re: To set up SSO login in ICN 2.0.3.8
« on: January 31, 2017, 07:12:03 AM »
Hello,
you cannot compile the user exit with only "gcc -o arsusec arsusec.c" that will NEVER work.
This is why you got the Makefile included that will compile it as it should be with all the correct parameters.
which corresponds to what you have found:
Otherwise, I am not sure to understand your problem... if you return: ARCCSXIT_SECURITY_RC_OKAY then you will be able to enter CMOD whatever password you enter... since CMOD will think that whatever you used, it is valid, and will shortcut the validation in CMOD.
Could you describe step after step what you are doing exactly, and what is the result you get?
you cannot compile the user exit with only "gcc -o arsusec arsusec.c" that will NEVER work.
This is why you got the Makefile included that will compile it as it should be with all the correct parameters.
which corresponds to what you have found:
Code: [Select]
gcc -o arsusec -g -O -fPIC -m64 -pthread -std=c99 -shared -I. -I../inc -DLINUX -DLINUX_INTEL -D_REENTRANT -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_FILE_OFFET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-eSECURITY arsusec.c
Otherwise, I am not sure to understand your problem... if you return: ARCCSXIT_SECURITY_RC_OKAY then you will be able to enter CMOD whatever password you enter... since CMOD will think that whatever you used, it is valid, and will shortcut the validation in CMOD.
Could you describe step after step what you are doing exactly, and what is the result you get?
86
MP Server / Re: ARSADMIN unload - specifying a date range
« on: January 26, 2017, 06:00:51 AM »
Hi,
Nope, you cannot, the only way to do it, is to gather all the loadids from your AGs between the FromDate to the ToDate, and do a loop to unload them.
How to find the loadids? from the "System Log", or "System Load".
Kind regards,
Alessandro
Nope, you cannot, the only way to do it, is to gather all the loadids from your AGs between the FromDate to the ToDate, and do a loop to unload them.
How to find the loadids? from the "System Log", or "System Load".
Kind regards,
Alessandro
87
MP Server / Re: SQL Server high availability options
« on: January 25, 2017, 05:40:44 AM »
I suppose not.
But you need to test it.
I've never used, and neither my old customers MS SQL Server... so not experience with it, except that CMOD is quite simple in its usage of a DB.
But you need to test it.
I've never used, and neither my old customers MS SQL Server... so not experience with it, except that CMOD is quite simple in its usage of a DB.
88
z/OS Server / Re: How to specify storage node using ARSLOAD
« on: January 23, 2017, 09:20:04 AM »you cannot do it directly. But using the archive definition exit you can configure the node that shall be used for the current load.
Hello Egon,
Thanks, I've learned something new :-D
Regards,
Alessandro
89
z/OS Server / Re: Load ID Format - Help
« on: January 23, 2017, 09:18:06 AM »
in the load id, the field corresponding to MinDate and MaxDate correspond in your load that you are trying to archive to the field that represent the "segment" flag in your application group (maybe a field called docdate).
And during the load "arsload" will look at the oldest date and newest date from your batch.
In your case, all documents have the date "20161007000000", so it is normal that MinDate = MaxDate = "20161007000000"
If you have a mix of dates, let say "20161001000000", "20161007000000", "20161011000000", the your load ID would look like :
5559-11-0-10381FAA-20161001000000-20161011000000-5562
since MinDate=20161001000000 and MaxDate = 20161011000000.
Regards,
Alessandro
And during the load "arsload" will look at the oldest date and newest date from your batch.
In your case, all documents have the date "20161007000000", so it is normal that MinDate = MaxDate = "20161007000000"
If you have a mix of dates, let say "20161001000000", "20161007000000", "20161011000000", the your load ID would look like :
5559-11-0-10381FAA-20161001000000-20161011000000-5562
since MinDate=20161001000000 and MaxDate = 20161011000000.
Regards,
Alessandro
90
MP Server / Re: ARSMAINT slowness
« on: January 23, 2017, 09:14:06 AM »
it depends on which argument you are using in arsmaint, AND how you configure your application group (mainly the expiration type).
If you have expiration type= document... then you will experience a HUGE slowliness of arsmaint...
so if you can give us more information on the setup that you have, it will help us to understand clearly what other thing can influence the speed of arsmaint, in addition to what Justin and teeraw just said.
Regards,
Alessandro
If you have expiration type= document... then you will experience a HUGE slowliness of arsmaint...
so if you can give us more information on the setup that you have, it will help us to understand clearly what other thing can influence the speed of arsmaint, in addition to what Justin and teeraw just said.
Regards,
Alessandro