InfoButtonVM

[jrivasg]

I solved the problem with the port, the vagrant VM is running, but I`cant access, username and password required, could you please provide it?

Thanks.

[gdelfiol]

The latest VM should have fixed this problem. You shouldn’t need to enter a user name and password to connect to the VM. Have you downloaded the latest one? Please let us know if the problem persists. Note that you don’t need to login to the VM to use OpenInfobutton. The latest installation instructions clarify that. From: Rivas <[email protected]> Reply-To: VHAINNOVATIONS/InfoButtons <[email protected]> Date: Monday, May 22, 2017 at 3:45 AM To: VHAINNOVATIONS/InfoButtons <[email protected]> Cc: Subscribed <[email protected]> Subject: [VHAINNOVATIONS/InfoButtons] InfoButtonVM (#14) I solved the problem with the port, the vagrant VM is running, but I`cant access, username and password required, could you please provide it? [mage]<https://cloud.githubusercontent.com/assets/5821130/26302057/52049270-3ee3-11e7-94a0-86188ccf7ec2.png> Thanks. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#14>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD6r2W9RCEqBPd8xTparueZWwMbY18DFks5r8VkdgaJpZM4NiHoq>.

[aniskand]

Hi, rather than using the VirtualBox console to try and login to the VM, just open up a terminal shell and change to the directory with the VM and Vagrantfile. The run the command 'vagrant ssh', and it should log you right in. For the method you're attempting, you can try the password 'vagrant'.

[wahmedswl]

@aniskand @gdelfiol machine access is needed in case need to review the deployed components. I have build the InfoButton according to the build Guide, and infobutton-service.war is also deployed, but i don't see anywhere i can give DB Credentials in that. When exploring the URL given in the VM Guide, the local deployed site give up following error

http://localhost:8080/infobutton-service/infoRequest?representedOrganization.id.root=1.3.6.1.4.1.3768&patientPerson.administrativeGenderCode.c=F&age.v.v=47&age.v.u=a&taskContext.c.c=PROBLISTREV&mainSearchCriteria.v.c=44054006&mainSearchCriteria.v.cs=2.16.840.1.113883.6.96&mainSearchCriteria.v.dn=Diabetes%20mellitus%20type%202&performer=PROV&informationRecipient=PROV

could not execute statement

[wahmedswl]

@aniskand @gdelfiol it might be that missing something but, any help would be appreciated as VM size is quiet large and what about the upgrades? Every upgrade will need the full VM download again so wanted to chose a route where upgrade is also simple.

I have also created ticket for DOCKER version #15, DOCKER can also streamline the build and deploy process.

Thanks