webMethods experts,
I have two simple questions…
1- Is there a way to force webMethods to only accept 128 bits SSL connections?
2- How can I stop the B2BServer without using the administration web interface. I know we can always kill the process/jvm but I am interested in a more graceful solution.
Thanks

— a java class to stop B2B I.S. —

import java.io.*;
import java.util.Vector;
import com.wm.util.Table;
import com.wm.util.Values;
import com.wm.app.b2b.util.GenUtil;
import com.wm.app.b2b.client.Context;
import com.wm.app.b2b.client.ServiceException;
import com.wm.util.coder.ValuesCodable;

public class B2BShutdown {

    public static void main(String[] args) {

if (args.length != 3) {

System.out.println("\nUsage: JavaCMD B2BShutdown [yes/no] [force/drain] [timeout]\n");
System.out.println("\t[yes/no] = restart?");
System.out.println("\t[force/drain] = immediate/wait?");
System.out.println("\t[timeout] = minutes to wait before committing?\n");

System.exit(0);
}

// Edit these settings for your locale and then compile
String server = "{your host name}:{port value}";
String username = "Administrator";
String password = "{the admin password}";

// Edit these settings to your preference
String bounce = args[0];   
String option = args[1];  
String timeout = args[2];

Values in = new Values();

Context context = new Context();

try {
context.connect(server, username, password);
} catch (ServiceException e) {
System.out.println("\n\tCannot connect to server \""+server+"\""); 
System.exit(0);
}

try {
in.put("bounce", bounce);
in.put("option", option);
in.put("timeout", timeout);

in = context.invoke("wm.server.admin", "shutdown", in);
} catch (ServiceException e) {
System.out.println("\n\tCould not shutdown server:  " + e.getMessage());
System.exit(0);
}

System.out.println(in.getString("message"));

}

}

Cheers,
Emmanuel

Another way to stop the server (remotely) is to paste the string http://hostname:port/invoke/wm.server.admin/shutdown
into your browser. You’ll be prompted for your username and password; once you enter them it’ll shut down.

As for 128-bit SSL, there’s two new configuration parameters in Integration Server 4.6: watt.net.ssl.client.strongcipheronly and watt.net.ssl.server.strongcipheronly. If set to “true”, then clients or servers (respectively) will refuse any 40 bit SSL connections. These parameters are mentioned in the release notes, but not in the Administrator’s Guide.

Thanks guys.
Btw we are using B2B 4.0.2 and it requires a patch from webMethods to be able to force 128 bit SSL.
Thanks again
-fA