The book and video tutorials that i am following for WebSphere Administration talks about "pmt.sh" script and how to use it.
However, in my WebSphere installation on Linux which is WAS 7.0 [not a ND package] I do not find any "pmt.sh" script.
Can you please let me know the equivalent script of the same and some idea about why it is missing in my Install?
The pmt.sh tool is not available on 64 bit systems.
You will need to use the manage profiles command line tool instead. See the link below to learn how to get and use the interactive wrapper for the command line tool, which makes the command line tool more user friendly.
http://www-01.ibm.com/support/docview.wss?uid=swg21442487
Related
I have a Windows installer script for a Windows application I'm delivering to customers. I want to have the application installed as a Windows service.
I've been reading up on various ways to do this. The closest I've found that can do this from a command is sc.exe as described in Create windows service from executable here at Stackoverflow, but this command requires running it as administrator, which as far as I can tell, also requires submitting an administrator's password.
In my build script, there's no way to right-click and "run as administrator".
Is there any way to do this from a build script (I'm using my company's installation packager to do this, which uses Ant-like XML build files with an command and statements -- so, much like running at the Windows command line). If I could figure out a command-line implementation that my customers can use I could give them this package.
Thanks for any tips.
Scott
Richard of Last.fm over at metabrew has ported his apps to Erlang. It was also done by riak, couchdb and others. He mentions extracting the needed parts, or including the whole VM into the distribution. Main trait here is: the program does not require Erlang to be installed on the target machine.
So the question is, how do you, step by step, package an Erlang program into a windows (and, less important, linux) executable?
P.S. I've seen the SAE project, and I've read all the relevant questions here. None answer my question.
Create a portable version of Erlang (for example using method from this discussion group: Erlang on Windows from USB). The most important part in this exercise is the creation of the erl.ini file with correct paths which can be used to start Erlang from any desired location.
Create an Erlang release of your application and the release boot script. For instructions see Erlang documentation about releases.
Create a Windows command line script to boot your application. This will simply run Erlang with your boot script as the parameter (e.g. erl -boot someapp). Erlang will read the erl.ini file to load your application and system libraries from correct locations.
Create a Windows setup application with all the relevant parts packaged in:
the Erlang distribution
the erl.ini file with all the paths as variables to be filled in by the setup application
the release of your application (all the beam files and the boot script)
the command line script to boot the application using the boot script
How it should work from the Windows installer point of view:
Ask user where to install the application (or use some default location in Program Files)
Copy the Erlang distribution, your application and the boot script to the correct location
Update erl.ini and the command line script to use the chosen location
Create icons or autostart entries that will execute the command line script
Now when user clicks the icon or executes the command line script in another way they will in fact run Erlang from the custom location, which in turn will boot your application according to the Erlang boot script. This is just a general idea because the command line script should for example check if Erlang isn't already running when user starts the application for the second time, or it may need to be able to uninstall it.
I'm totally new to Windows programming.
I wish to connect to a SQL Server that utilizes AD authentication. All we need is a simplest possible command line utility to fetch some data and dump it to a text file. Can I use VBScript for this/any-other-simple-script?
My first preference was to use Perl on Unix. Tried dbi:Sybase, doesn't seem to work :(.
TIA.
Edit: I don't have admin privs so my options are pretty limited. Cannot install Python.
If you want a simple "script" try out python pymssql:
http://pymssql.sourceforge.net/
available for windows python 2.4 , 2.5 , 2.6:
http://sourceforge.net/projects/pymssql/files/pymssql/1.0.2/
just install it and check out the samples:
http://pymssql.sourceforge.net/examples_pymssql.php
Googling by keywords powershell + sql server + windows authentication gives several solutions:
http://www.mssqltips.com/tip.asp?tip=1947
http://www.powershellcommunity.org/Forums/tabid/54/aff/24/aft/4540/afv/topic/Default.aspx
http://technet.microsoft.com/en-us/magazine/gg313741.aspx
etc
I have an Erlang application that is deployed on a server with Windows Server 2008.
The way I do this:
Copy application folder in Erlang lib directory.
Open command line (cmd). Execute erl.
Execute application:start(app_name) in Erlang shell.
Are there any better approaches to launch the application? How to make the application to launch on Windows startup?
I have no experience with Windows but...
`1. First of all, you might want to have a look to the concept of release in Erlang. Essentially,
When we have written one or more applications, we might want to create a complete system consisting of these applications and a subset of the Erlang/OTP applications. This is called a release.
`2. Then, you might want to create a script that contains something like:
erl -boot ch_rel-1
Where essentially you're starting Erlang/OTP using a boot script that you created above (just follow the instructions in the releases page)
`3. This article explains how to create startup scripts in Windows Server 2008 (not tested, just googled):
http://technet.microsoft.com/en-us/magazine/dd630947.aspx
Hope this helps. Nice question.
Perhaps rebar might help. It makes building an app skeleton and release quite easy. A nice tutorial is here.
After getting familiar with releases, take a look at manual pages (erl -man ) for start_erl and erlsrv. I used them to start embedded system ( http://www.erlang.org/doc/embedded/embedded_nt.html ) in windows 2003, hope it still works for you in windows 2008.
After creating service with erlsrv it is possible to manage it via standard windows command line and GUI tools, e.g. setting start mode and restart policy.
May be you could start just your application by supplying "-s app_name" as erl/start_erl additional flag, but I didn't try that, as I had to go long route with embedded system release. In that case make sure you have "start() -> application:start(?MODULE)." in your "app_name.erl".
Is there any free software to package a powershell script into a standalone WIN32 executable?
It seems it was possible to get the powershell beta's to run on win2000 and winNT, is there any known way to get the final powershell to run on it?
I don't think there is any software that will package a PowerShell script into a stand-alone executable. That would require bundling PowerShell itself with the script (no small feat).
The oldest supported OS is Windows XP SP2, so there is not a supported way to get PowerShell to run on NT or 2000.
A easy step would be to create a .NET exe which embedded the script.
This would, of course, require PSH (and any non-standard snapins) installed when executed.
To remove those dependencies you would need to be able to handle any cmdlets used, as noted #aphoria this would be reinventing PSH, and all the snapins.
Not strictly the answer you are looking for (free software), but it may be useful to others. Here are some commercial options for packaging scripts into single executables:
Admin Script Editor
PrimalScript OR PrimalPackager (just packaging portion of PrimalScript)