Tricentis Tosca 11.0 - How to install HOST Engine - automation

I have a Mainframe/HOST Application to automate using Tosca 11.0, I am unable to scan/steer elements in mainframe screen.
Solution found in Tricentis Support -
The Tosca Host Engine is installed by default as part of a complete Tricentis Tosca installation.
All information regarding software versions and hardware requirements for the engine can be found in the "System Requirements for Tricentis Tosca".
The file PCSHLL32.DLL needs to exist in the system and the operating system needs to know the path to this file (with the system variable PATH).
The 3270 terminal emulation needs to be initialized correctly, so that the connection to the HOST system to be tested can be established. Additional information is available from your system administrator.
I couldn't locate PCSHLL32.DLL in my PC.
Has anyone faced same issue? can someone help where to get PCSHLL32.DLL and get HOST engine working.

I had this problem for a while. I kept trying to figure out how to install the Host module because I couldn't find that PCSHLL32.DLL on my system...
Turns out HOST was already there... I just had to get Tosca Commander configured to find my terminal app (I'm using QWS3720 from Jolly Giant).
Try this - Go into Tosca Settings, and go to Settings > Special Engines > HostEngine> Emulation Environment and check the following settings:
1) Emulation Title: this should be the window title of your terminal emulator. * works as a wildcard. Since QWS3270 changes it's window name to match it's session, we just use * in this field.
2) Emulation Type: try to find your terminal emulator's maker listed here... Mine is set to Jolly Giant.
3) Session ID: this is the important one. This is the HLLAPI ID of the term window, basically the handle that automation needs to know to "see into" the terminal window. it seems to typically be set to "A" (same as with QuickTest Pro/UFT).
Once these settings are correct, then TRY to scan your terminal window. Launch your terminal emulator first, CONNECT with it (to start up the HLLAPI), then run Tosca's scanner - just don't expect it to scan like web pages, it will use the older scanner. Select Scan Application > Other... and it will start the older "Tosca Wizard". Click Scan, then point to your Terminal emulator. If you see the little box showing "Recognized Wizard >HOSTEngine
Good Luck!

Related

Can I use the Remote Platform option in Netbeans from Windows 10?

I am trying to use my computer with windows 10 installed so that I can build and compile jar files but test them remotely on my raspberry pi4 down the hall. This method worked fine when I was using a linux (Ubuntu) laptop, but unfortunately...the laptop broke, and now I'm installing linux on another computer...and in the meantime, I would like to continue working. I have Apache Netbeans 12.3, java version 16, and here are the specifics of what is happening: I can go into manage platforms, I can set up a remote platform, and can test it...and the connection tests out successfully. However, when I go to File->ProjectProperties and select Categories->Run, in the drop-down box where you can usually select the platforms you have established....there are no options--it just offers Project Platform. Maybe it's a windows thing? A priviledge thing? I can't find the answer...thanks in advance.
This is the screen where the problem exists. The arrow points towards the drop down menu that won't drop down and acts like no other Platform has been defined.
By downgrading the JDK to JDK11, I was able to select newly existing Remote Platforms in Netbeans in the File->ProjectProperties window, under the Run category, as detailed in the picture above.

VirtualBox won't run win10: Failed to open a session for the virtual machine w10. Result Code: NS_ERROR_FAILURE (0x80004005)

