I have set up a MQ Server 7.1 on my local machine.
I have set up a Queue Manager : QM_APPLE
I am trying to run the sample .Net Code from the MQ Examples to PUT a message on the Queue : Q1.
When I try to instantiate the MQQueueManager, I get the above error.
I have tried following the Authorization steps in http://www-01.ibm.com/support/docview.wss?uid=swg21166937 but I am still getting the error. Obviously I am not specifying the parameters correctly here. Can anyone help?
alladm is administrative privileges. It doesn't work for API privileges. Try with +allmqi.
But that's generally not advisable. Try to drill down to specific authorization (like put, get, setid, setall) when you start developing a real application.
http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/index.jsp?topic=%2Fcom.ibm.mq.ref.adm.doc%2Fq083500_.htm
Related
Hi everyone one,
On my project, we are developing a spring boot application which is using JCo3.
It works fine for calling SAP from JAVA.
Now we are enhancing this application and we want to create a Jco server.
It will have to communicate with 2 different SAP system.
Each system have its own message server.
We customize each message server with several logon group according to our needs.
So we have created 2 classes to build up 2 Jco server one per system.
For server class, we hae base our development upon this blog:
https://blogs.sap.com/2017/08/25/sap-jco-server-example/
So we use a ServerDataProvider to use the parameters below
jco.server.connection_count=2
jco.server.progid=JCO_SERVER_SAP
jco.server.repository_map=SID(020)=S4
jco.server.mshost=myslanaddress.com
j
co.server.msserv=3601
jco.server.system_id=SID
We have 2 files to specify these parameters one per SAP system
The other system wil use a different progid.
When starting our application, everything goes well for the first bean instanciation.
As soon we arrived on the other, when trying to create the new Jco server
with for instance new progid JCO_SERVER_SAP and with new message server info)
with (server = JCoServerFactory.getServer(properties.getProperty(ServerDataProvider.JCO_PROGID));
The Constructor threw this exception; nested exception is com.sap.conn.jco.JCoRuntimeException: (136) JCO_ERROR_ILLEGAL_STATE: JCoServer JCO_SERVER_SAP is currently running. Current server state is STARTED
It is strange because in debug the progId is JCO_SERVER_CAR and not JCO_SERVER_SAP..
I foun this message (https://answers.sap.com/questions/12862862/how-to-implement-a-jco3-server-with-multiple-diffe.html) but I don’t know how to build such solution.
Do you have any clue ?
Thanks in advance for any help.
I tried to create and use
jco.server.repository_map
but it do not work.
Application: http://localhost:1080/webTours/home.html [I intend to use it for Jmeter testing]
Below error is displayed when I am trying to click on "sign up now" link. Kindly help to fix it. Pls note, I have strawberry-perl-5.30.0.1-64bit.msi also installed and path is set to the environment.
Internal Server Error The server encountered an internal error or
misconfiguration and was unable to complete your request.
Please contact the server administrator, admin#localhost and inform
them of the time the error occurred, and anything you might have done
that may have caused the error.
More information about this error may be available in the server error
log.
Thanks.
Probably, you need to do the correlation for the dynamic parameters like sessionID etc.
Record two scripts using tools like fiddler or LR or any other sniffing tool and compare two scripts to find out dynamic variables required. Then correlate them. For correlation, identify the first occurrence of the variable in the response then extract them using post processor and pass them further below/to all the request that requires it.
Hope this helps.
It appears that your Web Tours Sample Application installation is broken, looking into MICRO FOCUS SUPPORTED stanza in the application details you should contact Micro Focus Support or ask the question in Micro Focus Community Forums.
In the meantime you can use http://blazedemo.com/ page and Getting Started with JMeter - A Basic Tutorial as the alternative test application for your JMeter training
If you are not getting internal server error while sign up (or) accessing administration link then follow the below,
a. close the server from the cmd
b. In the Web Tours 1.0 parent folder, find the file .msi file: strawberry-perl-5.10.1.0
c. Double click on strawberry-perl-5.10.1.0 msi file to install
d. Once it is installed, Now re-start the server (Double click on StartServer.bat file) under WebTours sub-folder
e. Now, Go to link http://localhost:1080/webtours/home.html
f. Click on Sign up (or) administration link
g. Hope you are able to access the Web Tours app in local server now. Thanks! :-)
I am trying to queue a build in my own build definition. But the sql connection in my code throws an exception that Login failed for user 'domainName\computerName$' which is natural since it should have used domainName\userAlias.
My question is why is it using domainName\computerName, and how to make it use windows auth instead? Can some one please help me with this?
You need to set the service account that the build service uses on the server(s) running your Build Agent(s). It sounds like it's currently set to run as Network Service.
You can change it by firing up TFS Admin Console, and going to Build Configuration and changing the properties on the service:
I am getting an WebSphere MQ Reason code 2195 MQRC_UNEXPECTED_ERROR when I try to connect to the message flows deployed on the execution group. Can somebody please tell me what exactly does this reason code mean? Queue manager, broker , execution group.. everything is up and running and the ports are also open. I am not getting anything worthwhile on the net.
Please advise.
The 2195 return code is a high-level exception that is hit when errors are not caught at lower levels in the code. Very often these are generated when some external dependency such as file access or OS resources do not behave as expected and the failure cascades into WMQ.
Usually when these errors are thrown, WMQ will produce an FDC file in {WMQ install dir}/errors to record the event. The FDC file tells which executable failed, the function that was executing during the failure, the environment, user ID and many other details. These can be used by IBM to diagnose the problem but are often useful for WMQ admins as well.
As a general rule, for any WMQ error that you cannot easily diagnose, take a look in:
{WMQ install dir}/qmgrs/{qmgr name}/errors/AMQERR01.LOG
{WMQ install dir}/errors/AMQERR01.LOG
{WMQ install dir}/errors/*.FDC
When reporting an error, please post whether you found any error log entries or new FDC files in these locations and if so what the content of these was. This will make it easier for respondents to to provide answers that are specific and relevant. If you care to update your question with diagnostic info from the errors directories, I'll be happy to update this response in kind.
You might encounter this code after changing your NT password, as the service tries to log on with your saved credentials.
Change the UID/pwd through the command console -
AMQMSRVN -user \ -password
And, to be safe, in ther services menu, update the stored passwords for Services MQSeriesBrokerROL_ACB_BROKER and MQSeriesServices in properties -> LogON
I try to create a WebSphere queue manager in production env. Before this I manage to create the queue manager in the development env with no problem.
I'm using this script to create the queue manager:
crtmqm -u SYSTEM.DEAD.LETTER.QUEUE test1.qm
But it give no response (no error or success message).
When I try to start the queue manager (strmqm test1.qm) it give
"AMQ8118: WebSphere MQ queue manager does not exist."
Then I notice lots of strange thing that supposed not happen:
I can run the "crtmqm -u SYSTEM.DEAD.LETTER.QUEUE test1.qm" several times without any error
I can just type crtmqm and got no response
I can type crtmqm -y (which is not possible since there is no -y argument) and still no response
Can anyone tell me what is wrong?
If you are on UNIX, it may be that the OS kernel parameter requirements have not been met. Check the relevant WMQ Quick Beginnings manual for the platform.