CHS is in 2007 opgericht met als doel het ondersteunen van zorginstellingen en zorgverzekeraars bij het bereiken van hun kwaliteits-, efficiency- en veranderdoelstellingen. Dit wordt gerealiseerd door ze te voorzien van bruikbare stuurinformatie en praktijkgerichte ICT-oplossingen. CHS is specialist rondom volledig geautomatiseerde (en complexe) DBC berekeningen en validaties. Zorgverzekeraars hebben een formele verplichting om controle uit te voeren op alle gedeclareerde zorg. CHS verwerkt jaarlijks meer dan 80% van alle DBC controles in heel Nederland. Naast analyseproducten (waar onder DubDecTM en Cope-controle®) op het gebied van medisch specialistische zorg zijn ook producten ontwikkeld op het gebied van de GGZ en farmacie. Analyseproducten op andere gebieden binnen de zorg, waaronder tandheelkunde, staan in de planning.

Door deze samenwerking bieden CHS en Yenlo een beveiligde, betrouwbare en stabiele omgeving voor zorginstellingen en zorgverzekeraars rondom ondermeer DBC berekeningen en validaties.

De heer M. Persoon, Adjunct Directeur CHS: “Toen ik op zoek ging naar een partij die de door ons ontwikkelde software betrouwbaar en professioneel kon ondersteunen, was de keuze voor mij gauw gemaakt. Yenlo heeft een uitstekende staat van dienst op de componenten die wij in onze software architectuur gebruiken. Heel specifiek hun kennis op het gebied van Glassfish en openESB, zorgt ervoor dat wij op een veilige en betrouwbare wijze onze dienstverlening kunnen blijven aanbieden aan de zorginstellingen en zorgverzekeraars.”

Klik hier voor meer informatie rondom de beheerservice van Yenlo.

Deel deze informatie op LinkedIN

De Pretium Groep en Yenlo, specialist op software ontwikkeling (specifiek in het SOA domein met behulp van Oracle en Java technologie) en op het gebied van 7*24 beheer van Java (Glassfish) en Oracle gerelateerde informatiesystemen, hebben een overeenkomst gesloten voor het volledige beheer en hosting van alle Pretium Groep informatiesystemen binnen de Yenlo beheerservice. Voor de komende jaren zal Yenlo voor de Pretium Groep alle Java en Oracle (Glassfish Applicatieserver en Enterprise Service Bus, Oracle databases en Oracle Fusion Middleware platformen) gerelateerde zaken actief beheren in haar NEN7510 / ISO9000 gecertificeerde datacentrum. De beheerservice betreft zowel de hardware, de hosting als ook het 7*24 technisch en functioneel bewaken van de gehele applicatie- en database omgeving(en).

Klik hier voor meer informatie rondom de beheerservice van Yenlo.

Deel deze informatie op LinkedIN

Please click here for more information about these screencasts.

Log in on the admin console, click on domain > Administrator Password, and put in a new password. Click on save. The password is immediatly changes. This does the same as “asadmin update-file-user –authrealmname admin-realm admin” commando, except the update-file-user expects that there is an other user. Default there is only the admin user. Both actions change the keyfile in $GLASSFISH_HOME/domains/domain1/config. I perfer the change password through the console, since I don’t have a second admin user.

next we have to change the .asadminpassword file in the user home. Start asadmin and enter the following commands:

[glassfish@YSGF01 ~]$ asadmin
Use "exit" to exit and "help" for online help.
asadmin> change-admin-password
Please enter the old admin password> [new password]
Please enter the new admin password> [new password]
Please enter the new admin password again> [new password]
Updated .asadminpass file with new password.
Command change-admin-password executed successfully.

Next we have to make sure the the node-agent are aware of the changed password.

asadmin> stop-node-agent nadev01-yenlo
Command stop-node-agent executed successfully.
asadmin> start-node-agent --startinstances=false nadev01-yenlo
Please enter the admin user name>admin
Please enter the admin password>
Redirecting output to /u00/oracle/product/2.2/glassfishesb/glassfish/nodeagents/nadev01-yenlo/agent/logs/server.log
Redirecting application output to /u00/oracle/product/2.2/glassfishesb/glassfish/nodeagents/nadev01-yenlo/agent/logs/server.log
Command start-node-agent executed successfully.
asadmin> list-instances
indev01-yenlo not running
indev02-yenlo running
Command list-instances executed successfully.
asadmin> start-instance indev01-yenlo
Command start-instance executed successfully.

