Currently Microfocus server and IBM MQ are hosted in different servers and linked by MQSERVER environmental variable in Microfocus.
What configuration need to be changed in Microfocus to connect to IBM MQ hosted on same server?
I tried changing the MQSERVER variable to new server details, but it failed due to 2538 unable to find mq host.
Assuming that your code does not provide any of the connection details, which given you are using MQSERVER environment variable, suggests it does not; then you can switch from a client connection to a local bindings connection by:-
Removing the MQSERVER environment variable
(Optionally) setting the MQ_CONNECT_TYPE environment variable to LOCAL
Related
I/m trying to connect remote queue manager from my Java code.
I have host name, port number, channel, Queue manager name and queue name to connect the remote mq.
So my questions is...
Do we need to create a new queue manager and queue in local and then do Java configuration in code to connect remote mq?
I see MQSample.java has no local queue creation code, which was provided by IBM websphere mq.
When i try to access the host and port using telnet...it works showing blank cmd and. So I guess no connection problem to that remote host.
Please show some examples to connect remote mq using Java. I tried looking IBM MQ tutorial also.
I have installed WebSphere Application Server v7 Stand-alone Edition. I have also created three application server profiles and one administrative agent profile. The hostname parameter was set to 'hostname' when creating these profiles. How can I update this parameter to the actual hostname of the machine?
You can use the wsadmin tool to change the hostname. For instructions, see this link to the IBM Documentation for WAS 7.
You will need to repeat the process for each of the created profiles. Once the change is done, restart the servers for the changes to be correctly reflected.
Stop WAS
Edit the file serverindex.html located under:
#IBM_home$/profiles/$Server_name$/config/cells/$cell_name$/nodes/$node_name$
Replace the old hostname with new hostname under all hostName and host definitions
Start WAS
the request from ihs is passed to plugin then to the application server and server received it.there is no cluster environment here.the server is up and running fine.But the response is not going back to plugin.how to troubleshoot?
(I would have made this a comment, but I don't have enough rep points).
You may need to engage IBM WebSphere Support to assist with this, but typically, for that type of issue, you would need to trace both sides of the connection (IHS plugin and WebSphere). Specifically,
Set LogLevel="Trace" in the plugin-cfg.xml
Set the following trace spec on the AppServer:
=info:com.ibm.ws.webcontainer=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:TCPChannel=all
Reproducing the failure and reviewing the http_plugin.log and trace.log may provide some clues.
Do you receive some type of error in the browser? timeout? Is there anything (firewall, proxy) sitting between the IHS server and WebSphere AppServer?
It could be DNS problem with your WebSphere server. Can you please let us know about your IHS and plugin. Is it installed on same server where WebSphere is or on different server? If IHS and plugin is on different server just check that WebSphere server is able to resolve the IP address of IHS server using hostname. If not try to update host file with IP and hostname of your IHS server. It should work.
Does the client or the plugin not getting the response? Will that the request result in secure connection (i.e HTTPS/SSL...)?
The WAS server should extract most of the ports correctly if IHS/plugin is used in between. If using different webServer/load balancer(LB), the WAS server may not extract the listerning ports on the webServer/LB correctly.
You can take a look at the sample setting in PK55330 where a different web server is used in place of the IHS.
http://www-01.ibm.com/support/docview.wss?uid=swg1PK55330
Regards,
We can do a cf login in an environment that requires an (HTTP) proxy. But cf ic login fails. Is there something else we have to do? We were able to use cf ic login when switching to another network that doesn't use a proxy but that is no long term solution.
If you have an HTTP proxy server on your network between a host running the cf CLI and your Cloud Foundry API endpoint, you must set HTTP_PROXY with the hostname or IP address of the proxy server.
The HTTP_PROXY environment variable holds the hostname or IP address of your proxy server.
HTTP_Proxy is a standard environment variable. Like any environment variable, the specific steps you use to set it depends on your operating system.
For setting your http proxy, you should follow the instructions described at
http://docs.cloudfoundry.org/devguide/installcf/http-proxy.html
I am attempting to create a new Database Project in VS2010 via the New Project Wizard, and via this article: http://msdn.microsoft.com/en-us/library/aa833432(v=vs.100).aspx
I am on the 'Configure Build/Deploy' step, and am attempting to connect to a named instance of SQL Server 2008R2 that I just installed, called DEVELOPMENT. Assuming the server name is DB-01, I am using DB-01\DEVELOPMENT as the Server name in the dialog in the screenshot below. I'm also using the remaining settings in the dialog, but it keeps giving me the following error:
A network-related or instance-specific error occurred while
establishing a connection to the SQL Server. The server was not found
or was not accessible. Verify that the instance name is correct and
that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the
connected party did not properly respond after a period of time, or
established connection failed because connected host has failed to
respond.)
DEV is the name of a database I created on the DEVELOPMENT instance. If I use DB-01 as the server name, which is the default instance, it connects. In the past, we've been developing from a database on the default instance, with no issues, but I'm trying to move to local, source-controlled databases. What am I missing with this not connecting?
EDIT: As a little more context, it's not the username/pw combination, or the existence of the DEV db on the instance, because I receive different errors if either of those are incorrect. It's simply not able to connect once I give it the named instance.
Figured it out:
The default instance of SQL Server (called MSSQLSERVER in some places) uses port 1433 by default for incoming connections, which was opened in Windows Firewall. This is why I was able to connect to the default instance (DB-01). If you've created a named instance of SQL Server, by default these instances use port 1434 for incoming connections. These are TCP ports for each case. Well, I have to admit that I opened TCP port 1434 in Windows Firewall and still was not able to connect to the named instance remotely, and still am not sure why this was the case. So instead, I opened up a random port (6969) in Windows Firewall, and configured the DEVELOPMENT (named) instance to accept incoming connecting over that port only. For instructions on how to configure specific SQL Server instances to use ports other than the default, see this article:
Configure a Server to Listen on a Specific TCP Port
Once I configured the instance to use port 6969, I was able to connect with no issue. Hope this helps others that are having a similar/same issue.