I've been working on a message flow on IBM Integration Bus just for my studies where I wanted to use the Loopback Request Node to connect with MongoDB Atlas. I created a userID "iibUser" and set the password to "iibP#$$w0rd".
Next, I wanted to set the params using mqsisetdbparms WBIBKD12 -n loopback::secID -u iibUser -p iibP#$$w0rd but after mqsireportdbparms WBIBKD12 -n, it is not showing in the report, check this. Although it worked fine for password without any special character.
Can anyone please help me regarding this?
Related
I'm new in JMeter and I am using the JMeter5.1 and I want to know about that how to record the script in JMeter through VPN Server?
I want to record the script in using this command line:-jmeter.bat -H -P -u -a -N
But I'm facing a some issue.That website run only Firefox browser without proxy. that's why I'm not able to record the script.
I know you can do this but there is no enough information in your question. Can you give more details so the other can try to help!
What is your situation? Are you tying to record an application on the same network as JMeter or a different network...?
My only experience with using VPN was when I had to record via VPN few times using a work laptop from a hotel room. I was able to do so, but I got few weird issues about JMeter browser trust certification, so I had to remove it and re-install it again.
I want to email myself an error log stored on AWS EC2 instance to help me troubleshoot an issue I am having while trying to remote desktop to the machine. This is a one time thing - I am not going to use EC2 to send emails reguarly from a web app etc. Reading this link it says:
Q: Are there any limitations in sending email from EC2 instances?
Yes. In order to maintain the quality of EC2 addresses for sending
email, we enforce default limits on the amount of email that can be
sent from EC2 accounts. If you wish to send larger amounts of email
from EC2, you can apply to have these limits removed from your account
by filling out this form.
So this means I should be able to send a few emails without any problem. I tried emailing myself the error log like this:
cat log.txt | sudo mailx me#yahoo.com
It does not give any error but the file is never delivered. I think its never send out. How can I troubleshoot this? I am not familiar with unix. Reading around a bit mailq shows me this:
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
6295B488F5 37616 Wed Apr 1 02:10:30 root#ip-xxx-xx-x-xx.us-west-2.compute.internal a#yahoo.com
I don't know what to do beyond this.
EDIT: Its funny. I did get the messages delivered to my inbox but it was only after about 2 days.
If you have ssh access to the box,just use scp to get the file. E.g., from OSX command line:
scp -i your.pem ubuntu#ec2-1-2-3-4.compute-1.amazonaws.com:your_file your_file
This is for "ubuntu" login, with "your_file" in home directory, saved to same name locally. I guess there are GUI versions also, e.g., I used to use Putty on Windows.
We are trying to do performance testing using JMeter.
I used the sample guide provided in jmeter using HTTP PROXY SERVER but my record controller was not recording any requests.
After doing a lot of research and here is what the complete scenario is.
I am accessing external sites using company proxy server. So, after a bit of research, I understand I need to start my jmeter by supplying all information via command line. e.g.
jmeter -H 129.198.1.1 -P 8000 -u someusername -a someuserpassword -N localhost
Now i understand that, i don't need to confuse these settings. By default JMETER uses its own internal proxy server.
We need to configure our browser so that it uses jmeter proxy settings and i did that way.
I added a thread group, a recording controller, http proxy server with url include patterns and exclude patterns but still, it's not able to record any scripts.
What am i doing wrong? Can someone help me with it?
I used document JMeter proxy step by step which comes bundled with JMETER documentation.
Here is my configuration
Remove everything in :
URLs patterns to include
URLs patterns to exclude
click on Add suggested excludes
It should work.
Currently your include patterns are wrong :
https://jmeter.apache.org/usermanual/component_reference.html#HTTP_Proxy_Server
The include and exclude patterns are treated as regular expressions (using Jakarta ORO). They will be matched against the host name, port (actual or implied) path and query (if any) of each browser request. If the URL you are browsing is
"http://jmeter.apache.org/jmeter/index.html?username=xxxx" ,
then the regular expression will be tested against the string:
"jmeter.apache.org:80/jmeter/index.html?username=xxxx" .
Thus, if you want to include all .html files, your regular expression might look like:
"..html(\?.)?" - or ".*.html" if you know that there is no query string or you only want html pages without query strings.
See this reference documentation for how to record:
https://jmeter.apache.org/usermanual/jmeter_proxy_step_by_step.html
If you're looking to learn jmeter correctly, this book will help you.
I had a similar problem when configuring firefox for proxy and recording on localhost. In Firefox -> Tools -> options -> Advanced -> Network -> Settings
there was an entry for localhost in No Proxy for.
I removed that and it works
I have faced similar problem, please see below. As JMETER proxy is running on localhost, please uncheck the below checkbox.
Install Jmeter Chrome extension which records HTTPS protocol without any issue.
You have done wrong writing the syntax/format for "URL Patterns to Include" and "URL Patterns to Exclude" in "HTTP Proxy Server" under Workbench. The syntax/format should be as below:
.*\.jsp
.*\.jsf
.*\.html
But, you have written forward slash(/). Such as .*/.jsp. After correcting the syntax it should be recorded.
The Jmeter proxy server must be started before Firefox can connect to it. JMeter has its own proxy server so the Recording Controller 'start' button has to be pushed before FF will allow access to a website.
As far as I can understand the issue. The issue is not what it seems, JMeter and Browser are able to interact with each other. But the thing is that How to make sure that JMeter is able to use the proxy.
Now for this, there are many way outs. I'll start with the easiest one.
Install Blazemeter Extension in your browser and start recording in it. It will provide you a .jmx file once you're done
The second one is configuring JMeter to access the proxy.
the command is changed a bit now.
jmeter -E https -H my.proxy.server -P 8000 -u username -a password -N localhost
Please note that you need to change the below values:
my.proxy.server
8000
username
password
In case you don't use a username and password to connect to the proxy, simply omit the -u username -a password part.
Reference: https://jmeter.apache.org/usermanual/get-started.html#proxy_server
This will work to record the script.
Now, to run the script. This may not execute the things as expected.
In that case, you have a Advanced Tab in HTTP Request Sampler, go there and provide your proxy server details there.
I am trying to start an application in Websphere 8, and keep on getting the following error.
From the message, it means we are missing the bindPassword, but we never have to define in WAS 6.1
Currently we are using Standalone LDAP registry. Does anyone have any idea where I should start looking to fix this error?
UserManagemen E com.ibm.ws.wim.management.UserManagementProcess handleNo
tification CWWIM6004E Initialization of the dynamic reload manager failed.
com.ibm.websphere.wim.exception.MissingInitPropertyException: CWWIM0004E The initialization property 'bindPassword' is missing from the configuration.
at com.ibm.ws.wim.adapter.ldap.LdapConnection.initializeEnvironmentProperties(LdapConnection.java:194
7)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.initializeServers(LdapConnection.java:1904)
at com.ibm.ws.wim.adapter.ldap.LdapConnection.initialize(LdapConnection.java:1832)
at com.ibm.ws.wim.adapter.ldap.LdapAdapter.initialize(LdapAdapter.java:235)
at com.ibm.ws.wim.RepositoryManager.initialize(RepositoryManager.java:610)
at com.ibm.ws.wim.RepositoryManager.<init>(RepositoryManager.java:131)
In regards to ".... never have to define in WAS 6.1"
The requirement for a LDAP bind password is enforced by the LDAP server, this is not a WAS requirement
If in fact you didn't define it in WAS v6.1, the LDAP server in use for WAS V6.1 didn't require it.
Based on the error, you've either changed LDAP servers or the LDAP server configuration has changed (or both)
As mentioned in the other post, you can troubleshoot this using a tool like ldapsearch
The technote at http://www-01.ibm.com/support/docview.wss?uid=swg21470063 discusses obtaining "must gather" and troubleshooting these types of issues (refer to the "collecting data manually" section)
You must check your ldap connection to the ldap server
User IBM WebSphere Console, Security settings, LDAP and take note about the LDAP connection settings.
Use a tool like ldapsearch in order to check the connection via shell command line.
It is possible that these bind password is not correct.
If you are using un Novell eDirectory Server you must take special attention in the bind user creation ( field password )
Maybe not the best worded question, but hopefully it's a straightforward problem.
The scenario is SSHing from a personal account on box A to a generic account on box B. The script running on box B needs to capture the personal account name for logging purposes. Is there any way of capturing this, either via SSH itself or some information captured by the shell? We are using ssh2 (Reflections), and KornShell (ksh) on Solaris.
If you have full control of the client machine, you can deploy identd to get the username.
Full procedure to get name from script:
Walk up process tree, find sshd
Walk netstat -p to find the remote IP and port.
Connect to client on port 113 and ask.
You may have to disable privilege separation for this to work as-is; however it should be trivial to modify to work w/o it.
You can't log the remote username reliably
You can log the IP of the connection (see the SSH_CONNECTION variable)
You could have a standard where they use an alias for ssh that logs the remote username as part of the login process, or where they store their username in a .ssh/environment file (but allowing environments to be set may require ssh/sshd config changes).
alias sshblah='ssh blah "REMOTEUSER=$USER; bash'
(Except that doesn't work, and I haven't tried to figure out why - and it would be different if you use tcsh, etc).
You can use environment passing in this manner, and select which variables you allow to be set. You'd have to get the users to set some alternate to $USER, like $REMOTE_USER=$USER, and then allow $REMOTE_USER to pass through. And you're trusting they don't set it incorrectly, or forget to set it (you can handle that case with a little annoyance by modifying this mechanism).
Note that you almost have to trust the client connecting to tell you who the user is - you can make it hard/annoying to spoof the username, but unless you use per-user certificates instead of a generic login/password they all know, you can't verify who connected.