Log in on every node of the cluster, stop the node agent, then start it again without starting the instance on it (–startinstances=false). Then start the instances on it. On this way you can change your password without any down time.

Select “File system” and click “Next >”. Locate the WSDL, and accept all default settings by clicking through the whole wizzard. The result:

Implementation

Next, create a new Collaboration Definition (JCD) inside the project. We want to initialize the JCD with a Queue message. So the input will be a JMS operation. For the output parameter look up the newly imported WSDL definition.

After creating the JCD, open it and look for the WSDL definition inside the mapping editor. Look for the PortType node. Rightclick the node :

Next an object browser window opens :

If the service needs input, we first have to fill all input objects, and after that call the invoke() like this (inside the code view):

Configuration

Create an environment inside the services tab of Netbeans with a logical host for catching message queue’s, and pointing to the right integration server. For calling the webservice we create an extra ‘SOAP / HTTP Webservice external system’.

Rightclick on the external system icon for the service, and click the ‘configuration’ menu:

It is also possible to store all above configuration data inside LDAP, and fill ldap://…. references inside the external engine configuration. After finishing the environment, create a connectivity map, drag and drop the JCD inside. Generate the mappings. Create a deployment profile and build the system.

The LDAP config menu

Now configure the connection settings.

Now ESB knows where to find LDAP.

OpenESB is the umbrella project that takes the core runtime in Glassfish, the design time tooling in Netbeans, and many of the JBI components from OpenJBI and packages them into a single installer which you’re able to download.

First let’s map out the differences between OpenESB and CAPS 6

Glassfish v2 Enterprise AS has extra admin monitoring abilities plus user persistance storage capabilities for high availability.

In CAPS 5 applications were deployed to an integration server (IS). Connectivity information was embedded in repository-based EAR files. There was no connectivity information in the IS. Any change in configuration required a regeneration of the EAR file. A workaround was to use LDAP. However LDAP connectivity information is stored in the EAR file, which means that when the LDAP server is changed, the EAR file must be regenerated.

In CAPS 6 applications are deployed on Glassfish. CAPS 6 includes a new concept called Environment Objects, which represents connection information to an external system. This info is stored in the AS, where it is serialized in the domain.xml. When the EAR is deployed on the AS, environment configuration is overriden with the info stored inside the Environment Objects. You are able to use environment objects in combination with environment variables stored inside LDAP. (OpenDS for instance)

Admin password:

$ asadmin change-admin-password
Please enter the old admin password>
Please enter the new admin password>
Please enter the new admin password again>
Updated .asadminpass file with new password.
Command change-admin-password executed successfully.

Master Password:

First stop de Domain Administration Server

$ asadmin stop-domain domain1
$ asadmin change-master-password domain1
Please enter the new master password>
Please enter the new master password again>
Master password changed for domain domain1

If you are using a password file, don’t forget to change your passwords there as well.

Update:

Unfortunately  The above steps are not enough when you are running a mutli node or enterprise glassfish environment. When you change the admin password, all the nodes have to be aware of the new password.
For more information regarding the password change in a multi node or enterprise environment see: http://wiki.glassfish.java.net/attach/GlassFishAdministrationPages/admincreds.html#changing

The way to assign a default JDK is to go to the Netbeans install location {root}/netbeans/etc and edit the file netbeans.conf.

# (see http://wiki.netbeans.org/wiki/view/FaqGCPauses)

# Default location of JDK, can be overridden by using –jdkhome :
netbeans_jdkhome=”D:\jdk1.6.0_10″

# Additional module clusters, using ${path.separator} (‘;’ on Windows or ‘:’ on Unix):
#netbeans_extraclusters=”/absolute/path/to/cluster1:/absolute/path/to/cluster2″
netbeans_default_userdir=d:/JavaCAPS62/.netbeans/caps
#netbeans_jdkhome=D:/jdk1.6.0_20

I’ve commented out the first bold line and filled the reference to the new default location, and commented the old default location. Restarting Netbeans will run the new settings.