Ok so I want to get a virtual machine with Windows so I can download applications only on Windows (Not on OSX (I'm on Big Sur 11.2.3 by the way)), so I downloaded VirtualBox, then downloaded the Windows thing which apparently I have to (as seen in one of the pics) (you can tell I have hardly any experience with vms), then I created a new vm in the VirtualBox app, and left all the default settings except for the type of hard drive (which is also in one of the pictures), then I clicked Start and it asked me to add a 'virtual optical disk file', so I clicked on the folder button then clicked add in the top left, and it gave me this error code:
Failed to open a session for the virtual machine w10.
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
as you can also see in one of the pictures below. Also, when I leave the screen for a couple of minutes right before I click on the previously mentioned add button, this appears:
but I tried just leaving it to load, and nothing happened. I have tried uninstalling using the uninstall tool twice, rebooting my Mac, etc etc, and yes I have allowed everything I need to in the Security settings. I'm not installing it on a moderator account, but the Windows 10 virtual optical disk file is in Documents which the account I'm on has read and write access to, and obviously the actual VM is in applications.
Thanks so much!
Here's the previously mentioned image of the one changed setting:
And here's the pic of the Win10 64-bit I had to install:
thanks everyone!
VirtualBox Version: 6.1.22 r144080 (Qt5.6.3)
Host Operating System: MacOS BigSur
I came across exactly same issue, where clicking on add to choose image was crashing the dialog. This issue persists in the latest version of Virtual Box for Mac.
I could figure out couple of ways to avoid clicking on Add button to choose image.
First Option:
Steps:
Click on Settings to open settings window for your VM.
Choose Storage
Select Empty disc and choose Disk image by clicking small disc icon in the Attributes section. Please follow the image to have visual instructions.
Second Option:
Steps:
Click on VM's Normal start
Once you get the option to choose image, simply cancel the dialog.
Now click on the small disc icon in the bottom of VM's dialog to choose the image.
Hope this helps. Feel free to comment if you find this post useful.
I had the same message because of permissions at directories where the hard disks were stored in. So, just execute VirtualBox 'As Administrator' and all run well.
I was getting the same error on Ubuntu 22.04 machine while trying to start an existing or a new VM-
Failed to open a session for the virtual machine NuacareRocky.
The VM session was aborted.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {c0447716-ff5a-4795-b57a-ecd5fffa18a4}
I tried a few things as suggested on youtube, but nothing worked. finally, I just upgraded the extension and it worked.

Blue Prism - Not able to spy elements - Browser Firefox

I have an issue with spy Browser mode in Firefox.
I have designed a new RPA process on Dev machine where I have spy in Browser mode (in firefox) web page.
On my Dev machine the Browser mode is working good and the process runs very good.
The issue is on production machine where the modeler don't see the elements which have been spied on dev machine.
Actions so far done.
We have set all settings regarding Firefox to the same like on dev machine using the BP guide,
We have installed the same Firefox extension on prod like on dev machine.
We have set the same internet options.
Non of the actions have helped us to be able to spy elements in Firefox on prod machine.
My questions to the experts community:)
What else could have impact on the BP - Browser mode which is stopping BP to see elements?
What virtual machine settings need to be set/or what to check?
We have BP Version 6:
Application Manager 6.4.2.10610
.Net Framework 4.7
Firefox version 72.0.2
Blue Prism Browser Extension version 6.4.2.10610vycoxormiz (updated 30. Jan. 2020)
Thank you for your help!
I found the solution.
During investigation I came on this link
[https://superuser.com/questions/719875/google-chrome-always-says-google-chrome-was-not-shut-down-properly][1]
In the location "%UserProfile%\AppData\Local\Google\Chrome\User Data\Default\Preferences
I have changed the "exit_type": "normal" to "exit_type": "standard" and immediate the
Browser mode on production machine was working and we could run the process.
It seems that the chrome when it wasn't shut down properly has impact on Blue Prism.
Adding update.
I have noticed that each time Chrome opens it changes in the Preferences file the status to Normal.
I have fixed the issue in that way, that I have added additional logic to my solution:
1. I have copied the Preferences file to a different location and changed in the file the status to Standard.
2. I have added additional logic to my process where bot copy the file from the new location and replace the file in the Chrome location each time he runs.
Hope this will help others with similar issue.
Regards!

"Not Enough Memory available" exception while running windows phone 8.1 emulator

"Windows Phone Emulator is unable to verify that the virtual machine is running :
Not Enough memory is available in the system to start an emulator that uses 2048 MB of startup RAM"
I am a beginner to Windows Phone App developement.I was trying to Deploy a Hub App template and while executing the code for the emulator I got the above error message! Please help me out.
Probably its because your machine does not hove enough RAM? acording to this article there are some workarounds.
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
To work around this problem in a system that is running many programs that are using lots of memory, try to close those programs and then restart the emulator.
If the emulator still does not start, you can disable the Hyper-V runtime memory monitoring functionality by adding a MemoryReserve registry. To do this, follow these steps:
Start Registry Editor.
Locate the following registry subkey:
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization
Right-click the Virtualization folder, point to New, and then click DWORD Value..
Type MemoryReserve, and then press Enter.
Double-click MemoryReserve, enter 2048 in the Value data box, select the Decimal option, and then click OK.
Close Registry Editor.
In systems that experience this problem and that have fewer than 8 GB of RAM installed, a MemoryReserve value of 2048 (2 GB) is recommended. A value of zero (0) causes this registry setting to be ignored.
Note You must restart the computer for this registry setting to take effect.
If this doesnt help give some more info about your machine haracteristics.
Also you can check this article

Winpe 4 drivers not loading

I need to inject custom drivers to wim file offline.
I'm using standard scenario described on MSDN http://technet.microsoft.com/en-us/library/hh825206.aspx: mount, add-components (WMI, .NET4), add-drivers (signed, work correctly on windows 7 & 2012, x86/64), unmount, makewinpemedia.
However, when I booting from iso (on VMWare), drivers not loading.
Any suggestions?
Thanks.
The most important thing while developing Win PE driver is to follow the architecture(using 32 bit on 64 bit Win PE can cause failures)
Follow the steps:-
Take the 'Custom Windows PE' rescue CD option in the rescue CD wizard.
If you haven't previously installed the Windows Automated Installation Kit (WAIK), then this will need to be downloaded and installed. This is a big (1.7GB) download, so please be patient. The WAIK download dialog will be shown. Just click 'Continue' and be patient while the integration completes.
Once the integration is finished cancel the rescue media wizard.
Download and run 'inject.exe' from here:
http://updates.macrium.com/reflect/utilities/inject.exe
This will automatically inject the drivers into the windows image file (WIM) and will take a few minutes.
Once completed, take the rescue media build wizard again, select the 'Custom Windows PE' and click through to the final page.
Click the 'Rebuild' button to re-integrate the WAIK. This will not need to download and install the WAIK again, so will be much quicker.
Once completed, if you now burn the rescue CD the drivers will be integrated and you should have no problems booting with the CD and recognizing your local RAID volumes.
Have you gone through Windows Automated Installation Kit (AIK) you can have a look at the following link it may help you.
http://kb.acronis.com/content/24254
Windows PE always uses the same basic VESA mode video driver regardless of the card in use.
Please check the link below.
http://technet.microsoft.com/en-us/magazine/cc160920.aspx
This particular link for creation of the ISO with Windows Automated Installation Kit (AIK) can also help you get going.
http://www.bootfromcd.com/compare-solutions/windows-pe-boot-disk-review/
i did spent some time with Win PE,there is a image below are you getting the same message while booting with VM?
There are some additional steps given in the follwing link you can check if it works this way
https://users.emulab.net/trac/emulab/wiki/WindowsByWinpe
another helpful link
http://desktopreality.com/windows-7-deployment-the-easy-way/
Updated the information check if it helps.
Thanks